We have some projects that have lasted years, and some catalogs require maintenance. To not loose data, the preference is to add a prefix "DELETED" to those values that are not supposed to be used anymore, so we don't loose the value for old records and the new ones have a way to tell the user the option is no longer valid. We would have preferred to just "disable" the option, but that behavior is not avaialble.
What would be the groovy solution?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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