You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I am trying to switch context on a field for a let say project A .
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?
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|
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.