Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,561
Community Members
 
Community Events
176
Community Groups

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

Atlassian Community Events