You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Advanced roadmaps; I have two projects configured in one plan. Oddly a couple tickets show up in both those plans where it should not. I cannot find what would be causing this. Have you ever heard of that?
Example:
Plan: Test
Project: ABC Project
Project: 123 Project
Result is I see both projects in one plan, displayed separately. But some of the tickets are appearing in both.
Thanks,
Karl
Hi Karl,
This could be related to the grouping you've applied on your Plan. Please have a look at Issues appearing in the Unassigned swimlane when Grouping by...
Cheers,
Belto.
Hi Karl,
Can you attach screenshots of the configuration? This sounds like there is a board or filter also configured in that plan.
Also is this for Cloud or Data Center?
Best,
Clark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Karl Rothenberg What are you grouping by in that screenshot? Also what are your Issue sources for the plan? Whole projects or individual boards? If boards, what are the filter queries of those?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi...
Sources are 3 separate projects
Grouping is by project
I suspect this is happening because there is some overlap between some epics. Which is to say that an epic lives under one project but sub tasks lives under a different project. Though that it just speculation on my part.
Karl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I suspect you are right @Karl Rothenberg as I note that OPSP-2 entry in Ops Rox has a > next to it, signifying that it has child tasks under it, where the Ops Project entry does not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.