Is it possible to restrict non unassociated custom fields from issues search navigator ?

Ramesh Udari1 June 3, 2013

Hi,

We are using JIRA 5.0.2 and recently we come accros once problem in jira issue search navigator.

In JIRA issue search navigator whenever project is selected and refreshed, system will show all available customfield in system, instead of showing only assiciated customfields of selectd project. So is it possible to restirct issue navigatore to show onlyselected project associated customfields in issue navigator list.

3 answers

2 votes
MatthewC
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.
June 3, 2013

It's all a question of scope.

Ideally a custom field will only be visible to where it is being used. It makes the interface simpler and it also helps performance. Just because you can't see the field on the screen, it doesn't mean it's not there underneath the screen and still accessible to Jira.

This is what is happening when you see all the custom fields on the issue navigator.

The link Christian gave you will give the technical instructions but it's not great at explaining why or how best to do it.

You want to restrict the scope (aka context) of a Custom field (CF) as much as possible. So at the very least, go through each custom field and add a context based on project name. This means it will only appear when your search includes projects that have this custom field.

One behaviour here to watch out for is that if your search results contain a mix of projects, some have the CF and some don't, then Jira will hide the CF from your search options. So to see the CF in your search options, you will need to limit the search to the scope/context of the custom field.

I'd also recommend using issue types rather than projects to limit your scope where possible.

Having to go back to the CF configuration everytime you want to add a project is time consuming. If you the configuration is associated with the issue Type, you just have to add the Issue Type to the project's Issue Type Scheme & Issue Type Screen Scheme and you inherit the configuration.

0 votes
nidhis July 13, 2016

still all fields are visible even if the are not in the context

0 votes
Christian Czaia _Decadis AG_
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.
June 3, 2013

You'll have to set a context. That way only fields associated to aproject via the context will be shown:

https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field

Cheers Christian

Suggest an answer

Log in or Sign up to answer