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!


Doubts jql hierarchy Initiative and bigpicture

Hello everyone!

I currently have two templates of project in my Jira Standard Cloud, portfolio project and Operational project.

  • In Portfolio it would have the structure Business Value>-> Initiative
  • In Operational Projects it would have the structure Classical Epic-> Story/bug...


The structure would be

      Business Value (issue link Is Parent of)

                       -> Initiative (issue link Is Parent of)





I only have Jira Standard and Bigpicture apps.  I don't have the Premium version Jira nor do I have the jql [ issuekey in childIssuesOf("XXX-1") ]

When I'm scoping inside bigpicture, is there a way to indicate that I only want to get requests related to Business Values ​​up to Story?


Best regards








1 answer

Many approaches to Initiatives exist throughout the project management community. Some claim an initiative is a short-lived, rough idea that will either receive funding (and become a project) or be scrapped. According to others, an initiative is as elaborate as a project, has epics and stories linked to it, and lives as long as a regular project would do. How to model initiatives in Jira BigPicture? Also, how to leverage Portfolio for Jira initiatives in BigPicture?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events