Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

making a field visible based on some condition

gil
Contributor
July 29, 2013

I have a JIRA screen configuration which is shared with multiple JIRA projects. One one project, I want to show a new custom field but it should not appear on rest of the project. I try to avoid creating another screen configuration. Is there a way to make a field visible only to this particular project, or another best practice to handle such situation?

3 answers

0 votes
Ravi Sagar _Sparxsys_
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.
August 4, 2014

Without creating separate field configuration or screen scheme, this can be achieved simply by using Custome Field Contexts.

0 votes
Nic Brough -Adaptavist-
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.
July 29, 2013

It depends on your *exact* requirements, but if your need is what I think you've said, you've got three options.

I think you have a custom field that should only appear in project X, although you've got projects X, Y and Z. This is exactly what the schemes are for, and you can choose between:

  1. Having a separate set of screens for project X
  2. Having a separate "field configuration" for project X (in there, you can show or hide different sets of fields.
  3. In the custom field context, you can say "only project X" instead of "global"

On points 2 and 3, the important point is that you still put the field on screens. For a field to appear within a project, it has to match ALL three criteria.

The best practice is a little difficult to define, there's several factors in which methods will work best for you and your users.

0 votes
Justin Leader July 29, 2013

You can have different issue types, and only allow the field to associate with certain issue types by using field configurations. That is the easiest way to do this that comes to mind.

Suggest an answer

Log in or Sign up to answer