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 find sibling story with same epic

Jim Ralston_2y1hgg

I have situation in which i have multiple user stories that have already been created under a single epic.

Desired behavior: When user enters value in one custom field in a child story, and then sets status of that story to done, copy the value for that custom field to same customer field for another 'sibling' story with the same epic, where the 'destination' story has a particular summary value.

However, it seems that automation engine can't identify the sibling story. What is the correct JQL/smart values to do this?

Screen Shot 2022-10-11 at 4.22.55 PM.png

Accepted answers

All comments

Jack Brickey

Can you share the details of your"Then: edit issue fields"? Are you copying the value of the Field from the issue triggering the event? Also are you getting errors in the audit log? Can you share?

Bill Sheboy

Hi @Jim Ralston

Adding to Jack's questions...

Would you please post an image of the audit log details showing the rule execution? That may provide some context for this symptom. Thanks!

Kind regards,
Bill

Jim Ralston_2y1hgg

Thanks much for your help.

Please see screenshots attached: a) audit log; b) Story KYC, the "source", see field Doxxed with value 'xyz'. I set this one to "Done" to trigger the copy/paste; c) Story 'Dev', the "destination", see field Doxxed with value null. These two stories share common epic link, as per d) epic

Screen Shot 2022-10-12 at 11.45.22 AM.png

Screen Shot 2022-10-12 at 11.50.42 AM.png

Jim Ralston_2y1hgg

Sorry - i think these are out of order now -- here's the audit log

Screen Shot 2022-10-12 at 11.43.20 AM.png

Jim Ralston_2y1hgg

Apologies Bill - I've tried multiple solutions so i must have munged up the data.

Here's the situation:

I have an epic (OP-903) for a piece of work, and it has multiple child stories (e.g., OP-904, OP-905), representing each different piece of the work. One person works OP-904, gets some info, writes that to the Doxxed field, and then sets status to Done, signifying that their work is done. The consumer of that Doxxed info works a different ticket, OP-905, so I want to automatically copy the value of the Doxxed field from OP-904 to OP-905 when OP-904 is Done.

Screen Shot 2022-10-12 at 2.17.24 PM.png

Bill Sheboy

Thanks, and let's try this again...with some extra condition checks for insurance :^)

First question: will the child stories *always* have that text of "KYC" and "Dev", or are those subsets or examples of text? Let's assume they only contain those values.

trigger: issue transitioned to Done
condition: issue type is Story
condition: summary contains KYC
branch: on JQL of... parent = {{triggerIssue.parent.key}} AND summary ~ "Dev" AND status = "Backlog" AND "Doxxed" IS NULL
- action: edit issue to set Doxxed with "Copy from Trigger Issue"

Next question: can issues ever move "backwards" in flow, from Done to earlier steps? If so, what should happen?

Another question: is there always a 1-1-1 relationship between the Epic, KYC, and Dev stories? If not, what other patterns are there to handle?

Jim Ralston_2y1hgg

Thank so much...i really do appreciate all your help. I think the smart values you provided (esp. parent = {{triggerIssue.parent.key}}) will do the trick.

To answer your questions:

The summary names/values will remain constant. I used shortened KYC (aka "Know Your Customer") and Dev ("Contract Development") for my toy test problem, but the fuller names will always be the same

Its possible, but unlikely, that the issues will move backward in the flow. Since we're a small operation, and its unlikely, I can handle those with ad hoc manual fixes.

And yes, there will always be that 1:1:1 relationship, between epic, kyc and dev stories.

Now, let me try your suggestion!! :-)

Jim Ralston_2y1hgg

Ugh -- Didn't work. I thought for sure that this would work.

Screen Shot 2022-10-12 at 4.15.52 PM.png

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