Stream: JIRA/Confluence
Topic: how to "group" on a ticket attribute?
Isaac Vetter (Mar 17 2020 at 05:20):
Newb question -- is it reasonable to see all of the entered values in a specific field across some number of issues?
For example: I've got around ~100 issues on the FHIRcast STU2 ballot. Commenters did a good job filling in the "Related Section(s)" attribute and I manually cleaned up the rest. I'd like to see the values used in this field for all issues in the ballot / specification in order to categorize (and delegate) issue resolution/work. Is this possible/reasonable?
In SQL, this would be a group by.
For example, here's all the issues with a "Related Section(s)" of "Conformance"
project = FHIR AND Specification = "FHIRCast (FHIR) [FHIR-fhircast]" AND "Related Section(s)" ~ "Conformance"
Lloyd McKenzie (Mar 17 2020 at 13:50):
"Related Section(s)" is an open string element - as it was in gForge. There's little consistency to how users have filled it out, though most commonly it's by section number - which themselves are pretty dynamic. The only fields that are defined as drop-downs based on specification are "Related Page(s)" and "Related Artifact(s)" - and those weren't terribly well populated historically for IGs because you were stuck with the dropdowns from core.
Isaac Vetter (Mar 17 2020 at 13:57):
Hey Lloyd! Okay. If you wanted to categorize a bunch of issues together in order to group them, and then work through them a category at a time -- how would you do that?
Lloyd McKenzie (Mar 17 2020 at 14:12):
Use the 'Grouping' element - it's a Jira Tag element so you are free to invent your own categories
Eric Haas (Mar 24 2020 at 17:46):
how to filter on 'Grouping is empty' ? is not working for me... I can't filter out the already triaged stuff using for example (Grouping not in ('a', b') or Grouping is empty)
Eric Haas (Mar 24 2020 at 17:48):
Grouping is empty is alway true
Lloyd McKenzie (Mar 24 2020 at 17:54):
@Joshua Procious Eric is right - and I'm not sure why things are working that way...
Joshua Procious (Mar 24 2020 at 18:03):
Looking into this now.
Joshua Procious (Mar 24 2020 at 18:14):
@Eric Haas can you provide the jql you're using please?
Lloyd McKenzie (Mar 24 2020 at 18:25):
Here's a simple one: project = "FHIR" and grouping IS NULL
Joshua Procious (Mar 24 2020 at 18:30):
Thank you, looking.
Joshua Procious (Mar 24 2020 at 18:49):
There are duplicate custom field entries for "Grouping". Removed duplicate. search: project = FHIR AND Grouping = waiting_for_input seems to be returning correct results now. @Eric Haas can you please verfiy?
Lloyd McKenzie (Mar 24 2020 at 19:09):
Do we know how the duplicate came to be?
Eric Haas (Mar 24 2020 at 19:10):
beautiful ... 'Grouping is NULL' or 'Grouping is EMPTY' both work as expected ...thanks!
Joshua Procious (Mar 24 2020 at 19:32):
Fantastic. You're welcome. The duplicate was associated with an old set of screens that are now set to inactive (had "-2" appended to their names) so my guess is that it came to be on one of the renames or imports from Dev.
Lloyd McKenzie (Mar 24 2020 at 21:45):
We're confident that won't be an issue for future Dev imports?
Last updated: Apr 12 2022 at 19:14 UTC
