This is a very serious issue for us. (FYI - ticket and issue are synonymous, we say ticket, so that's how this is written)
I created a project for one of my teams that needed to use ticket type and sub-types. By sub type I mean I defined a multi checkbox custom field that would be used for each ticket type. Each type has its own custom field. My field configurations match the ticket type to its subtype field.
We need to be able to produce a report every month using the following JQL:
project = projectname AND created >= startOfMonth(-1) AND created <= endOfMonth(-1)
The problem is, even after adding these columns to the navigator, NONE of these checkbox fields show up in the navigator and NONE of these fields appear in the Excel file that is generated, no matter if current fields or all fields is selected.
This project has 11 ticket types. Running 11 separate filters, generating 11 separate reports, and combining them into one is WAY too much work - especially since I'd be telling a Director that this is their option.
If you have a solution - one that does not involve eazyBI Reports or any plugins that require a paid license (because, bottom line, that ain't happenin') I really could use that info.
I'm a little confused on what you've actually configured here, but my best guess is that when you say "sub type", you're referring to JIRA sub-task issue types.
If that is the case, then the problem is a long-standing design flaw in JIRA - when you're in the issue navigator, it will only display fields that are valid for all of the project/issue-types selected in the query. So, if you have a field like "colour" that only applies to "bugs" and you run a report for "issuetype in (bugs, features)", it silently drops the colour field because it does not apply to "features"
You can test my guesswork by adding "and issuetype = <one single sub-task type with the field>" - if the column gets populated, then my guess is right.
But the problem you described is not always true. For example, I have a field called "Version Status" that is only applicable to a single project. I can out that field in the navigator and I will see results for the following query:
(project = key1 or project = key2) AND "Version Status" is not EMPTY
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs