Stream: JIRA/Confluence
Topic: Finding Jira issues for a spec or IG
Josh Mandel (Feb 08 2022 at 23:27):
If I'm viewing an issue like FHIR-28468
and I see:
How can I "pivot" to seeing all issues associated with this specification? The name isn't a link, and the JQL builder doesn't auto-complete names:
and manually copying names doesn't work:
Specification = "SMART Web Messaging (FHIR)"
^^ finds no results.
Richard Townley-O'Neill (Feb 08 2022 at 23:40):
Try looking for it in all text
https://jira.hl7.org/browse/FHIR-28471?jql=project%20%3D%20FHIR%20AND%20text%20~%20%22SMART%20Web%20Messaging%20(FHIR)%22
Richard Townley-O'Neill (Feb 08 2022 at 23:41):
Josh Mandel (Feb 08 2022 at 23:43):
This finds 22 items -- it's missing most of the 81 issues on that spec (e.g., FHIR-29360), and it has some extras that don't belong (e.g., NEWID-2866).
Josh Mandel (Feb 08 2022 at 23:43):
The "right" answer appears to be a JQL expression like:
Specification = "SMART Web Messaging (FHIR) [FHIR-smart-web-messaging]"
but I had to "cheat" to find this, by looking on a dashboard that I happen to have access to for SMART Web Messaging, and I don't know how to do this for other specs where I can't cheat.
Notification Bot (Feb 08 2022 at 23:54):
This topic was moved here from #IG creation > Finding Jira issues for a spec or IG by Lloyd McKenzie
Lloyd McKenzie (Feb 09 2022 at 00:00):
I figured this was a better place for the discussion.
Jira doesn't support pivoting. The simplest way for someone to come up with the query is to indicate that they want a new search, select the FHIR project, select all 4 issue types, select "More" and choose "Specification" and then select from the dropdown. The need to choose project=FHIR first is because the set of specs varies by project. The need to select the 4 issue types first is because the plugin we use to allow the list of specifications to be dynamically adjusted based on what's committed to JiraSpecArtifacts wants it that way and I've found no way to get around it.
Josh Mandel (Feb 09 2022 at 00:03):
Thanks! I don't think I would have ever discovered this because I never would have selected all four issue types because it doesn't feel like part of my goal.
Lloyd McKenzie (Feb 09 2022 at 00:10):
Yeah, it's not intuitive. I did include it in the documentation though: See here
Some fields that may be useful to search on (e.g. Related Artifact(s), Related Page(s), etc.) may not be selectable unless your search explicitly filters on Issue Type. That's because these fields are constrained to only be enabled for certain issue types. If you filter and select all four issue types (Proposal, Technical Correct, Question and Comment), you'll avoid constraining out any issue types and will be able to filter by the restricted fields
'Specification' is one of those fields.
Richard Townley-O'Neill (Feb 09 2022 at 00:26):
I found that if you use advanced search you can use specification without filtering the issue types.
project = FHIR AND specification ~ "SMART Web Messaging (FHIR)"
image.png
Lloyd McKenzie (Feb 09 2022 at 02:39):
Yes, but you don't get a handy dropdown with advanced search.
Corey Spears (Feb 09 2022 at 08:18):
I think the Jira Search you want is
project = "FHIR Specification Feedback" AND Specification = "SMART Web Messaging (FHIR) [FHIR-smart-web-messaging]
I find if you make start with project = "FHIR Specification Feedback", the autocomplete will work with Specification. No cheating required.
Josh Mandel (Feb 09 2022 at 15:17):
Ahh, interesting -- @Corey Spears your assertion made me keep trying and I figured out that in terms of search semantics, using a lower-case s in "specification" works fine -- i.e., this search works correctly
project = "FHIR Specification Feedback" and specification = "SMART Web Messaging (FHIR) [FHIR-smart-web-messaging]"
however, in terms of activating autocomplete, you need a capital S in "Specification". Looks like a Jira bug, unless @Lloyd McKenzie is aware of a setting that we can change to improve this.
Josh Mandel (Feb 09 2022 at 15:18):
From https://community.atlassian.com/t5/Jira-questions/Where-do-I-report-a-Bug-to-Atlassian/qaq-p/797944
To report a Bug, Customers with a commercial support license should raise a support case with Atlassian Support.
Does someone here from HL7 HQ have that customer relationship with Atlassian?
Lloyd McKenzie (Feb 09 2022 at 17:11):
I expect Jira will say it's a 'feature'. Field names are technically case-sensitive.
Corey Spears (Feb 09 2022 at 17:22):
The differences in case always confused me. I had to assume it is somehow related to the difference between the column key and column display, but I have not figured out the pattern as it relates to the jql/search query and autocomplete.
Josh Mandel (Feb 09 2022 at 17:29):
It can't be a feature that they're case-sensitive for autocomplete and case-insensitive for search....
Lloyd McKenzie (Feb 09 2022 at 17:38):
@Joshua Procious Do you want to file an issue? (Not that I'm optimistic about a fix anytime soon...)
Joshua Procious (Feb 09 2022 at 20:44):
@Lloyd McKenzie @Josh Mandel Yes, I have the relationship with Atlassian to create the issue with them. I'm doing so now.
Josh Mandel (Feb 09 2022 at 21:27):
Thanks
Last updated: Apr 12 2022 at 19:14 UTC
