Stream: Announcements
Topic: FHIR Tracking in JIRA
Wayne Kubick (Nov 13 2019 at 17:30):
We have scheduled the migration of FHIR tracker items from GForge to JIRA for this coming weekend, November 15-17. We expect to be using JIRA exclusively for FHIR tracking tickets by Monday, Nov. 18.
To ensure that we migrate all Tracker items to JIRA, FHIR GForge Tracker will be locked to read-only at precisely 8pm EST on Friday, November 15 - no one will be able to enter or update FHIR tracker items in GForge after that time so we can ensure all content is migrated to JIRA.
A set of brief webinars on the basics of using JIRA have been posted at https://confluence.hl7.org/display/HDH/JIRA+Tracking .
If you still don’t have a Confluence/JIRA account, you can request one at https://confluence.hl7.org
Lloyd McKenzie (Nov 13 2019 at 18:51):
If you have an account on gForge and don't yet have one on Confluence, we'll migrate your existing count over. If you've got one on Confluence, we'll do our best to link the ported Jira issues to your existing Confluence account.
Wayne Kubick (Nov 15 2019 at 22:19):
Reminder: We'll be migratingFHIR tracker items from GForge to JIRA this weekend. FHIR GForge Tracker will be locked to read-only at precisely 8pm EST Friday evening. We'll send out an update after the migration is completed.
A set of brief webinars on the basics of using JIRA have been posted at https://confluence.hl7.org/display/HDH/JIRA+Tracking .
If you still don’t have a Confluence/JIRA account, you can request one at https://confluence.hl7.org
Lloyd McKenzie (Nov 16 2019 at 01:15):
gForge FHIR tracker is now off-line for the migration process
Lloyd McKenzie (Nov 18 2019 at 02:39):
The use of gForge for FHIR tracker items has now come to a close. The very first tracker item was raised on January 19, 2014. In the almost 6 years since then, the community has submitted 18,534 requests for change - either as part of ballot (8440) or as unsolicited change requests (over 10,000).
All of these tracker items - and their associated balloting information - have now been successfully migrated to gForge. Redirects in the FHIR specifications should now direct users to gForge rather than Jira.
All issue identifiers have been retained, though they are now prefixed with 'FHIR-". For example, our very first issue, which was located at https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=2839 is now located at http://jira.hl7.org/browse/fhir-2839. (See how much better Jira is? :>)
Redirects in the core spec and in chat.fhir.org have already been changed to the new platform, though IGs that were published using older templates may still end up directing to gForge.
As has previously been mentioned, there are a set of starter videos on Confluence (https://confluence.hl7.org/display/HDH/JIRA+Tracking). As well there's detailed documentation on the use of the feedback trackers here: https://confluence.hl7.org/display/HL7/Specification+Feedback
If you run into any questions/issues, you can raise them on the #JIRA/Confluence stream. (If you're not on chat.fhir.org yet, consider this your excuse for signing up, though if need be, you can also send me an email.
Note that the balloting function is not fully functional yet. For now, focus on using Jira just to submit and manage tracker items. Adding additional projects to support CDA, V2 and other product families is on the agenda for the new year.
Lloyd McKenzie (Nov 18 2019 at 10:50):
(Above should have said "successfully migrated to Jira", not gForge :> )
Sean McIlvenna (Nov 21 2019 at 16:12):
@Lloyd McKenzie and @Josh Mandel , SDWG has noticed that "Cross-Group Project Work Group" is not listed as one of the work groups in JIRA. Please add.
Sean McIlvenna (Nov 21 2019 at 17:02):
Also, can you reply directly to email notifications? I noticed that the email notification for a JIRA ticket update came from webmaster@hl7.org... I suspect that if I reply to the email notification, it will not be automatically added as a comment to the issue?
David Pyke (Nov 21 2019 at 17:06):
That's a general ability of Jira, It would be great to have it part of the HL7 Jira
Sean McIlvenna (Nov 21 2019 at 18:04):
agreed
Sean McIlvenna (Nov 21 2019 at 18:05):
also, when I assign a ticket to someone specifically, it seems to be transitioning the issue to "Waiting for input"
Sean McIlvenna (Nov 21 2019 at 18:05):
not sure that is a desired behavior
Sean McIlvenna (Nov 21 2019 at 18:05):
I would think I would want to be able to leave a JIRA ticket as "Triaged" but assign it to someone
Dave deBronkart (Nov 21 2019 at 18:20):
Question with all respect- aren’t discussions like this supposed to migrate quickly out of announcements?
Sean McIlvenna (Nov 21 2019 at 18:28):
probably
Sean McIlvenna (Nov 21 2019 at 18:28):
just don't know where
Lloyd McKenzie (Nov 21 2019 at 20:06):
Answers on #JIRA/Confluence
Last updated: Apr 12 2022 at 19:14 UTC
