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.
Thanks Marcus - that works. But I'm glad that there's a request to change this behaviour - it's a bit counter-intuitive. I will vote on the Improvement request to get this changed (JRA-9367).
Regards - Jeff Winget
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.