Some background information: * Project A hosts Epics and Tasks * Project B hosts Initiatives (Initiatives are done through epics in multiple projects, and for clarity's sake I'm only mentioning one project where the Epics are) * Epics are the child issues for the Initiatives in Project B * We want to have the Epics as Child Issues and as blocking issues for the Initiative to facilitate the use of the timeline and dependency report in Advanced Roadmaps I'm trying to automate the following: * Parent Link added by the user to an Epic in Project A* Parent is an Initiative in Project B * Add an "Is blocked by" Issue Link to the Initiative from the trigger issue I've tried the following automation in Project A: * When: Value changes for Parent Link * For: Parent * Then: Edit issue files* Linked Issues* Is blocked by: Trigger issue This does not create the link between the Epic and Initiative. I've added both of the projects as the Scope for the Automation. Any thoughts on how to get the Automation working? Thanks.

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

How to do an automation for linking issues when adding a parent between two projects?

Janne Jääskä

Some background information:

Project A hosts Epics and Tasks
Project B hosts Initiatives (Initiatives are done through epics in multiple projects, and for clarity's sake I'm only mentioning one project where the Epics are)
Epics are the child issues for the Initiatives in Project B
We want to have the Epics as Child Issues and as blocking issues for the Initiative to facilitate the use of the timeline and dependency report in Advanced Roadmaps

I'm trying to automate the following:

Parent Link added by the user to an Epic in Project A
- Parent is an Initiative in Project B
Add an "Is blocked by" Issue Link to the Initiative from the trigger issue

I've tried the following automation in Project A:

When: Value changes for Parent Link
For: Parent
Then: Edit issue files
- Linked Issues
  - Is blocked by: Trigger issue

This does not create the link between the Epic and Initiative. I've added both of the projects as the Scope for the Automation.

Any thoughts on how to get the Automation working?

Thanks.

Accepted answers

Francis Batilo_vmnw04

Hi @Janne Jääskä

Can you share us a screenshot of your Automation rule as well as the audit log of a sample test case that you've initiated?

Cheers,
Francis

All comments

Francis Batilo_vmnw04

Hi @Janne Jääskä

Can you share us a screenshot of your Automation rule as well as the audit log of a sample test case that you've initiated?

Cheers,
Francis

Janne Jääskä

Hi @Francis Batilo

Thanks for the quick reply. Here's screenshots for all of the automation rules I'm using + audit log.

Screenshot 2023-09-20 at 9.19.43.png

Screenshot 2023-09-20 at 9.19.53.png

Janne Jääskä

And the audit log, I don't know where that disappeared to.

Screenshot 2023-09-20 at 9.20.03.png

-Janne

Francis Batilo_vmnw04

@Janne Jääskä ,

Thanks for providing the screenshots. From what I've gathered, the Parent Branch feature is used for identifying the parent of a sub-task, and not the parent of custom hierarchy. The nomenclature is definitely not helpful, and I tried to it for the same purpose and found it not doing what I want.

I would suggest that you use JQL instead of the Parent Branch, check out the screenshots I have below. I've tested it and it works for what you are trying to achieve.

atcom - 1.png

I hope this helps.

Cheers,

Francis

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud