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

Project (or) Global Rule for "Branch Rule / Related Issues" condition?

Praveen Chitturi_dvr8ns

Hi Community,

We've a project A for Epics and Project B for Development stories.

I'm trying to setup a rule to update the epic field when the story under epic got transition. So I used "Branch Rule/Related issues" block as below. The default scope is coming as the current project where the stories exists. If I want to the epic fields based on the story fields , any best recommendation? I am currently doing that as below .

But the rule audit log showing as No related issues found.

Should I need to change scope as Global for this rule by adding both Project A & Project B as scope?

Regards,

Praveen

Accepted answers

Pramodh M

@Praveen Chitturi

Ideally, create a global automation and scope it to Project A and Project B

Let me know if it works

Thanks,
Pramodh

All comments

Pramodh M

@Praveen Chitturi

Ideally, create a global automation and scope it to Project A and Project B

Let me know if it works

Thanks,
Pramodh

Praveen Chitturi_dvr8ns

Hi @Pramodh M ,

Let me ask my JIRA admin to change the scope to Global and update you back.

Regards,

Praveen

Pramodh M

Sure @Praveen Chitturi

Praveen Chitturi_dvr8ns

It worked for me now. Thanks @Pramodh M and I'm happy to see the atlassian community support. It makes us to continue use the JIRA products in more deeper working level.

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-server

automation

jira-service-management-server