We have added the feature issue type manually to our jira issue type structure. This has prevented us from being able to use some automation aspects within Jira. HOWEVER, Project management tools and many companies have moved to Agile which is about Feature releases. We have company initiatives that have Epics linked to them. From there we create features under the epics as it may take more than 1 delivery team to complete an Epic.
I would like to see Atlassian have a feature issue type as standard technology.
No I will not rename the epic to feature and create a "new epic" above the orignal to resolve this issue as that suggestion is a very backwards solution to resolving a standard process.
Hi @Lindsey Abrahamsen ,
Few posts that might be relevant (not a concrete answer) :
seems like renaming would be the right way ahead, but they've also mentioned a few SAFe related add-ons that might be of use.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.