Stream: JIRA/Confluence
Topic: Setting up non-web specs in "other" Jira feedback project
Lorraine Constable (Aug 17 2021 at 21:13):
Are there any guidelines for configuring non-web based specifications in the "Other specification feedback" project? Now that the Consent Management Service Functional Model has been published, my last task is to set that up (I have a DAM in the queue as well). Most of the configuration instructions I read in confluence seem to assume a web based publication. Do I use the product brief page as the root URL, for eg? Can I set internal sections of the doc as separate artifacts? etc. @Melva Peters @Lloyd McKenzie
Melva Peters (Aug 17 2021 at 21:17):
@Lorraine Constablefor the root URL, use the product brief URL. Yes, you can use the internal sections as separate artifacts. You can look at what was done for the specifications that exist in the "Other" Specification Feedback Project.
Lorraine Constable (Aug 17 2021 at 21:30):
BTW, this note on the Configuration page should probably be updated or removed:
NOTE: The structure of the Git project are set up to support artifacts from all product families. However, at present, only FHIR has a Specification Feedback project. Other product families should not use Jira for issue tracking until the appropriate tracker has been set up and approved for use by the Technical Steering Committee.
Lorraine Constable (Aug 17 2021 at 21:33):
Also, are there naming conventions I need to follow listed somewhere?
Melva Peters (Aug 17 2021 at 21:43):
The name displayed in Jira needs to be one that the community understands and it is clear what specification is being referred to. I'll update the page.
Lorraine Constable (Aug 17 2021 at 21:46):
I was more referring to key names, etc, but I think I have worked it out
Lloyd McKenzie (Aug 18 2021 at 00:13):
key names can be whatever you wish - but once established, can't change (regardless of what you do to the artifact names)
Last updated: Apr 12 2022 at 19:14 UTC
