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

[rashmi singh]

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? 

[Nic Brough -Adaptavist- · Accepted solution]

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