While Moving issues from Project A to Project B i want the new field to be created in Project B
Asked by 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.


Answers:
author: Charlie Gavey
body: Hi [@SURESH G](/t5/user/viewprofilepage/user-id/4575776)  

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.

![Screenshot 2021-11-10 at 10.44.01 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/168639i6BBBC5DA91FCB267/image-size/large?v=v2&px=999 "Screenshot 2021-11-10 at 10.44.01 AM.png")

Hope this helps!  

Cheers,  
Charlie

comments: author: SURESH G
body: Many Thanks [@Charlie Gavey](/t5/user/viewprofilepage/user-id/4622713) i will test this out


author: Curt Holley
body: Am I right in thinking you only want the field to be mandatory when an issue is "moved"?  
That could be tricky. [@Grigory Salnikov](/t5/user/viewprofilepage/user-id/1323725) suggestion is correct for making a field mandatory, but that will mean the field always needs to be populated.


author: Grigory Salnikov
body: Hi [@SURESH G](/t5/user/viewprofilepage/user-id/4575776) and welcome to our community!

![welcome.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/168286i5F81C819859ED1AF/image-dimensions/402x279?v=v2 "welcome.jpeg")

Please have a look at the following workaround:

[Make custom fields required in a workflow transition in Jira server](https://confluence.atlassian.com/jirakb/make-custom-fields-required-in-a-workflow-transition-in-jira-server-691011903.html) {#toc-hId--1211265907}
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

comments: author: SURESH G
body: 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


author: Curt Holley
body: 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.


author: SURESH G
body: Yes this might solve my issue will check and update the status   
Many Thanks