I was hoping to get a few tips on how to manage a backlog with a large amount of different kind of stories. Our problem is that the product owner is having a hard time seeing the big picture and as such also is finding it difficult to prioritize. As you are not able to group stories in more then two levels (Story - Subtask or epic - story) in jira/greenhopper we can not group them together the way we like (i.e. Epic - story - subtask) in order to get a better overview and still use Greenhopper to prioritize and manage the stories. Anyone who is facing the same problem and have a nice solution?
You might want to check out the Structure plugin... I'm taking a look at it now. My immediate reaction was that I wasn't loving the user experience and it seemed a bit un-intuitive, but it may be that I've just not understood fully how it works yet. Let me know what you think. NB: it's currently for installed JIRA only, not OnDemand. https://plugins.atlassian.com/34717
This is how we handle stories in Jira Greenhopper..
The only problem with this setup is the ranking field is for all issues in Jira. Therefore, we have to rely on the planning board to visually understand our work priorities.
Your summary above makes me believe that your user stories aren't related to a specific high level product feature (epics).
Hopefully this helps,
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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