This page will be used to post CTO and project team updates related to the implementation of Confluence and Jira Collaboration software at HL7.
As promised, we have now 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.
For those of you who are new 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 . We believe you’ll find JIRA to be intuitive and natural, but we’ll be adding additional documentation and tips over time to this page to help improve your experience.
In the future, all HL7 work groups and projects will be expected to use JIRA as our standard issue tracking tool. We will not be supporting use of GitHub tracking, so any projects using that are advised to begin transitioning to JIRA. Once the FHIR migration is completed, we’ll be getting in touch with other WGs to complete migration of any remaining GForge Tracker items.
So this is an exciting milestone in our quest for improved tooling at HL7. I’d like to especially thank Lloyd McKenzie and the JIRACon team (Lorraine Constable, Jean and Marc Duteau, Josh Procious, David Johnson and Patrick Lloyd in particular) for making this migration possible. And thanks to those of you who cleared up your remaining Tracker items in time to allow this to proceed as planned.
As always, if you can think of ways to improve our offerings, please click on the feedback links to tell us what you think. (We can take it.)
The FHIR community is leading the transition to adopt JIRA tracking to replace GForge. We’ve agreed that building comfort and familiarity with JIRA is a useful pre-requisite to making the transition to JIRA Balloting, though we still expect to begin balloting in JIRA later this year once we complete our system testing. We expect to provide more info about this by the Montreal WGM.
See the May HL7 Newsletter for additional tooling updates.
~85% of HL7 Workgroups have now been migrated to Confluence. For those of you who haven’t made the cut-over yet, please do sign up for schedule migration with Joshua Procious, HL7 Application Manager.
The HL7 Documentation and Help space has been consolidated and has new content pretty much every week regarding some little how-to or another
Improvements to attendance log to accommodate more simultaneous users
Workflow has been added to the online PSS. Pilot testing continues, and we’re planning to demonstrate in San Antonio.
Two new quick webinars with helpful hints(to join the 3 previously released):
There are feedback links in the description of each webinar where a user can say how they liked it and suggest/submit future webinar content so please tell us what you think.
For now, we’re continuing to make use of Confluence optional, but to achieve our goal of greater consistency among all HL7 work groups, we’ll be seeking to get all committees in the new environment and begin posting all new WG content in Confluence by early 2019. While we’ll continue to maintain access to MediaWiki, we would like to see all new WG process content in Confluence by the Montreal WGM if possible. We’re also using this opportunity to try to focus on migrating only current, important content to make it easier for all to find what’s really essential.
Of course, we recognize that introducing new systems can be an initial cause of disruption and angst, especially since we’re complicating the environment with yet more choices on where to locate relevant information. So here are a few guidelines for where we’d like to be before the end of 2019:
We’ll continue to use hyperlinks to navigate easily between hl7.org, confluence and MediaWiki. Again, we’ll be providing further details soon.
The advent of the new JIRA ballot system will introduce most HL7 members to JIRA beginning in 2019. Recognizing JIRA’s advanced features for issue tracking and work management, we expect to begin migrating work groups currently using Tracker to JIRA tracking early next year as well. Stay tuned for more details.
One of the main benefits -- and risks -- of Confluence is transparency. Although I promised to maintain regular updates in my May 3, 2018 post, it’s all too obvious how I have been remiss. So, let me begin with an apology, and a more sincere promise to be more communicative in the future as major developments occur.
Meanwhile, despite my radio silence and after a hiatus proving Hofstadter’s law, a great deal has happened since that last update.
We are very pleased and fortunate to welcome Joshua Procious as our new Applications Manager. Please be sure to introduce yourself. Josh will be supporting HL7 tools, including Confluence and JIRA, and will be joining us in Baltimore, where he’ll be conducting a Confluence training session Q0 Tuesday and be available for consultation throughout the week.
For those of you not yet using Confluence, we’re now working to actively move you over. Co-Chairs will be able to sign-up to schedule migration of their WGs to Confluence over the next several months. Use of Confluence is highly encouraged wherever practical but not mandatory at this point -- we’ll continue to maintain MediaWiki for the foreseeable future, especially for sites where migration may be impractical, and we intend for it to be available on an ongoing basis as a historical archive.
For those of you who are already using Confluence and don’t want to disrupt your current space design, please contact Josh who will work with you to get you easy access to the new templates. It will also be helpful to watch the webinars if you can.
For those of you who still aren’t ready to deal with anything like this now, you get a pass, though we’ll revisit you in San Antonio.
HQ will be rolling out a fresh new 21stCentury home page at the Baltimore WGM. Prepare to be amazed how an old dog can be taught new tricks!
Finally, a few words on remote connectivity. We tested a potential new process for allowing remote connectivity at two prior WGMs. Unfortunately, the experience was ultimately disappointing. The connections were time-consuming and problematic to set up with many challenges due to different hardware and networking issues, and were generally unreliable and more frustrating than effective. As a result, we have concluded that HQ simply can’t provide adequate support to offer this as a service for future WGMs. However, co-chairs who wish to allow remote connections for certain sessions are welcome to do so using their own facilities.
if you’re still not using chat.hl7.org, time to be woke. Remember, chat.fhir.org contains chat for the FHIR Community. chat.hl7.org is for the rest of us to discuss other HL7 topics. The Zulip client allows you to access both streams.
New Confluence features now available from JIRACON project team:
System updates completed in April by Webmaster:
Work on Online PSS, JIRA Balloting and Unified Terminology projects continues.
Other: Zulip Update
On another note, if you’re not using chat.hl7.org, you should be. Now that we’ve had time to pilot Zulip for awhile, we’ve eliminated the requirement that you receive an invitation before joining a stream. Now you can elect to join any public stream. You can register by going to chat.hl7.org.
Remember, chat.fhir.org remains for the FHIR Community. chat.hl7.org is for the rest of us to discuss other topics. The Zulip client allows you to access both streams.