I have a cacading select field, which i want to export to excel (i am on jira 6.1)
If i use the JQL, <cascading-field-name> is not null and then export the results then the cascading field appears in my excel (i am doing export all fields)
But, if i do not pass this parameter, which means, i am returning field values which are null and not null, in this scenario, the cascading field does not get exported to excel.
How do i get round it?
Simple answer is to keep including the clause that says "not null"
The reason this is happening is a long-standing and annoying design oversight in Jira. When you define a search that includes any fields that are NOT valid for some of the project/issuetypes that could be returned by the search, it silently drops the field. Not prints it with "n/a" or blank, but completely removes the column. Even when you've got data on other issues, and even when you're not returning any of the project/issuetypes that don't have the field.
So, the answer is to limit your search to where the field is valid. It is by project and issuetype, but you are accidentally doing it by saying "field not null" as well, because that limits your selection to places that do have the field.
It's wrong, it's broken, and I've been whinging about it for a decade, and I'm not alone <sigh>
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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