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; } } }

Automation: on related issue status change add comment

Katja Huss

In the legacy automation I have a rule with trigger "A linked issue is transitioned".

I do not find this in the new automation.

Using the trigger "issue transition" I have the problem, that the scope of the rule is just the Jira Service Management project. However the related issues are not in this project. I assume that this rule will not trigger then.

Accepted answers

Katja Huss

Background information: When the bug ticket is resolved then the service center worker (which are only 2 persons in my case) shall get informed. They write to the customer that the problem is solved.

All comments

Katja Huss

Background information: When the bug ticket is resolved then the service center worker (which are only 2 persons in my case) shall get informed. They write to the customer that the problem is solved.

Katja Huss

By writing this background information I found the solution myself. I create a rule for the other project and use there the "issue transition" trigger.

Katja Huss

Nope, still does not work.
The branch "For linked issues" considers only the one project

Katja Huss

Okay. I found the answer in this question https://community.atlassian.com/t5/Jira-Service-Management/Automation-Create-a-new-Global-rule-I-cannot-edit-The-Scope-of/qaq-p/1715648

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management