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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

how to make automation rule change issue field value when issue moves

how to make automation rule change issue field value when issue moves?

i use automation rules, and choose trigger "when issue moves"

but when i move issues by more-> move or by bulk -> move 

between story 

the rule don`t recognized it.

what my options are?

1 answer

Hey @Виктория could you show us the print screen of the automation rule you have created? It will be much easier to troubleshoot it that way :)

@Marta Woźniak-Semeniuk 

both of the triggers don`t do anything.
a can see it in logs of the rule.

I move sub-task from one story to another and expected same value of parent story
Screen Shot 2022-12-14 at 09.54.47.pngScreen Shot 2022-12-14 at 09.54.17.png

What does the log say?

@Marta Woźniak-Semeniuk 
nothing the rule don`t catch any issues. the log is empty

I just realised that you said you are moving them between stories - but are you also moving them between projects? Because the "move" trigger is designed to work when you change the projects

@Marta Woźniak-Semeniuk 
no. same project.

i need when move between story or epic in the same project

Then this automation will not work. "Move" trigger catches only issues that you move between projects. 

If you are changing the parent ticket you could use trigger "issue field change" - for epic it would be "Epic Link" field.
As for the tickets under story - are this sub-issues or do you have hierarchy setting where story is also a a true parent ticket to issues? 

@Marta Woźniak-Semeniuk 
this sub-issues. just child of story.

story is parent of iisues just in structure by linkes.
but there is now the context.

we have case: when subs move story. thats all

Okay. Try trigger "When value changes for "Parent Link" and make 1st condition "And issueType = sub-task" - then proceed with the rest of conditions and actions as you had them. 

@Marta Woźniak-Semeniuk 
unfortunatly same resolt. the rule doesn`t catch it

Screen Shot 2022-12-16 at 08.24.26.png

Okay, so - I read more about it and it seems that you would need an add-on like a Script runner to make this trigger work correctly after all. 

@Marta Woźniak-Semeniuk 
could you share please a link and more info about it

Not everything can be automated with JIRA Automation and this is a case here.

Somehow JIRA can't "catch" change of the parent issue for sub-tasks.

If you still want to have it you would have to use an add-on called ScriptRunner

Can't help you with the details though, as I did not use ScriptRunner for JIRA server. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events