Stream: JIRA/Confluence
Topic: importing Ballot spreadsheet for non-FHIR Ballots
Lorraine Constable (Sep 21 2021 at 17:26):
I just tried uploading a comment spreadsheet for a non-FHIR ballot (in this case, the Nutrition DAM headed for the OTHER spec feedback project).
The upload validation is rejecting the page number references the balloter provided, and insisting on Resource and HTML definitions, where this is a PDF.
Additionally, for the spreadsheet I received with just a tracker number (OTHER-2161), I get the error [image.png]
ERROR: 7. Referenced issue is not tied to the correct project. For this ballot, issues must be recorded in the specification feedback project.
but the tracker is in the specification project. Is there somewhere different I need to go for non FHIR ballots? @Lloyd McKenzie @Melva Peters
Lloyd McKenzie (Sep 21 2021 at 22:37):
Right. When we did the initial analysis and the various management groups weighed in on what adjustments they wanted made to the Jira process to accommodate their distinct requirements. The decision was that section text and mandatory resource or page name would be the same across all product families. So anything in page number needs to move into 'section' and you must categorize the content as per the pages defined in 'Jira'. For the second issue, can you share the spreadsheet?
Lorraine Constable (Sep 22 2021 at 14:39):
ah, yes, but there was no one to ask about the "other" requirements as they have no management group (maybe other than TSC) and HQ defined the project pages in Jira so there is really no way for a balloter doing a traditional ballot to find that out. I will send you the second spreadsheet - it has a couple of other errors (specifying summary when Jira ticket described, etc). One of the spreadsheets I have referenced line numbers as the pdf provided line numbers to aid balloters. We have a mismatch between what we are sending balloters with the spreadsheets and the expectations of jira
Lloyd McKenzie (Sep 22 2021 at 15:25):
Agree that we should be only sending 'Jira' spreadsheets to all balloters, given that the content needs to be imported into Jira - so there shouldn't be columns for page numbers available to balloters, even if they're still balloting by spreadsheet - @Lynn Laakso
Lorraine Constable (Sep 22 2021 at 18:04):
yes, for the ballots that are currently non Jira ballots, we are setting expectations that do not match with getting them into Jira. This is a fairly small ballot on a pdf document. I am strongly tempted to just reconcile in the spreadsheet and upload to the ballot desktop for this cycle
Lloyd McKenzie (Sep 22 2021 at 18:13):
You can argue with @Melva Peters on that :)
Melva Peters (Sep 22 2021 at 18:56):
@Lorraine Constable if you would like to propose a different structure for the related sections and related pages for the Nutrition DAM, we can change it in Jira. We tried to get this into JIRA so that the imports could be done. Going forward, the owing WG will need to take responsibility for the creation of the files in Github that populate Jira.
Lorraine Constable (Sep 22 2021 at 19:16):
@Melva Peters The key problem is the mismatch between the spreadsheets that are sent to balloters and the requirements of the import process. So they provide identification based on what we asked for on the spreadsheet, not what we actually want for Jira. The current rules are not well suited to pdf type specs. The product family management groups are all transitioning to web based specs but we did not really think through the "other" category well
Melva Peters (Sep 22 2021 at 19:17):
@Lorraine Constable We will make sure make sure the correct spreadsheet is provided for January.
Last updated: Apr 12 2022 at 19:14 UTC
