Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What are the options for using "Components" in NextGen projects?

What are the options for using "Components" in NextGen projects?



I haven't tried components in a NextGen project as I am not a big fan of them due to it's simplicity and lack of reconfigurability.

Still, I think you may be able to use them as I describe below although I don't know how well or even if either of my examples would work.

We use components in our system to direct an issue to a group. It isn't the most elegant solution but in our system, we have a company-wide issue tracker that the lead team that will be asked to handle the issue is determined by using components. This field is then used to reassign it to the lead of that team who can make the determination of how it will proceed.

I've decided to try using within a new classic KanBan project to break up a huge board that has 13 columns which is way too busy and unwieldy. The project will have five components to break it up into a more manageable system.

Erica Moss Community Manager Sep 28, 2020

@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


Log in or Sign up to comment
Community showcase
Published in Next-gen

Feature Announcement: Jira Software Next-gen Workflows Transitions: In Progress -> Done

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...

4,348 views 27 25
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you