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.

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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

Is it possible to ignore sub-grouping for particular groups to avoid over nesting in Structure?

Edited

Hello, 

I'd like to group all items under an epic into two groups:

  1. External Dependencies
  2. Tasks/Stories under the epic.

And then I want to apply grouping only to the second group, grouping the tasks/stories by their status. Is there a way to ignore this grouping for the first group?

 

Project Epic

-- 01 - External dependencies

----- Epics from external project

-- 02 - Stories

----- 01 -  In Progress

----- 02 - Not Started

----- 03 - Completed

 

1 answer

0 votes
Stepan Kholodov _Tempo_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 29, 2023

Hello @Sasha 

It is not possible in the described setup. You can apply two different groupers and only consider one type of issues for each, but due to how groupers work, the 'no value' group will be created for ignored types by both groupers, which will likely make the hierarchy confusing. Moving Stories or Epics from external projects to a different hierarchy level, or introducing a different change in the setup might work.

I hope this helps. If you have more questions, please reach out to us directly at our portal: https://tempo-io.atlassian.net/servicedesk/customer/portal/6/group/1051

Best regards,
Stepan Kholodov
Tempo

Suggest an answer

Log in or Sign up to answer