Issue Navigator view only Jira Admin can view

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2013

I have an issue similar to https://answers.atlassian.com/questions/42133/issue-navigator-view.

http://confluence.atlassian.com/display/JIRAKB/Custom+Field+Column+not+Visible+in+Issue+Navigator

I can view all columns in the project with ISSUETYPE query, however the Project Lead with Admin Role cannot view the columns added. What permission are we missing? Seems there is a view Jira Admins can view the columns fields but Project Admin & Project Lead cannot.

Example field: Discovery Hrs.

1 answer

1 accepted

0 votes
Answer accepted
darylchuah
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 26, 2013

Is not about the permission thing actually. It is actually the context set by the Custom Field that is being configure to display only in certain issue type.

As explained in here, http://confluence.atlassian.com/display/JIRAKB/Custom+Field+Column+not+Visible+in+Issue+Navigator

You will need to set the Custom Field with the global context or for all issue types. Then only you are able to view it in the issue navigator.

Alternatively, you do the following as well:

  • Include an "issuetype = " JQL clause to restrict the issue type,
  • Include a "<fieldname> is not empty" JQL clause for at least one of the custom fields, or
  • (Less practical) Include a "key = " JQL clause for every issue you expect in your result.
KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 26, 2013

So only Jira Admin can view non Global Context in that query? The project lead & project admin could not view with the queries in the alternative but my userid can. So do we have to make it Global since it is not working for them with Include an "issuetype = " JQL clause to restrict the issue type, But works for me

Suggest an answer

Log in or Sign up to answer