Stream: IG creation
Topic: JIRA specification file
Mohammad Jafari (Dec 01 2020 at 03:18):
We currently get this error in the QA:
There is no jira specification file defined with the expected name of FHIR-security-label-ds4p in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
I understand that this means we should update the JIRA specs file we have in that repo. What I'm wondering is that if we push a new JIRA sepcs file, will that affect or potentially disrupt our current JIRA tickets?
Grahame Grieve (Dec 01 2020 at 03:23):
no
Lloyd McKenzie (Dec 01 2020 at 04:36):
The push process won't let you remove keys for stuff you already have, though it will let you deprecate artifacts, versions and pages. If you update an issue with a deprecated page or artifact, it'll make you update to something that now exists. (Which is why it's good to not deprecate things if all you're doing is renaming.)
Mohammad Jafari (Mar 29 2021 at 23:10):
(This has been a long-running issue for our IG and I'm going back at it after almost a year)
In the QA report I get this error:There is no jira specification file defined with the expected name of FHIR-security-label-ds4p in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
When we created this last year, I was not able to name the file FHIR-security-label-ds4p because it failed a validation check that didn't like numbers in the file name. So, at the time, we moved forward by name the file FHIR-security-label-ds-for-p.xml.
Now that this error is back I am trying to start by renaming the file to match the specs name but the CI fails with java.io.FileNotFoundException while looking for FHIR-security-label-ds-for-p.xml.
Where can I start to fix this?
I am also wondering if the IG build generates a draft for this XML since I heard from @Lloyd McKenzie at the time that it does, and the confluence documentation also alludes to this (the IG publication process it will generate a 'candidate' specification XML file), although it doesn't mention where this candidate file will be located.
Lloyd McKenzie (Mar 30 2021 at 04:16):
Follow the instructions here to add a jira-code parameter to your IG that specifies that security-label-ds-for-p as the code for your IG (because it's different than the id of your IG)
Lloyd McKenzie (Mar 30 2021 at 04:18):
Once that's working properly, the sample file should generate into your root folder.
Lloyd McKenzie (Mar 30 2021 at 04:18):
(of your IG)
Mohammad Jafari (Mar 30 2021 at 06:05):
Thanks @Lloyd McKenzie .
To allow the IG to link to the correct Jira file, add a parameter called 'jira-code' with a value of whatever the 'Code' is in Jira.
where should I add this parameter? I tired the ig.ini and package-list.json but it didn't fix it.
Lloyd McKenzie (Mar 30 2021 at 06:06):
It's an ImplementationGuide parameter
Mohammad Jafari (Mar 30 2021 at 15:11):
Thanks. Can I file a CR against the confluence page to clarify this further in the docs?
Lloyd McKenzie (Mar 30 2021 at 15:20):
We don't do CRs for confluence pages - just go ahead and update the page if you feel additional clarification is needed.
Last updated: Apr 12 2022 at 19:14 UTC
