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

Potfolio Epics don't have an Epic ID

Creating an epic under the portfolio plan doesn't populate an Epic ID number.


For example, if I create an epic in Jira Software, it assigns the ID as "EPIC_23" but if I create the epic under the portfolio plan it assigns the ID "EPIC" and doesn't add that to my Jira software issues list.

1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 02, 2018

Hi Linda,

When you create an Epic in Portfolio, did you do a commit changes? Portfolio will only persist changes or ticket creation once you commit the changes back to Jira.

There should be an uncommited changes lozenge by your plan name, you can click on this and it will show you the changes or issues you created in Portfolio, clicking on commit will then put it through to Jira Software and after this it will reflect back on Portfolio the issue key assigned to it.

Hope this helps.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events