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
We're using Jira Data Center 9.1.1
A department has the following workflow:
The problem we're trying to solve is there is a field in the issue - call it 'Mandatory_Field' - that the test team need populating.
Because this is as 'issue-move' operation and not an 'issue-transition' one, we're struggling to find out how to make this field mandatory (i.e. is populated / is not empty) during the issue-move operation.
Does anyone know if this is possible? For example, could some configuration do either of the following:
You can't do validation on issue moves.
You have a much bigger problem here - your process is broken. Moving an issue from one project to another is never part of a process, it breaks so many things.
You need to revise your data structure - your projects sound like they are aligned to teams, which is not the right thing to do for you. The "assign issue to test team" should be part of the workflow, not done by project.
Why not add a Validator to the transition in the Dev team project workflow to require the field be populated before moving it to ready for test?