Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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. 

3 answers

1 accepted

2 votes
Answer accepted

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.

Screenshot 2021-11-10 at 10.44.01 AM.png

Hope this helps!

Cheers,
Charlie 

Many Thanks @Charlie Gavey i will test this out 

0 votes
Curt Holley Community Leader Nov 07, 2021

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.

0 votes

Hi @SURESH G and welcome to our community!

welcome.jpeg

Please have a look at the following workaround:

Make custom fields required in a workflow transition in Jira server

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

Like Grigory Salnikov likes this
Curt Holley Community Leader Nov 09, 2021

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.

Like # people like this

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

Like Grigory Salnikov likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Do you use Jira Cloud with Microsoft Teams?

Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...

533 views 1 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you