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

Factom: Portfolio for Jira case study

Josh Frank
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 04, 2018

Recently, as part of a series of Portfolio for Jira case studies, we spoke with Carl DiClementi, Director of Product Management at Factom about how he uses Portfolio for Jira. In lieu of spreadsheets, Carl takes a unique approach with Portfolio for Jira to building and communicating plans. To plan for the quarter he creates a level of hierarchy above Epics, which he calls "Programs" and works with his engineering team to break down the "Programs" into smaller pieces of work. From there he uses Portfolio for Jira's scope table to massage the details and prioritization of the Epics and Stories for each Program. In order to communicate his plans with business stakeholders, he embeds Portfolio for Jira's schedule report into a Confluence page, which stays current even as plans change.

Read the full story here. Check out our series of Portfolio for Jira case studies to learn how other businesses are using the tool here


Hi Josh.  Interesting read and good to know that other businesses are utilizing JIRA Portfolio.  I wanted to ask if there's ever a plan for JIRA Portfolio to support additional hierarchy between Epic and Stories?  

We have users who've come from using MS Team Foundation Server, which provides a hierarchy level of Epic > Feature > Story > Tasks/Subtasks.

While Portfolio offers hierarchy to build on top of Epics, there doesn't seem to be a way to build below.  Thoughts?

Roi Fine
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 08, 2018

Hi Ricky,

Thanks for your inquiry. Adding/customizing an issue hierarchy between epic to story is not in our short term roadmap. 

I created a feature suggestion ticket to capture the terminology gaps of scaled agile frameworks(and any customized solution) with the Atlassian product line.

We are prioritizing our roadmap constantly, please provide us further feedback on the ticket.


Hi @Josh Frank we are currently working on a project for Tokyo's Olympics during 2020 and we'd love to talk to you about how we are using JIRA Portfolio.

Claire Cook
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 18, 2018

@ローハン I oversee customer marketing at Atlassian and would LOVE to hear your story. What's your email? 

Hello Claire and I would LOVE to tell you! Use

thank you.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events