How to divide a complex workflow into an auxiliary task template?

Question

Our company moves to Jira for project management and problem solving

We have some basic uses that I am trying to create for templates. One of them is a typical problem, found and fixed, and it can be easily handled with a single problem with the jira workflow mainly turned on.

A more complex process follows the Waterfall workflow, where Requirements, including pricing, are compiled. Then "Development" is launched, and test scripts are executed in parallel. After development, the project is tested and transmitted to the client. And finally, once everything is tested, we will release the change and re-testing. In total, I have 30 different steps, built on 5 subtasks (however, this is all just drawn in Visio, not in jail).

Sub-tasking, I hope, can accomplish 2 things. Firstly, we want to track the time of discoveries and efforts (hours of work and days). And we must divide the workflow into several people so that the developer can work, while the tester can build his testing plan. This can save a few days, but this is not an interruption of the transaction.

So, a few questions that I hope will help make this possible, although I am completely new to various additions to Jira, I have no idea if we will get everything we want.

1, Is there an add-in that creates subtask templates, since each subtask needs its own workflow. Currently, the rules for Jira are to assign a workflow based on Project + Issue Type. Therefore, I believe that for each subtask I can create a suitable part of the workflow by creating many types of problems, such as "Custom-Dev-Analsys" for the subtask called Analysis

2, is it possible to have only 1 or more of all subtasks that are “current”? When the problem starts, the first subtask should work only one, and only one of the steps is assigned to someone. After signing, there should be 2 subtasks, development and creation of test scripts. But all 5 subtasks should not start from the very beginning, but it seems that this is what Jira will do. I looked at the Structure add-in, and although it has an unlimited hierarchy, I don’t think it will allow sub-tasks to open in order. There may be a simple way to get the workflow to open the next task (I am very new to workflows and try to learn as much as possible before messing with our site)

3, If anyone can think about how to do what I need differently, I’m all ears.

Thanks!

Answer 1

I don’t know any plugin that does everything I asked for, but I had to deal with similar problems, and I managed to sort most of them using the Jira Scripting Suite , but it took some development (using python).

It’s easy to add workflows to your transitions that will create or close a new problem or new subtask . I use it to create subtasks by simply filling in some required fields on one of the problem screens. After creating subtasks, only automatic scripts can close the problem, and this can be done by closing all subtasks.

If this solution suits you, I will be happy to help with any further inquiries.

Answer 2

JIRA does not support nested workflows, but it is worth remembering that if you change the type of JIRA problem, it may have a different workflow. Thus, the problem can start as TEST-123, which is a requirement. Then, after it reaches the end of the workflow, it can be moved as a type of task task. Subtasks must remain the same.