We are trying to use next-gen projects and have a couple of questions.
1. Is it possible to make a context field mandatory (doesn't seem to be). We need to ensure that some fields are always filled in on new issues
2. If a context field had (say) 6 possible values today and then next week I didn't want anyone to use one of the values and deleted it, would it be deleted from any existing issues which had that value or would it only not be available for new issues. We wanted a way to have a fluid list of possible values dependent on where we are in the project but don't want to lose historical information.
Hi Karen, a solution for #1 could the use of transition 'Rules' in the workflow.
For example, I ask users to provide a reason when they transition a ticket to the ON-HOLD status.
Not sure on #2, should be easy to test though.
Hi Atlassian Community, My name is Avni Barman, and I am a Product Manager on the Confluence Cloud team. Based on feedback from you, we are giving admins more power to create templates that a...
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