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

Structure: show issues (story, tasks, sub-tasks) grouped by assignee

Rainer Binggeli
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 13, 2023

Hi

I'd like to create a structure where we can plan the capacity per assignee during PI-Planning (and with every scope change), so we can identify over-allocation.

In order to calculate the sum in column "OE" correctly, the structure should not show the sub-task of "Ehrlich" in my folder. It all works nicely even when the epic is not assigned to me, the story or task still show (because the label "scoped23-4" we only put on work items such as story, task, sub-task).

Any idea how I could filter it the way that it only shows the stories, tasks and sub-tasks per assignee preferably grouped by epic.

Thanks for your help!

 

image.png

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.
Oct 16, 2023

Hello @Rainer Binggeli  

If you're looking for a way to only consider issues that have Assignees that match the Assignee either of their parent issue or their Epic, it can be done by the Formula column. For example, you can exclude OE values for all Sub-tasks with non-matching Assignees like this: 

if issuetype = "sub-task" and assignee = parent{assignee}: oe

and then aggregate the column's values enabling the 'Sum over sub-items' option in its configuration.

But if you want to specifically filter out such issues, you can do it with the Attribute Filter and a formula like this: 

if issuetype = "Sub-task" and assignee != parent{assignee}: 1

The filter's Operator should be is true and the Filter on level should be set to Manual: 2 level.

I hope this helps. If you need further assistance with this, please reach out to us directly at our support portal.

Best regards,
Stepan Kholodov
Tempo

Rainer Binggeli
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 19, 2023

Hi Stepan

Thanks for your support. I've tried, however, not with the desired result. What I need is to sum all "original estimates" by work-items assigned to one person providing me with a total of hours scoped per assignee, which I can then compare to the net capacity. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events