FHIR Chat · Linking Jira tickets · implementers

Stream: implementers

Topic: Linking Jira tickets


view this post on Zulip Cooper Thompson (Sep 23 2021 at 20:51):

Who owns the workflow for FHIR Jira tickets? I've noticed you can't link tickets after a ticket has been resolved (the "Link" option is no longer available under "More"). Who can fix that?

view this post on Zulip Gino Canessa (Sep 23 2021 at 21:17):

Paging @Lloyd McKenzie =). But if you're interested in non-authoritative, vague memories...

I believe the rationale is that once a ticket is resolved, there's little chance of anyone seeing updates, so they are generally locked to prevent any changes that could effect their intent/resolution/interpretation/etc.

For links such as marking duplicates, it's dangerous to try since the ticket may be trying to address old tickets that were applied insufficiently or incorrectly, marked as applied but not, etc.

view this post on Zulip Cooper Thompson (Sep 23 2021 at 21:23):

I mean the workflow now is to re-open the ticket, link trackers, then re-resolve the ticket.

view this post on Zulip Cooper Thompson (Sep 23 2021 at 21:24):

For historical reference, having linked trackers is very useful. Can we pretty please update the workflow to allow linking?

view this post on Zulip Lloyd McKenzie (Sep 23 2021 at 23:38):

Can you explain more about what your objectives are with the linking? (Also, things like this are best asked in #JIRA/Confluence)

view this post on Zulip Cooper Thompson (Sep 24 2021 at 13:57):

PA has a bunch of trackers about RelatedPerson relationship and role. We addressed those trackers over several meetings, and ended up with resolutions that "conflicted" (the intent of the resolution was consistent, but the specific wording we drafted was slightly different). E.g. FHIR#19411 and FHIR#26994. Having these linked would be nice when we go to apply them so the editor can easily see that these are related.

view this post on Zulip Cooper Thompson (Sep 24 2021 at 13:58):

This is the recent example that spurred this request, but there have been past examples as well.

view this post on Zulip Cooper Thompson (Sep 24 2021 at 13:59):

Also - feel free to move this over to #JIRA/Confluence if you like.

view this post on Zulip Lloyd McKenzie (Sep 24 2021 at 15:17):

Ok. Trusted users can add comments, so what I've done in those situations is just comment and specify a hyperlink in the comment. I can update the "change groupings" function to also allow changing linked issues I suppose. But not sure what to name that combined ability. I'll put it on my list of potential enhancements.

view this post on Zulip Cooper Thompson (Feb 14 2022 at 20:28):

@Lloyd McKenzie - is the feature to be able to link resolved tickets still on your todo list? I'd still find that very useful. PA has several "master" trackers and I like being able to link all the "child" trackers so we have one place to look for all the related changes. When both the master and children are already resolved, that isn't possible. I've been trying not to use my "reopen" powers to add links, but doing a re-open, link, then re-resolve with same vote and a backdate is increasingly tempting when it isn't possible to do a link...

view this post on Zulip Lloyd McKenzie (Feb 14 2022 at 21:36):

Yes, that's still on the list. It's tricky though as we don't want things like 'duplicate', or vote links to be allowed to issues that are already resolved.

view this post on Zulip Cooper Thompson (Mar 02 2022 at 21:04):

Here is another example of two trackers that would be useful to link after voting: FHIR-36074 and FHIR-34261.

view this post on Zulip Cooper Thompson (Apr 04 2022 at 15:57):

Another example of two tickets that would be nice to link: FHIR-36655 and FHIR-36657.


Last updated: Apr 12 2022 at 19:14 UTC