Hi folk!
My team owns a Jira project that sometimes is used by other teams. To avoid displaying extra tickets and Sprints of other teams, we used the Jira query excluding by the Component field. This filter formed our Backlog and Board correctly. Any extra Sprints were not shown in our Backlog.
But after the last big Jira release in November, I can see all Sprints that have tickets from our shared service. The Jira query is the same. And extra tickets are still excluded, we only can see all Sprint with zero tickets in our Backlog, which brings a mess.
Is it a known issue that has to be fixed by Atlassian or we can use some tips to fix this problem?
Hi @Anna Naidenko -- Welcome to the Atlassian Community!
You note that the Jira project is "sometimes used by other teams".
Is their usage frequent enough that it would warrant creating a separate Jira project for them, eliminating the impact on your team?
Kind regards,
Bill
Hi @Bill Sheboy
Usage is stable. They need to use this project, cause there is a rule in our company - relation 1 service = 1 Jira project
Previous workaround with excluding was good to separate Backlogs and avoid any impact.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Given this symptom appeared after the board / backlog enhancement went live, and you are on a paid, Jira license, I recommend working with your site admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ The admin will need to submit the ticket, and they can add you as a contact to interact with support.
After you hear back from them, please post what you learn to benefit the community. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could this be related - JSWCLOUD-26041 ?
Is it possible to try filtering out both the parent and sub-task issues in your filter, if yes?
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ste Wright
I've checked and would like to add that even when a sub-task is also excluded, I still can see redundant empty Sprint. Unfortunately, this workaround doesn't work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I gave this a try and it does the same for me - and I couldn't get them to be hidden, even with various different filters.
I assume you already have 2 separate boards here? One for your Sprints, one for the other teams? If not, I'd try this as one option.
But I do agree with @Bill Sheboy - I'd contact Atlassian Support for this one!
Ste
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.