How can I keep the Stories and Tasks Separate on a board since we use Tasks for the Estimations and tracking

Atul Jain

In our Development Project, we have Organized our requirements in EPIC and Stories which holds the functional requirements. Development team creates the tasks which we link to stories (not making sub tasks as otherwise we can not move sub tasks to Future sprints for Planning purpose.)

Now, on various boards, we have stories as well as tasks appearing together that increases the count of overall incidents unnecessarily whereas we are interested only in looking at tasks for tracking purpose.

 

Also, since we can not create sub tasks for practical purposes, it is very difficult for us to find whether we can close a story or not. 

 

Can somebody please help in suggesting a better organization of our Incidents so that we can keep the requirements as well as development tasks all at one place in JIRA and still have better visibility?

 

 

Nic Brough -Adaptavist-

>Now, on various boards, we have stories as well as tasks appearing together that increases the count of overall incidents unnecessarily whereas we are interested only in looking at tasks for tracking purpose.

That would make me say simply "change the board filter to say 'and issuetype = task'" which would drop the stories out and make the board focus entirely on tasks.

Other options would be around visibility - add quick-filters or swimlanes for the issue types.