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

Can Project Automation be used to move Story to a certain status ?

Aisha M

I have the below set of Epic workflow statuses, (All global status)

Backlog -> Analysis > Planning > Planned > Working > Delivered

So, when an Epic issue moves up from ' Working' to any other status above (like, Planned, Planning, Analysis, Backlog), all stories associated with the Epic, which is in 'Working' status should be moved to 'To-do', except for the Done stories.

How to achieve this ? Can Project automation be used ?

Thank you

Accepted answers

Callum Carlile _Automation Consultants_

Hi @Aisha M

Yes this can be done using an automation rule (see below)

So when a task is moved from WORKING > [any other status], IF said task is an epic issue type, then for all unresolved stories within that epic which are in a status of Working, they will be transitioned to To Do.

Hope this helps!

All comments

Callum Carlile _Automation Consultants_

Hi @Aisha M

Yes this can be done using an automation rule (see below)

Hope this helps!

Aisha M

Hi @Callum Carlile _Automation Consultants_ Thank you for the comment.

We have the below hierarchy,

EPIC > STORY

So, can this set up be used, if an EPIC is moved back from "Working" to any other above status, I want all the STORY that is in "Working" to go back to "TO DO"

Callum Carlile _Automation Consultants_

@Aisha M Yeah that's correct, I actually tested out this rule before posting and here's what it looks like:

Epic and 2 of it's stories are in status WORKING

After Epic is transitioned to something else (in this case, PLANNED), ONLY it's 2 stories in WORKING are transitioned to TO DO, all other stories/tasks remained unchanged:

Aisha M

@Callum Carlile _Automation Consultants_ Thank you so much ! This works amazing !

Aisha M

@Antoine Berry Hi Do you think this can be achieved using the workflow ? The automation seems to happen with a lag . . .

All the workflow transitions are global, so dunno where & what to add to the workflow for this requirement . . But we have below validator as below for checking a field when an Epic moves up from working.. Should something like below or a post function be used ?

eg,

def LastTransitionBean = changeHistoryManager.getChangeItemsForField(issue, "status").getAt(changeHistoryManager.getChangeItemsForField(issue, "status").size() - 1);
String LastTransitionFrom = LastTransitionBean.getFromString();
String LastTransitionTo = LastTransitionBean.getToString();
log.debug("LastTransitionFrom :${LastTransitionFrom} LastTransitionTo :${LastTransitionTo}")
log.debug("Last Transition Action :${LastTransitionTo}")
log.debug("Current Transition Action : ${actionName}")

if(LastTransitionTo == "Ready & Planned" || LastTransitionTo == "Working")
{
//Check for field-

Aisha M

@Antoine Berry LOL, I think you accepted my above comment as answer by mistake

Antoine Berry

Hi @Aisha M Are you sure it was me ? This is the first time I open this question

Anyway yes this is probably possible with a script. To be honest the above solution with automation seems just fine. Either way the "visual" of the status is not refreshed automatically. Automation or scriptrunner, you will have to refresh the page to see the new status.

And this requirement is probably more suited to an automation.

Aisha M

@Antoine Berry Anyway, I got a fake "accepted answer" badge for it :D:P

Yes, I know . . This is soo simple & easy . . But for some reason they want everything on the workflow ! And, since all the Epic workflow transitions are global transitions . . Really confused what kind of a post function to add to ensure the stories of the Epic which are only in "Working" are moved back to To - do .

Arrgh, just 3 more weeks before I go away from work

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

workflow

automation