JIRA Custom Field Context issue

I created a custom field(select list) called 'Type', and in Project A, I have 3 issue types, is there a way to configure 'Type' with different select list options for each issue type under Project A? Thanks

for example:

  • Issue Type 1, 'Type' with values 1, 2, 3
  • Issue Type 2, 'Type' with values A, B, C
  • Issue Type 3, 'Type' with values X, Y, Z

2 answers

1 accepted

Accepted Answer
0 votes

Hey there,

Yes this is possible via a Custom Field Context. To do this, go to Administration > Custom Fields, click the Cogwheel icon on the far right side of your custom field, select Configure.

Select the "Add new context" option. You can specify the Select List options for particular issue types and particular projects from here by adding a new context for each Project/Issue type combo. :)

Yes, But the problem is, the first time I choose Project A and issue type A,B as context, the next time, Project A won't shown in the list again, you know, I still have issue type C to configure for Project A.

Yes, this is a long-standing bug in Jira - once you've configured one project context, it drops off the list. That's fine if you're only configuring by project, but if you're trying to do project and issue type, it can become a problem.

I don't seem to have the bug report bookmarked, but I don't remember that there are any work-arounds. I think you can sort part of it out by making a context quite wide initially and then narrowing it, but that only helps with the first time you run into it and it's not ideal. Also, you can force it by putting contexts directly into the database, but that only works for schemes not currently in use and I have no idea if it works in any version above Jira 3.3

@Nic and @Daniel

Thank you both.

Hey there,

Ahh, I might've missed that... it seems that the contexts apply only on a per-project basis... ):
https://answers.atlassian.com/questions/41699/can-a-custom-field-select-list-have-different-options-based-on-the-issue-type-screen-it-is-used-for

Sorry that my solution didn't help. I think the only viable workaround is to have different custom fields for different value sets.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

22,745 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you