I have the next situation. I have a Custom Field: Variant cascade selection:
Main selection: A Second: 1, 2, 3
Main selection: B Second: 4, 5, 6
I want to created a specific project context:
Main selection V1 Second: a, b, c
Main selection V2 Second: x, y, z
My question is if the old issues, the one that are opened are affected by this potential change?
That does make sense - when you put value X on a field, you expect it to stay there until someone changes it, or the value for X has changed.
You've not really said to do either of those with the context change, you've changed the list it draws values from. So the issue will retain X until changed.
We are facing this issue and now trying to find where projects have a new context, but issues have a value from the old context so that we can update the values before they are lost. I was trying to do it inline on a screen by finding fields changing values (in these cases they are set to none) and either validate the value against the current context and add a message to the user to select a valid value. I have not found a perfect option yet sans writing a behaviour that will evaluate all the fields that are in this situation and looping through them to provide a user with notification.
This all stems form: https://jira.atlassian.com/browse/JRASERVER-62455 which now we are trying to find a way to do damage control.
If anyone else has thoughts on options I would love to hear them :)
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events