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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Structures - Can I "group by" underneath the top level issues (Initiative/Epic) instead of above?

I'm attempting to group my issues in a way that doesn't seem possible in structures. What I want to do is essentially: GROUP BY Initiative, Component so that the layout looks something like this:

(Initiative-1) Show value via metrics
     (Component-Team 1)
          (Epic-100) Determine appropriate data to gather

     (Component-Team 2)
          (Epic-101) Build charts

     (Component)-Team 3)
          (Epic-102) Determine appropriate data to gather

(Initiative-2) Create documentation
     (Component-Team 1)
          (Epic-103) Create confluence space

     (Component-Team 2)
          (Epic-104) Refine process documentation

     (Component)-Team 3)
          (Epic-105) Refine process documentation

...Where the focus is on the Initiatives first and foremost, and the grouping below it is by Components (teams in this case). I can only get this to work in the opposite way, where Component is the top level which then shows all of the Initiatives under it since no single team owns those.

Is there a way to achieve this view? When I try to add "Group By" automation after the initial JQL insert, it says I'm creating a generator and fails. If I add it to the top level, that is not what I'm looking for.

1 answer

1 accepted

0 votes
Answer accepted

Hi Douglas

If my suspicion is correct, you might need to invert the order of the groups, or manually set the Group by component/s generator to work on the "Next Level,"

Another way to achieve this goal is to:

1. Insert the initiatives through the Insert generator

Automation > + > Insert > JQL Query... 

A simple query example would be: Project = xxx and issuetype = initiative

2. Use the Child Issues (Portfolio) extender to pull in the epics.

Automation > + > Extend > Child Issues (Portfolio)... 

3. Group by Component/s

Automation > + Group > Component/s - (Set it to work on the next level).

4. Use the Stories under Epics generator to pull in stories, optionally.

Automation > + > Extend > Stories under Epics

Note: Before adding a generator, you need to select the top level-row of your hierarchy (where it displays your structure's name).

I hope that helps.

(Thank you for using Structure).

Mario O.G

[ALM Works]

Thank you Mario. I realized  "Group on level" setting is what I needed. It's strange that the setting isnt visible when you are creating the "group by", but appears when you go to edit it.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you