nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Notification when there is a status change (linked issue project)

Barış Özer

Hello,

We made an automation as follows. @Trudy P Claspill thanks thanks

I would like to add the following rule to this automation.

@Trudy P Claspill

Can we write a rule regarding "status" changes in the automation you showed me?

((Can we notify the Service Desk when the "status" changes in the INF Project?

Example:

In INF Project status = Backlog and
After a few days, when status = In Progress, will the Service Desk receive an update regarding the status change?))

Accepted answers

Trudy P Claspill

Hello @Barış Özer

What do mean exactly by "notify"?

Do you want a comment added to the linked SD issue that says the status on the INF issue changed?

Rules are triggered by events. The other rule is triggered by a Comment being added. You can't add a second trigger to that rule to take an action based on a different event.

There is a Issue Transitioned trigger that you can use to trigger a rule when the status of the INF issue changes. That will have to be a separate rule from the other rule.

This new rule will need to be a multiple projects scoped rule, like the first one.

You'll need to have a condition in it to check the project of the triggering issue, like we had suggested in the first iteration of that other rule.

Why don't you make an attempt to construct that rule and show us what you come up with?

All comments

Trudy P Claspill

Hello @Barış Özer

What do mean exactly by "notify"?

Do you want a comment added to the linked SD issue that says the status on the INF issue changed?

Rules are triggered by events. The other rule is triggered by a Comment being added. You can't add a second trigger to that rule to take an action based on a different event.

There is a Issue Transitioned trigger that you can use to trigger a rule when the status of the INF issue changes. That will have to be a separate rule from the other rule.

This new rule will need to be a multiple projects scoped rule, like the first one.

You'll need to have a condition in it to check the project of the triggering issue, like we had suggested in the first iteration of that other rule.

Why don't you make an attempt to construct that rule and show us what you come up with?

Barış Özer

Hi @Trudy P Claspill

Actually I want to do this.

How can we transfer the status change within this automation we have made?

Maybe as a comment?

If we do a different automation, we use too much automation. I don't actually want this.

Can we do this for this automation?

When the status changes in the INF Project, write a comment to the SD project.

For example;

For example, when the Backlog status is In Progress, I want it to say = status changed In Progress.

How can we auto-comment the SD project?

Trudy P Claspill

Hello @Barış Özer

It is possible to create an automation that is triggered by any one of multiple events, but Issue Commented is not one of the events that can be combined with others in a trigger.

Screenshot 2024-04-05 at 10.26.20 AM.png

You will have to create a separate rule. You cannot have a single rule that is triggered by both a new Comment and by a status change.

The calculation of rule executions is not based simply on the rule being triggered, but on whether or not the rule then executes a meaningful action. If you use Conditions in the rule to determine if it should proceed with the Actions, and if those Conditions are not met, then the rule does not count as being executed. Refer to this for more information:

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Does that address your concern about too many rule executions occurring?

The alternative to an automation rule for this requirement would be to look at a third party app that would let you extend the Workflow capabilities so that you could add a script to the status transition directly in the workflow. You would then have to write an appropriate script to execute all the checks and then post the comment.