how2 enforce a field is populated during an issue-move from Project A to Project B

[Darren]

We're using Jira Data Center 9.1.1

A department has the following workflow:

• an issue is created in the dev team's Jira Project ('Source Project')
  • the dev team work on the issue and eventually transition the issue to status = 'ready for test'
• then the dev team give the issue to the testing team by moving it to the test team's project ('Target Project')
  • (the workflows are aligned: status = 'ready for test' appears in both projects' workflows)

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:

• Either prevent the Source Project issue-move operation from being initiatiated unless the Mandatory Field != empty
• or the Target Project refuses to accept incoming tickets (from an issue-move operation) unless the Mandatory Field != empty

[Nic Brough -Adaptavist-]

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.

[John Funk]

Hi Arnold,

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?