Stream: terminology
Topic: jira ticket assignment to term
John Moehrke (Mar 08 2021 at 15:44):
I have some JIRA tickets in FHIR core that are against vocabulary now managed in terminology. Is there a process to move them? I have some really simple ones in that the comment is that the date of the codesystem is in the future (2023), which clearly is not true. FHIR-25623
Lloyd McKenzie (Mar 08 2021 at 15:46):
Use the UTG process
John Moehrke (Mar 08 2021 at 15:50):
awful big and cumbersome hammer to get a typo fixed. This typo might stay wrong until after 2023
John Moehrke (Mar 08 2021 at 16:00):
does the UTG process explain how to re-assign tickets? or link them?
Lloyd McKenzie (Mar 08 2021 at 16:08):
@Ted Klein
Ted Klein (Mar 08 2021 at 20:01):
@Lloyd McKenzie @Jessica Snell @John Moehrke I assume you mean reassigning a FHIR ticket to UTG John? If so, we have not documented or done work to explore and debug exactly how to do that - it is hopefully just an artifact of startup of the new process for updating terminology, swirled with the fact that some very old FHIR tickets were agains core terminology that was 'moved' to THO as part of the R4 core release. In hindsight, what probably should have been done is tickets referring to the moved stuff should have been moved as well. Ah well, 20/20 hindsight...the datafields and screens are different so they cannot just be moved in Jira. I'll put this on the UTG call agenda to be discussed.
John Moehrke (Mar 08 2021 at 20:07):
yes, that is the case... but I would not classify this as a legacy jira ticket problem. This jira ticket came in thru the FHIR change request method, I would expect many others might do that today.
John Moehrke (Mar 08 2021 at 20:08):
but I also wonder if UTG has a light weight pathway for something like this that is clearly just a typo, vs a signficant code fix.
Michael Lawley (Mar 09 2021 at 10:05):
Is it not a simple as creating a "UP" technical correction ticket in Jira and linking the original ticket to it for traceability?
Last updated: Apr 12 2022 at 19:14 UTC
