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

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
4,559,863
Community Members
 
Community Events
185
Community Groups

I set up my plan based on filter but the plan does not pull all items?

We are using plan and is not pulling all Initiatives into the plan that my filter does? IN MY FILTER I HAVE 76 ITEMS but my plan shows only 30?

1 answer

1 vote
Niranjan
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 05, 2020

Hi @Zsofia Kope ,

I believe that you are using the filter query as a data source of your plan. Could you confirm the settings from your Issue sources of your plan "How long completed issues will be shown in your plan?"

https://confluence.atlassian.com/advancedroadmapscloud/issue-sources-998651043.html

I can set the time. The issue is that is clearly pulling subtasks associated with the stories that are to to or left in progress etc.

Whether I change 30 days or 90 days my unestimated issue count is the same (subtask and stories lumped together) . we do not estimate subtasks so is pulling all of them in :(.

JIRA considers subtask te same as any issuetype and that is the issue. I plan we should be able to choose what issuetype needs to be rolled up to initiaitive + epic level. WE dod not have that flexibility. so my executivesare flipping because does not give the accurate unestimated stories z(since adds subtasks:()

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events