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
Next: Root
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.
I want to be able to make some fields be mandatory when an issue is moved from Project A to Project B. Does anyone know a way to do this ?
Thanks,
Fiona
Hi @Fiona Brown
Welcome to the community!
You need to set field as required in Field Configuration Scheme. During moving issue Jira will mark this field as required to fill.
Hope it will help you!
Regards,
Sushant Verma
Thanks but I only want these to be mandatory when they come from the other project not when raised as an issue in the project.
The use case is L2 support team need to add details of triaging steps before they move the issue to L3 team's project
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Fiona Brown If you have defined required custom fields for your issue that do not exist in your target project, you must set values for them. You will only be prompted to enter the values for required custom fields in the target project that are missing values. If the custom fields of your original project also exist in your target project, and these custom fields are not required in the target project, you may need to set values for them, to move the issue successfully. If you wish to change the existing values for other fields on your issue, you can do this after the move is complete.
Regards,
Sushant Verma
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.