You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
What are the options for using "Components" in NextGen projects?
@Frances Moncrief Hey, Frances! I'm going to go ahead and move this to the Next-gen collection, so you may get the best possible answers.
We tried setting up similar functionality by using release/versions for one of our projects. We setup different releases for different 'components' and identify epics/stories under right release by setting up versions on issues. It complicated things, but provided similar approach as that of components from classic projects.
If there is no reporting requirement, custom field, or label is another option to categorize issues.
But then, introducing components like breakup to next-gen project defies the purpose of the project type itself. Next-gen setup is for easy to setup, short, nimble projects. If project scope is huge, and you really need features like components, my suggestion would be to consider defining project as classic project, and invest few hours into project configuration.
There is an open request to add feature to next-gen projects. If it is popular requirement, maybe it will get introduced for next-gen projects as well in future release. Here is the link : JSWCLOUD-17601
Hello Jira Software next-gen fans, My name is Bryan Lim and I'm a Product Manager working on next-gen. Today, I'm pleased to announce the launch of Workflow Transitions in next-gen. Workflo...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events