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!?!?!? :-)
Hi Vijav,
In my organization(huge bank, north america) we are using Agile Cards for Jira (Spartez) and it's working well! I'm not saying other plugins are better or worse but I can tell you that we've never been disappointed with the plugin. The new "project template" feature can even print cards in different formats for different project based on templates! We are convinced it's a good product and I would definitely recommend you to try it out!
Cheers
@miikhy Thanks for the mention!
@Vijay Reddy Adrian from the Agile Cards team here. 👋
As your decisive driver is solving the problem of synchronisation of physical and digital boards, perhaps the following blogposts will provide you with some better context on how it can be achieved using our app -
Also, feel free to book a time with us if you would like to have an introductory demo. 👍
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.