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?
>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.
Thanks Nic, Though setting the filter to "Issuetype not in (Story)" would make more sense as there are other items too which would need the attention.
There would be another problem with this approach, Now, since Stories will not appear on Board, they will not be the part of sprint and we will not be able to close them or pay attention to them. Adding a Quick filter can resolve this to an extent, but still Stories and Tasks would both needs to be managed in that case. I am still looking for some mechanism where JIRA treats Story as story and move them off the list automatically as it does with EPiC.
They are treated as stories, stories are supposed to be on the board. They're not Epics.
Did you have a look at swimlanes? I suspect your best option would actually to have swimlane = story, they're correctly on the board then, and let you manage tasks within them.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs