Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi @jrm ~ Atlassian's roadmap for Cloud can be found here: https://www.atlassian.com/roadmap/cloud?selectedProduct=jsw&
Hi @jrm , create a custom issue type 'Feature' and it will be underneath Epic in the standard issue type hierarchy (but not above the other base issue types). Although that's probably not the anwer you'd like to hear.
Alternatively, you could rename Epic to Feature and add Epic as level above, but I wouldn't recommend it personally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the suggestions. We received those suggestions from support and tried the first one but it didn't work for what we needed and the 2nd sounded like too much of a band aid that might get us in to trouble so decided against that one.
Not sure if we aren't doing something correctly or if what we want just won't work. We are fairly new to administering Jira. We used it in the past though and loved it. Thus why I was asking if it was on the roadmap to decide how to move forward.
Are there other suggestions on how to break down the work if you don't use features or do people add a layer above the Epic and if so, what do they call it?
We are starting agile in our company with a large CRM project so just an Epic and User Story is not enough to keep it all straight and to report upward clearly.
I appreciate any suggestions.
Thank you,
Jolie
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.