-
-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug Tracker Enhancement: Show Bug URL and Bug Status in the Test Execution Row inside Test Run #3748
Labels
Comments
@YouWhy several questions here:
|
|
atodorov
added a commit
that referenced
this issue
Nov 7, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs #3748
atodorov
added a commit
that referenced
this issue
Nov 7, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs #3748
atodorov
added a commit
that referenced
this issue
Nov 7, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs #3748
atodorov
added a commit
that referenced
this issue
Nov 7, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs #3748
atodorov
added a commit
that referenced
this issue
Nov 7, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs #3748
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs kiwitcms/Kiwi#3748
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs kiwitcms/Kiwi#3748
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
API: when integration with a 3rd party bug tracker is configured correctly the Bug.details() API method will now return the additional fields `id`, `status` and `url` alongside the existing `description` and `title`! Refs kiwitcms/Kiwi#3748
atodorov
added a commit
to kiwitcms/trackers-integration
that referenced
this issue
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Currently, we have the ability to log a bug in a configured Bug Tracker directly via a Test Run. I recommend one enhancement which will greatly improve the user experience.
Add BUG URL and BUG STATUS on the Test Case Execution Row. Typically a bug has only 1 state. And no matter which system the customer uses, this change will serve almost all Bug Trackers.
If a bug is logged via the Bug Tracker plugin, then this feature will help everyone visualize the status of Bugs from within the Test Run. So, lets say a BUG is RESOLVED, then a tester can either rerun the test or take some other actions as he/she deems fit.
Currently, user has to click on test case, scroll to bottom and click on the Bug URL to get to the issue status.
Describe alternatives you've considered
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: