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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Adding Themes, Features or Initiatives in Next Gen Projects?

Hi, I am using the Next Generation Project version of JIRA. Is it possible to add Themes, Features or Epics? I have admin access but can't seem to find these options. I am looking for a way to organise my epics into related themes of work. Can you help with this?

1 answer

1 vote
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 16, 2019

Hello Raj,

Thanks for reaching out and first, "Epics" are a native function in the next-gen projects, and additional details on working with epics in a next-gen project type can be found in: "Manage epics in next-gen projects" 

As for features and themes, Themes are an additional function provided by the add-on app Jira Portfolio, and I believe what you are looking for in Features lines up with the terminology "initiative" for a corresponding functionality of Portfolio.  details on the capabilities can be seen in the article "Epics, Stories, Themes, and Initiatives" 

However, Portfolio can import issues from a next-gen project it is NOT currently compatible with the next-gen project types, and a majority of the functionality will not cross over when using a next-gen project, so the use of the classic Project template would be the recommended approach,  Additional details on the functionality loss of Portfolio when using a Next-Gen project types can be seen here: "Portfolio for Jira next-gen support" 


Ok, thanks Earl

Like Stuart Tennison likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events