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 can I create sub-task in project A (Feature) when project B (story) status changes?

Steven Johnson_e13aja

I am trying to create a sub-task in a Feature when a story in that Feature moves to "Done". The Feature and story are in different projects and I do not have global admin rights, nor will any global admin set this up or change any of our policies, so I have to work around the constraints.

I have tried branching with the "Epic (parent)" branch in the project that contains the story, so when the status changes, it would look into that branch (the Feature) and make the changes, but I assume that is not working since they are in separate projects.

So the other way I have tried is to just create the link (rather than just containing the Feature link in the story), and use the "Link issues" action in the story project, and I link to the Feature. Then in the Feature automation rules, I am using the "Issue linked" trigger and allowing the rule to allow other rules to trigger. When I mark the story done, the link is created between the two, so it is added to the Feature, but I can't figure out why the rule is not being triggered.

Any idea why the trigger would not be tripped, or possibly another way to accomplish what I am trying to do, given my constraints?

Thank you!

Accepted answers

Trudy P Claspill

The Issue Linked trigger is triggered for the issue that gets the Outward Description portion of the link.

If your link is Screen Shot 2023-08-16 at 5.24.19 PM.png

if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B.

If you looked at the details of ISSUE-B you would see under the Links section:

blocks

-- ISSUE-A

The Outward Description (blocks) of the link relationship appears in ISSUE-B's details, so the triggering issue for the rule is ISSUE-B.

The link you create between the story and the feature needs to result in the Feature issue details showing the Outward Description of the link relationship.

All comments

Trudy P Claspill

The Issue Linked trigger is triggered for the issue that gets the Outward Description portion of the link.

If your link is Screen Shot 2023-08-16 at 5.24.19 PM.png

if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B.

If you looked at the details of ISSUE-B you would see under the Links section:

blocks

-- ISSUE-A

The Outward Description (blocks) of the link relationship appears in ISSUE-B's details, so the triggering issue for the rule is ISSUE-B.

The link you create between the story and the feature needs to result in the Feature issue details showing the Outward Description of the link relationship.

Steven Johnson_e13aja

So essentially I can't trigger from the Feature if the link is being added from the story project's side?

I am also trying to use the trigger of "Issue Updated", so when the link is added to the feature, it actually changes the "updated" date in the Feature, but even though the date changes, it does not trigger the rule. Any clue how I can trigger when that Updated date changes, since it doesn't seem to catch the date change when it's not directly something edited within the feature itself?

Steven Johnson_e13aja

So I could not use the "requires"/"prerequisite of" option since, even though it says that either would trigger, it was only looking for "requires" on the Feature side. So I tried the "relates to" since that is the same verbiage on both sides, and it worked.

It's not the cleanest way to do it, but it'll work for now, so your answer got me thinking about trying it this way.

Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server