Automatic rule to transition Epic Status based on a Task's transitioned Status

[Kathryn Swearingen]

Hi all, 

Our Jira issues are structured like this: 

Epic -- User Story -- Tasks

There's (typically) 1 Epic per release. We use 1 User Story per 1 webpage that we're updating, then we do 1 Task per each stakeholder (ex: developer, QA, UAT; story points are recorded here). 

Most of our projects have a User Story (1) and Tasks (2; 1 for dev, 1 for QA) dedicated to Build Kit Assessment as the first User Story to be triggered. Therefore, we'd like to write an automatic rule that when the developer-specific Task is transitioned to In Progress then automatically transition the Epic to In Progress and update its Start Date field. 

We use Manual Trigger automation to create the User Story from the Epic (so the User Story is a child of the Epic). Then from the User Story we use Manual Trigger to create the dev-specific Task and a QA-specific task for assessing the build kit. We don't use Subtask.

I've written this rule, but it just won't work. I've ensured that the User Story and 2 Tasks have the same Epic Link. I have an automatic rule in place that successfully transitions the User Story to In Progress and updates its Start Date, but I just can't get that Epic to do the same. 

HELP!?!?!? :-) 

[Joe Pitt]

I believe scripting is allowed in the cloud and I believe you can do it with that. You can do it without scripting by using multiple transitions. Use a condition check to see if they answered the first question and present the desired screen for that option and in the other transition check the condition the other way and present the screen in that one you need. Only one transition will be seen by the user. I would name the transition so you can easily tell what condition it checks. 

[Olga_Popova]

If I right understand I schould do 15 different screens. I have 4 questions and 15 different combination of them. Right?