It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
We recently completed a bunch of epics, however I still see them as a choice when I try to create a new issue. I've marked them as "Completed" on the Agile->Plan page as well as marked the epic-issues as resolved. We don't want people to be able to assign their issues to a completed Epic. What's the best way to remove the completed epics from the list of available epics?
Thanks!
I have created a bug on behalf of this:
https://jira.atlassian.com/browse/GHS-11362
Currently I do not think there is any workaround for it.
This is so painful! I have been struggling with the hierarchy and structure of JIRA for sometime now. We have stories that need more than one person to work on them. So initially we started using subtasks and assigning each subtask to a different user. However, we cannot assign story points to subtasks and they do not show up in the backlog. This is when we decided to uss Epics for these types of "big stories" that require more than one person. However since epics never go away when they are done, it is really frustrating.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreCan a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.