Hi,
I have a single Jira project and three teams (one backlog for all three teams). For each team, I created a separate board + separate sprint.
The problem is I see all three Sprints on each board.
* Naming convention is different for each team
* I create each sprint under a separate board (sprint A I create under Board A).
When I just create Sprint A with no tickets, it appears only under Board A, however, when I move any ticket to the backlog to Sprint A, the sprint gets appeared on all boards.
A sprint will show in any board that could include issues in the sprint.
The boards you have defined differ only by label, so it's perfectly possible that any issue could appear on any of the boards.
On an unrelated note, you really should remove the "sprint in openSprints()" and the "status not in (done)" clauses - one of them destroys the usefulness of the backlog, and the other destroys all the sprint reporting for the board.
Surprisingly, if I remove
"AND (status not in (Done) "
Then all issues that have been Done will show up in the backlog.
@Nic Brough -Adaptavist- could you elaborate on "could include in the sprint"? Is there a way how I might fix that? Adding another filter? Anything else I can do?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>Then all issues that have been Done will show up in the backlog.
That tells us that your status of "Done" is mapped into the wrong column in the board. It needs to be in the very last column of the board, Jira's boards only consider an issue done if it falls in the last column.
I'm not sure how to further explain "could include in the sprint". It really does mean what it says - if someone could take an issue from the backlog and drop it into the sprint at the top of the backlog list, then it could be in the sprint. When that happens, every board that issue appears on will display the sprint it has been dropped into because it's information about the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> That tells us that your status of "Done" is mapped into the wrong column in the board.
Doublechecked: Done is in the right column. I had to define "AND (status not in (Done) " because I combined two projects under one board. Either way, it just didn't work.
I think I got what you are saying regarding "could include in the sprint". So if all boards share the same backlog (the same tickets), then no matter under what board the sprint has been created, when you add a ticket to a sprint, it will show up on each board. -> That gives me an idea my real issue is in the board filter, I need to include one more rule to show specific sprint name for each board
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I modified the filter and it works with no additional fields added.
from
project in (Eng_project) AND (status not in (Done) OR sprint in openSprints()) OR project = Prod_project AND issuetype = Epic AND status not in (Done) AND labels = teamA
To
project in (Eng_project) AND (sprint = 'teamA' OR sprint is EMPTY) AND (status not in (Done) OR sprint in openSprints()) OR project = Prod_project AND issuetype = Epic AND status not in (Done) AND labels = teamA
Where teamA is the first part of the sprint name we use, the second part always changes like "TeamA Sprint 33"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For each of your boards is there a differentiating factor in the filters being used?
I've seen instances where a Custom Field is added to indicate a 'Team' and then when you transition from the Backlog to In-Progress (or whatever the status transition is) they are required to select which 'Team' is working on the issue.
Then for each 'Team' board, the filter being used would specify only issues with that attributed team would be displayed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Each board has a specific filter applied to that board.
General Idea: it combines all tickets under main project (Eng_project) and Epics from another project (Prod_project).
Here're board filters:
Team A project in (Eng_project) AND (status not in (Done) OR sprint in openSprints()) OR project = Prod_project AND issuetype = Epic AND status not in (Done) AND labels = teamA
Team B project in (Eng_project) AND (status not in (Done) OR sprint in openSprints()) OR project = Prod_project AND issuetype = Epic AND status not in (Done) AND labels = teamB
Team C project in (Eng_project) AND (status not in (Done) OR sprint in openSprints()) OR project = Prod_project AND issuetype = Epic AND status not in (Done) AND labels = teamC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Dillon if I get you right, you suggest:
1. Add the "Team" field to the Eng_project and make the field required
2. Have an additional board filter to include the "Team" filed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are essentially doing the same thing adding the team to the Labels field.
I'm not entirely confident this will work as I can't replicate your scenario, but maybe your query needs brackets surrounding the:
(OR project = Prod_project AND issuetype = Epic AND status not in (Done) AND labels = teamC)
That way there are only 2 conditions in which an issue will appear on the board, the string above and the one below.
project in (Eng_project) AND (status not in (Done) OR sprint in openSprints())
Is the Team Label being used in the Eng_Project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is the Team Label being used in the Eng_Project?
No, only to filter Epics in Prod_Project. Do you suggest adding labels across Eng_project tickets?
Let me try to modify the filter, maybe it will work!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.