While Moving issues from Project A to Project B i want the new field to be created in Project B

[SURESH G]

While Moving issues from Project A to Project B i want the new field to be created in Project B and it that field should be mandatory.

while moving issues from project A to Project B i want to create a new field called "Reason for change" and i want this mandatory. so that i will know the main reason why they are moving the issues.
i want to know how this can be Possible.
Thanks in advance. 

[Charlie Gavey · Accepted solution]

Hi @SURESH G

Just adding to Curt's suggestion above, you could include a condition in your rule to check whether the "Reason for change" field has been populated, and if not, trigger appropriate notifications to encourage users to complete this field.

I've attached a screenshot as an example of how this might look.

Hope this helps!

Cheers,
Charlie 

[SURESH G]

Many Thanks @Charlie Gavey i will test this out 

[Curt Holley]

Am I right in thinking you only want the field to be mandatory when an issue is "moved"?
That could be tricky. @Grigory Salnikov  suggestion is correct for making a field mandatory, but that will mean the field always needs to be populated.

[Grigory Salnikov]

Hi @SURESH G and welcome to our community!

Please have a look at the following workaround:

Make custom fields required in a workflow transition in Jira server

[SURESH G]

I appreciate your response.
what exactly i am looking is. when user move an issue from Project A to Project B then i want a field in Project B to be mandatory ( I want field required only when move issue is performed).

Or another possible case i am expecting is " when user move an issue from Project A to Project B then i want to ask for a comment in that case user have to update the comment.( so that i will know what exactly is the reason for moving issue to target project)

Thank you

[Curt Holley]

Hmmm, not sure if that can be achieved.

But, what you could do is have an automation rule where whenever anything is moved into Project B, a comment is added saying who moved it and an email could be sent to the initiator (of the move) reminding them to add a comment explaining the move.

Not perfect, but a relatively easy option that would (hopefully) encourage the desired behavior.

[SURESH G]

Yes this might solve my issue will check and update the status 
Many Thanks