Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is it normal to see "xyz(unavailable)" in single select list value when changing context of a field


I am trying to switch context on a field for a let say project A .

Example :

Earlier the field was using default context with value : One, Two, Three

Using these values, there are issues in the project A

After creating new  context, i have added values : One, Two, Three, Four.

Now if i switch it to the new context for this field, i see that the existing issue with value "One" in the edit screen show up as "One (unavailable)" and the drop down consist of "None, One, Two, Three,Four, One (unavailable)"

Is this accepted behavior? 




1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2023

Welcome to the Atlassian Community!

Yes, this is expected.  It's because you've put the issue into an unsupportable position, and Jira is trying to avoid data loss as a result.

It's easier to explain this by looking at the data behind what you have done.  Select lists work off a list of "options", and in the database the tables with all the options and contexts would add up to look a bit like:

ID Context Option's display name 
 10001  Project A  One
 10003  Project A  Two
 10007  Project A  Three
 10009  Project B  One
 10011  Project B  Two
 10015  Project B  Three
 10020  Project B Four

The important bit to understand is that the custom field actually holds the ID of the option, not the display name.

When you give the field a different context, Jira does not change or remove the data that is currently in, it offers it up unchanged, but with the warning that the data is no longer valid for this field.

That's what it means by "unavailable" - the issue currently has your field set to "10001", but that is not an option in "project B", so you can't set it on the issue

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events