My Rule does not show up in issue when clicking automation -> Rules execution

[Rajesh Patel]

I just created a new rule which will change due date of a dependent task when a due date of a main task is changed. When I went to dependent issue and tried to apply the rule using Automation and Rules Execution it shows the following. So the rule I created is not appearing there so that I can apply to this issue. Please help

Recent rule executions

No executions recorded against this issue yet.

[Mikael Sandberg · Accepted solution]

Hi @Rajesh Patel,

Welcome to Atlassian Community!

It is only manually triggered automations that will show up there and any automation that was triggered by the issue. If your automation is set to manual, make sure that you belong to the group that you configured the automation to be visible for. 

[Rajesh Patel]

How do I set automation to manually trigger? I am doing this first time, so a naive question? Thanks for a quick reply.

[Rajesh Patel]

BTW, I belong to the group for which the rule I have created. In addition, I also have admin privileges that I acquired recently. In addition the rule is enabled.

[Rajesh Patel]

When I manually changed the date, the rule showed up. However the date is not updated. I don't know how long it takes to update the date.

[Mikael Sandberg]

Use the manual trigger from issue option to make it show up under Automations on the issue.

[Trudy Claspill · Accepted solution]

Hello @Rajesh Patel 

What do you want your rule to do?

Do you you want the rule to run automatically based on another event, like a field in the issue getting updated?

Do you want the rule to run only when a user manually clicks a button that executes the rule?

If the rule is not updating the issue the way you expect, please show us screen images that show all the steps in the rule. Also from the Audit Log tab for the rule find the log entry for the execution of the rule, click the Show More link, and provide us with screen images showing the messages recorded during the rule execution.

[Rajesh Patel]

Ideally I want autoupdate when a due date for a task is changed. I have created a dependency between two tasks as "is duplicated by" as both tasks needs to move together with a same due date.

But for now I want to test the rule if it working properly or not as I am creating the rule first time and so want to run manually. Here is the rule.

[Rajesh Patel]

On the task where I expect to see due date update, I see the following in the automation rule, and it says Rule "No Action Performed"

[Rajesh Patel]

I suppose at this moment I am having an issue with "NO ACTIONS PERFORMED". So the rule is encountering error during execution:

1. I have Task A and Task B linked.
2. I want Due Date for both tasks to be same.
3. I want Task B Due Date automatically updated when Task A due date is manually changed.
4. I have Task A linked to Task B as "as Duplicated By".
5. I have Task B linked to Task A as "Duplicates".

6. I change due date of Task A, I see Rule Execution occur with error NO ACTIONS PERFORMED at Tasks A. I go to Task B, I see Rule Execution occur with same error NO ACTIONS Performed.

7. I change due date of Task B, just for testing, Tasks B shows Rules Execution with same error. Task A however in this case, do not show Rule Excecution.

8. Once I get over the error, I can modify links as I needed. Thanks for your help.

[Rajesh Patel]

I finally got the action to perform, but now Due Date of the destination task is whipped out instead of updating it. Please help.

[Trudy Claspill]

Please show us the current definition for your rule, and show us the details from the rule Audit Log for the execution of the rule that wiped out the Due Date value.

[Rajesh Patel]

Sure. I just updated a Due Date for the task highlighted in Blue at the bottom and you can see the Due Date for task highlighted in Grey was whipped out. Next message I will show my rule.

[Trudy Claspill]

Please provide screen images that show us the current configuration for your rule, since your previous responses indicate you made changes after the last screen image you listed.

Additionally, with each Automation Rule there is an Audit Log. Each time you change and publish the automation rule and each time the automation rule runs an entry is made in the Audit Log. Each entry can be expanded to show the details related to that rule change or execution. Please show us the details from the rule Audit Log for the execution of the rule that wiped out the Due Date value.

[Rajesh Patel]

This is the current configuration of the rule.

[Rajesh Patel]

This is the audit log

[Mikael Sandberg]

How is the edit due date step configured? If the due date is cleared out my guess is that the value you are setting it to is empty.

[Rajesh Patel]

Sorry, Here is the audit log. It says the change was around 3 hours ago. So per my time this would be a 12:02:56 Success event. My guess.

[Rajesh Patel]

Hi Mikael, No there is value and when I move one date the other gets whiped out. Just be sure. I done this again and saw the Due Date is cleared. See two items it shows in the audit log that cleared the Due Date,

[Rajesh Patel]

Here you go one more time Before:

[Rajesh Patel]

Previously Due date set to 12/04. Now after I change due date of the trigger task as in the below:

[Trudy Claspill]

@Rajesh Patel 

Please show us the details of the Audit Log entry for when the rule was executed. You need to click on the Show More link to display those details.

Please show us the details of the step in the rule where you are setting the Due date field.

It is possible that you have not provided the correct information in order for the Due date field to be set.

[Rajesh Patel]

This is the logic I have:

[Rajesh Patel]

Got it. I just created a fresh event and it showed 3 entries on the task where Due Date is whipped out. See below.

[Rajesh Patel]

The Task where the Due Date got whipped out is task 593. 

The task where I changed the Due Date is task 6062.

[Mikael Sandberg]

You need to uncheck the "Only include issues that have changed since the last time this rule executed" on the branch component, otherwise it would only update linked issues that have changed since the last execution. If you leave it checked you will end up with scenarios like the one here where 593 is not updated because it hasn't been updated since the last time.

In the edit issue component on the rule, what are you setting the due date to? Are you using a smart value? If you include a screenshot if the set up of it we can figure out why the due date is cleared out.

[Rajesh Patel]

I did uncheck "Only includes issues...", but same result, Due Date is wiped out. 

I am going to include two screen shots before and after updating due date. Basically I am moving the timeline bar (Gantt timeline) to change the due date.

[Rajesh Patel]

After I moved the gantt bar.

[Trudy Claspill]

@Rajesh Patel 

We have asked you multiple times to provide the details of the step in the rule where you set the Due date.

Please click on this step in the rule flow.

The details of the step will display to the right. Provide us with a screen image of the details that display to the left. For example:

It is very likely that you are providing the rule with invalid information for setting the Due date field and that is why the field gets cleared. But we can't advise you that without seeing exactly the information you are trying to put into the Due date field.

[Mikael Sandberg]

If you can add a screenshot on the Edit issue fields, similar to this:

[Mikael Sandberg]

We need to know what you are doing in that step in order to help you further.

[Rajesh Patel]

Got it and sorry about missing the message. Here it is.

[Rajesh Patel]

Basically I using choose fields to set and when I click a drop down appears and I select Due Date, which is one of the field we have. You can see the Due Date field in previous screenshots that I provided. Attached is the remaining things I see, but I am not selecting them.

[Rajesh Patel]

I think it needs to copy value from trigger task as supposed to edit the value??? Thoughts? How does it know to edit with what value? Just my guess. 

[Rajesh Patel]

I realize that I need to copy value from Trigger Task.Due Date to Destination Task.Due Date. I am not sure what I am doing is accomplishing that.

[Trudy Claspill]

The reason the Due date field is being cleared is 

1. You selected it from the Choose Fields drop-down list and then,

2. Did not actual put a value into the field to be inserted into Due date.

Notices the input field where it says "e.g. {{now.plusDays...}}"? And directly above that is the text Due date? The presence there of Due date is telling the rule you want to set the field. The "e.g...."text is an example of a value you would use to set it. But you didn't provide a value so the rule is clearing the field in the issue.

If you want to set the field to the same vale as is in the trigger issue you would use the smart value {{trigger Issue.duedate}}

[Rajesh Patel]

Thank you Trudy, I will try this out later on and report back. I tried the following and it worked.

[Rajesh Patel]

Thank you Trudy and Mikael for you help! I will continue to try few more things and see how it goes. I am trying rules first time and so in a  learning curve.

[Rajesh Patel]

Guys I am back. Run into another issue. This time I want to update status from trigger issue to the linked issue. Unfortunately the status field is not in the selection, that means I need to use smart values somehow. I tried several ways but every time in the box it gives me an error. No matter what I try, Save button does not become blue. 

I know, I have not selected field this time, so how do I select a field and then copy the value from triggerIssue.Status using Smart Value? Please help. Thanks.

[Trudy Claspill]

First you should use the Issue Transitioned trigger rather than the Field Value Changed trigger. That allows you to control more specifically the transitions for which you want to trigger the rule.

Then use the Transition Issue action instead of the Edit Issue action.

If you have more questions about different rules, please start a new Question post.

And please consider marking one or both Answers on this post as Accepted, since we have addressed the original question in this post about manipulating the Due Date value on dependent issues via automation.

[Rajesh Patel]

Thank you Trudy. I did accept both answers and will open a new thread for a new issue.