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

This plan is connected to too many projects to load correctly

Matthew Antoine
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!
Nov 07, 2023

I have a plan which uses a saved filter as the only source. The filter works as expected in both versions below.

The plan works fine until I specifically exclude a project by adding (... AND project != NPIR) to the filter. It then gives the 'This plan is connected to too many projects to load correctly. Refine your selection to connect to fewer projects.' error. So, it works fine until I reduce the number of projects by 1...

Any assistance appreciated.

1 answer

0 votes
Marc Koppelaar
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.
Nov 09, 2023 • edited

Hi @Matthew Antoine 

Welcome to the community.

Could you please provide the JQL of the filter you are using?

The more detailled information you provide to the members in the community, the more probability there is that the issue can be resolved.

If your filter has a catchall clause, then someone adding a new project or changing the visibility so your team can see it will cause this problem. 

You don't need to change the filter to cause it - someone could create data that tips the plan over the edge.

Cheers

Matthew Antoine
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!
Nov 09, 2023 • edited

OK. Thanks for the help.

This works as a filter and as source for plan and returns 6 projects, including NPIR

((project in (PMI, PMG, NETPM) AND (status not in (Closed, Cancelled, Resolved) OR resolved >= 2023-07-01 OR created >= 2023-07-01)) OR (assignee in (usera,userb,userc) AND created >= 2023-07-01)) ORDER BY Rank ASC

This works as a filter, but not as a source for plan. 

((project in (PMI, PMG, NETPM) AND (status not in (Closed, Cancelled, Resolved) OR resolved >= 2023-07-01 OR created >= 2023-07-01)) OR (assignee in (usera,userb,userc) AND created >= 2023-07-01)) AND project != NPIR ORDER BY Rank ASC

Thanks for the assistance.

Marc Koppelaar
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.
Nov 10, 2023

Hi @Matthew Antoine 

I can't see faults in you JQL.

You might want to pick this up with Atlassian Support.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events