I am in a pretty bad dilemma using JIRA for our software development projects. I hope you can maybe help me with the following problem concerning the estimate & remaining work.
We are using following structure to break down our project work:
We chose this way, because we need some kind of break down structure in order to sort all our tasks into the correct categories, modules etc. where work has to be done. Later on we use Tasks and Stories in our monthly sprints.
Beforehand, we use the above structure to estimate our work as follows:
And this is where my problems start:
Do you have any idea how I can keep working with JIRA using some sort of break down structure (EPICs, ...) and keep track of our workload? We need to sort work into different categories and using the JIRA Backlog with version numbers and epics seemed to be a good approach at the time.
I am open for suggestions
Thanks in advance
Not sure if you already found a solution, but you may want to check our Structure add-on. It will allow you to do several things:
Depending on your process, there might be other useful things Structure can do. If you want to discuss this in more details, please contact us at support.almworks.com and we'll be happy to give more ideas and explain these features in more details.
Eugene (ALM Works)
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
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