Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!


Does Portfolio for JIRA support multiple mappings in the Hierarchy configuration?

Hi all!

our organization has started to roll out Portfolio for JIRA and we quickly realized that the initial mappings for hierarchy (Epic = Initiative  / Feature = Epic & User Story / UserStory = Task) was unique and only made sense for a different business unit within our company.  we now face the issue where we need to have different mappings (Epic = Epic  / Feature = Feature / UserStory = User Story) yet don't want to conflict with the team already using this tool?



0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events