We upgraded to 5.2.7 last week and discovered what appears to be a new bug. Columns containing Custom Field data do not display after being added via Configure Columns.
Steps to reproduce:
1) display a list of issues in Issue Navigator
2) use Configure Columns; add a column representing a custom field
3) return to the Issue Navigator and note that the column you added is not displayed.
I made other changes, such as moving and deleting standard columns, and that works fine. The problem appears to be related only to custom fields.
Marcus Silveira of Atlassian answered this question.
This custom field has a project and Issue Type on it's context.
Therefore, the field will only be displayed when you filter by a Project and Issue Type that has the field.
I added the issuetype (in this case, "issuetype=SCR") to the query and the colums for the custom fields now display.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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