BUGG: Cross writing from one boards backlog to another boards backlog

[Glenn Andreas Samuelsen]

Hi,

I have a company managed set-up. One SW project with many sub boards. The other day when updating the backlog of one board (creating future sprints) the same update (naming of future sprints) appeared on a non-related boards backlog....

What`s happening? 

Anyone experienced this? 

How to "cut the link" so that this cross writing discontinues?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

Boards do not belong to projects and they are not containers for issues or even sprints.  They appear in projects as a convenience, but they are not locked to the project., and hence there's no such thing as "sub boards".

A board is a view of a selection of issues.  A board usually has the default selection of "project = X", so they look like they are project related, but technically, they are not.  You can create boards from any saved search (filter) you want.

I suspect this is what you are looking at - a board that has a filter that includes issues from other places that have been included in sprints that belong to another board.

[Glenn Andreas Samuelsen]

Thanks for laying out the technical realtionshis @Nic Brough -Adaptavist- 

I guess you are right in that there is a filter issue going on. Having looked at it a bit more, the "BUG" is only valid for the next future Sprint (3.5) we have planned in these two "projects / Sub-boards". In Sprints 3.6 the issue is no longer there. Odd.

I`m working with a colleague from work to sort this "BUG" issue out though. He is fairly well experienced with Jira, and had not seen this before. Hence keen to solve it:)  I`ll updatethis thread with the findings eventually.

Thanks:)

[Nic Brough -Adaptavist-]

There's still no bug here.

It now sounds like you have put the issue into a sprint.  That means it can not belong to another sprint, whatever the board the different sprints belong to.

It's not a filter thing, it does not make sense to have an issue in two sprints at the same time, because that implies different team ownership and an issue having two different places in the backlog at the same time.

[thuanddk56cc]

Hi @Glenn Andreas Samuelsen ,

Please check if your board filter contains issues from more than 1 project.

[Glenn Andreas Samuelsen]

Thanks for your repply @thuanddk56cc 

We have looked at the filters and they look ok, apparently..

As I wrote to @Nic Brough -Adaptavist-  earlier, this "BUG" is only present in the upcoming Sprint we have planned (3.5), In 3.6, also planned "The BUG" doesnt happen. No change to filters... Odd.

I`ll update on this thread when we pin down the issue.

Thanks:)