Multiple steps for an issue?

Mattias Andrén September 25, 2013

Hi!

Im quite new to the Jira-world.. but I have managed to set up some issues for my project.. however.. each issue has multiple "phases/steps" it has to go through.. for instance:

Lets say that we will create a website.. then we have some UX:ers, Designers, UI devs and some Systems developers..

In this new website.. we will build a menu.. to complete the menu it has to pass all the different people working with it.. so.. for instance:

We create the issue/task..

The task is then assigned to a UX:er

Once the UX:er is done, the task is assigned to the designer,

Once the designer is done, its assigned to the UI developer

and once the UI developer is done.. its assigned to the Systems developer.

The problem here is... they all share the same issue/task.. but they just change the assigned person.. which then makes it impossible to for instance do a time estimate for that issue..

So my question is... is there anyway to simply create an issue/task and then tell Jira that this task has multiple steps/phases that it has to pass, so each role can have thier own "instance" of the task?

As I said before.. Im quite new to Jira.. so I might be missing something here...

Thanks in advance!

2 answers

1 accepted

0 votes
Answer accepted
MichałS
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 25, 2013

Well from JIRA 6 you have the possibility to have an Epic which can contain multiple Stories which can again contain multiple Sub-Tasks. Its up to you how you would like to order it but it is definetely possible to have one parent issue with multiple child issues.

0 votes
RambanamP
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 25, 2013

one way is you can create one main CR issue and create multiple sub tasks and assigne each sub task to specific developer. once all the subtasks completed then you can allow to close main CR.

may be some one give other better solution!!!

Suggest an answer

Log in or Sign up to answer