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

[Meck]

Hi Afsoon,

You can do it. Read more here: https://confluence.atlassian.com/adminjiraserver071/associating-issue-types-with-projects-802592389.html

Regards,
Lameck.