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
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
The use case is pretty simple but I don't understand why it's not working:
I have 2 projects ES and OBT. I have 2 boards for my 2 teams.
- 1 board includes the entire ES project + issues from OBT project that have a specific component (let's call it X)
- 1 board includes the entire OBT project - issues from OBT project that have the X component
Therefore, those 2 boards are pretty exclusive. No issue is present on both, i've double checked it.
Here's the thing: When I import the scope, I choose the 2 boards and, by default, issues from the OBT project with the component X are unchecked. Not a big deal since I can select all. But, if I add a new one to the epic, it won't appear in my plan, which is very annoying. It means I would have to redo an import every time one of the team is adding an issue like this one.
Do you have any idea on this one? Should we migrate those issues to the same project (ES)? The reason we kept like this is that the component fixversion would coexist on both projects and that's not ideal.
I understand how the projects are configured. While replicating the behavior, I'm not entirely clear on what you meant by the following line.
But, if I add a new one to the epic, it won't appear in my plan
Could you clarify what did you add to the epic?
The problem is those issues are in the results of the board filter.
Here are my 2 boards respective filter:
project = ES OR project in (OBT) AND component in ("Buying Flow", Frontend) ORDER BY Rank A
project = OBT AND (component is EMPTY OR component not in ("Buying flow", Frontend)) ORDER BY Rank ASC
the issue in the screenshot does have the component "Buying Flow", does appear in Team ES board but it's not part of the scope unless I redo an import of issue sources by selecting all the issues