Jira Specification Feedback
Jira Specification Feedback has been implemented to support the capture of comments on specifications in all product families and for those specifications not part of a product family. Projects have been set up for each product family and for “Other” specifications at jira.hl7.org and are ready for use. FHIR was previously migrated to JIRA for specification feedback, so many of you will already have experience with it. The new projects have the same look-and-feel and workflow as the FHIR Specification Project.
What does this mean for your Work Group?
Specifications have been set up in the relevant projects where the project is in development or the specification is in an active Standards for Trial Use (STU) period or where an STU period expired in 2020 have. Comments from the STU Comment page have been migrated to Jira for all active STU specifications and specifications that expired in 2020.
In addition, comments captured for HL7 V2 changes and CDA changes will now be captured in Jira. Gforge comments have been migrated to the appropriate Jira Project.
Going forward, the set up and management of specifications in JIRA will be the responsibility of the Co-Chairs of the Sponsoring Work Group and may be delegated to the Project Team. Specifications can be set up in JIRA when it is ready to gather feedback. When a new version of a specification is ready for feedback, only the new version is added. Documentation for setting up new specifications or version in JIRA can be found on Confluence: Configuring Jira Specification Feedback
Once JIRA Specification Feedback is rolled out, you will manage all specification comments in JIRA. For more information on managing feedback in JIRA: Managing Specification Feedback
What does this mean for commenters?
Comments that you wish to make on specifications will be entered into JIRA. You must register as a user on HL7’s Confluence and Jira systems.
You can find more information about how to comment in Confluence: Specification Feedback and in these short videos:
Does this change how comments are made and managed for HL7 STU Specifications?
Comments on STU specifications will now be made in JIRA and not on the STU Comment Page. The Expired STU page will continue to be available as read-only. Existing comments for Active STU specifications and STU specifications that expired in 2020 have been migrated to JIRA.
Links to the appropriate JIRA project have been added to the Product Brief for each STU Specification that is accepting feedback. In addition, a link to the JIRA Specification Feedback Projects has been added to the HL7 Website on the Standards Page.
You will now manage all specification comments in JIRA. For more information on managing feedback in JIRA: Managing Specification Feedback.
Does this change how comments are made on HL7 Ballots?
For now, no changes will occur with the HL7 ballot process. You will continue to gather comments in spreadsheets as part of a ballot. As with the FHIR Specification Feedback process, submitters may add their comments in JIRA for specifications that are part of the ballot (assuming the specification exists in JIRA), but they must also submit a spreadsheet that references the JIRA issue.
If spreadsheets are submitted, at the conclusion of a ballot, co-chairs will be responsible for consolidating feedback into a single Excel spreadsheet, ‘cleaning’ that spreadsheet to meet Jira import rules and then importing the feedback into Jira prior to reconciliation. See Confluence for more information on how to complete this process: Importing ballot results from spreadsheets. In the short term, help for preparing spreadsheets for import can be requested via Confluence: https://confluence.hl7.org/display/HL7/Request+Help+Uploading+Ballot+Spreadsheets
We appreciate your patience as we transition to this new process. If you have questions or have problems finding the appropriate project or specification in the project, please post to the Jira/Confluence Stream on Zulip.