Automation rule fail

[Efe Işıkyüzlü]

I created a rule to heritage Priority Levels of User Story's to related sub-tasks. It failed and I dont understood why. Please find the details below, fail log and rule itself.

[Daniel Ebers · Accepted solution]

Hi @Efe Işıkyüzlü

is my understanding correct that it is not yet working for you?

In a team-managed project (I seem to have recognized you are using a tem-managed project) I was able to reproduce this problem - it looks like a timing-related issue and finally it was made working by the following fule (a re-fetch was brought in).

For completeness (as there seem to be several possibilities) the "Edit issue fields" action looks the following:

Regards,
Daniel

[Efe Işıkyüzlü]

Yes, this completely solved my problem, thank you very much.

[KAGITHALA BABU ANVESH · Accepted solution]

If you look at the above automation.

This is used to copy the priority from Parent(Story) to Sub-task.

You can set the default value for the priority in the actions.

Thanks

[Efe Işıkyüzlü]

hi again, my aim is copy the priority from parent(story) to sub-task also. Default value is medium but i want like that: if i create a sub-task in a Highest level story, this sub-task should have highest in default. 

[KAGITHALA BABU ANVESH]

Yes, The above-mentioned screenshot is the same.

adding the three steps below

Which copies the "Priority" from Story to Sub-task. 

[Efe Işıkyüzlü]

Could you understand why it failed then? What can I do to run it successfully?

[KAGITHALA BABU ANVESH]

Sorry, in the first answer, some information.

Please check the above, where all 3 steps are mentioned with screenshots.

By using these, you can copy the priority value from Story to "Sub-task"

[Efe Işıkyüzlü]

i did my rule in edit screen with same steps. Could you run this rule in your environment? Does it success?

[KAGITHALA BABU ANVESH]

Yes, it's a success.

Do you have any error?

[Efe Işıkyüzlü]

when i run, an error occurs in there. i did exactly same steps but there is an error, which i posted in the main question. i actually dont understand why.

[Jonas Ekström · Accepted solution]

Does your edit section look like this? If you choose copy from parent, it should work

[Efe Işıkyüzlü]

my edit section look exactly same with it. Could you run this rule in your environment? Does it success?

[Jonas Ekström]

It does indeed work without any issues

[Efe Işıkyüzlü]

an error occured in mine. i did same things (you may see in main question) but couldnt success

[Jonas Ekström]

Strange,
If you look at the workflow for sub-task, what post functions do you have on Create Issue? And in what order?

[Efe Işıkyüzlü]

I regenerate the rule with oen of my colleague with your steps from zero, same problem occured again. 
Then; to understand the reason of problem, i changed my case. I created a rule with same way, but not use priority that time, i used assignee. When i ran that rule, it seems succeed in activity logs, but it not heritaged actually. I wish i have a screen sharing call with you.

[Jonas Ekström]

What if you try to change the trigger from on create, to be a manual trigger? 
You should be able to trigger that automation from the sub-task and observe what happens

[Efe Işıkyüzlü]

i changed the trigger "manuel trigger" as you said and run my rule for a story which have 2 sub-task but there is no action also. 

Then i tried to run that rule in sub-tasks itself and it works but that is not helps to improve my process. 

Let me share my main problem:

When i create a story with high level priority and 10 sub-task in it; i must go inside each 10 sub-task and reselect their priority level from middle to high. If i use that rule in that way, i must go inside that 10 sub-task again, so it doesnt automate anything for me. I should run this rule in parent level. I want an automation that will run in that story and all 10 sub-task will be selected as high priority level. 

[Jonas Ekström]

That makes sense, the rule you described in the first place should take priority from parent when a sub-task is created. Which is why it works when executed from a sub-task but not it's parent. 

Running the rule manually was a way to identify if there is an issue with the logic of inheriting the value.

The sub-tasks you create, are those created by automation or manually?

There is something strange with the way you try to do it right now, as it works when I try the scenario.

Can you describe the order in which you do things? (Order of creating issues)

[Efe Işıkyüzlü]

Greetings again. No, I did not create the tasks with automation.
To describe the process I did, in order:
At first, I create a high priority level story. Then I create a sub-task by pressing the "add a child issue" button inside the Story page. This sub-task is created as medium priority level by default.

[KAGITHALA BABU ANVESH]

Hi @Efe Işıkyüzlü ,

according to the above screenshot.

You need to specify the field values 

Thanks

[Efe Işıkyüzlü]

first of all, thanks for your interest. It said that i need to fill it with a string but its a chosen value from drop-down list. How can I specify it?

[KAGITHALA BABU ANVESH]

Do you wish to copy the priority values from Story to "Sub-task" or something else.

Can you please provide more inputs?

[Efe Işıkyüzlü]

I aimed that: When i create a sub-task in a story or bug (via "Add a child issue button" etc.), this sub-task's priority level should be same with its parent's priority level. In default, system assign medium level to them, i try to ease my team's effort on re-adjusting it.

[Efe Işıkyüzlü]

@Tansu Akdeniz benzer bir konuda cevap bulduğunuzu gördüm, müsaitliğiniz olur da bakabilirseniz sevinirim :)