Closed jarrod-mg closed 1 month ago
This would be useful. Having a single field is not helpful when relevant tickets may exist in more than one system.
From what I see, the two comments above from @jarrod-mg and @reidca are actually referencing several independent points.
As I see it, the request can be split into:
Each one of these could technically be implemented totally independently, but having all of them would make a fantastic addition to the system.
A suggestion I have for a solution to the above would be along the lines of:
Regarding how we solve this currently, we have asked users to add a ticket number, followed by URL, i.e for the URL that @jarrod-mg gave then entering :
This is obviously a bit messy, and we have already seen plenty of user errors when entering it. These kind of enhancements would really help a lot.
This is still a useful enhancement, as we
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed.
I do see this as still useful
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed.
It would be great to be able to turn any reference to a ticket into a link. This would help particularly with approvers, so they can just clink a link to see more details about the request.
This could be as simple as a setting like "Ticket Link Format", which I might set to something like "https://mycompany.atlassian.net/browse/%s" - and then in the UI, any time you emit a ticket number, run it through a printf (or similar) with the ticket link format, in an
<a href="..." />
.