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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.