The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Create issues in A project but it appears in B project's backlog

jenny.lee
July 23, 2021

I created an epic in A project, and it is named A-001,

but I didn't see it in the backlog list of A project,

Instead, it showed in B project's backlog.

 

Why would it happen?

How can I move back to A project's backlog?

Thanks for answering!

 

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 23, 2021

Projects do not have backlogs.  Backlogs are a part of boards.  Boards are not containers for issues, they are a view of a selection of issues.  (It is common to set up "board = project" on a simple 1:1 basis, but it's not universal)

If an issue is in a backlog and you think it shouldn't be, then there's something wrong with the data on the issue.  It is being selected by the board that the backlog is part of.

Have a look at the board configuration, looking at the filter it is using to select issues.  This should tell you why your issue is appearing in the "wrong" backlog.

jenny.lee
July 23, 2021

Hello Nic,

Thank you for answering!

However, after I checked the board setting,

I found out the filter query is "project = A ORDER BY Rank ASC",

so when my epic is named A-001, I suppose it should be in A project's backlog?

It's so weird, could you offer me more possible answer?

Thanks again!

 

Jenny

jenny.lee
July 23, 2021

ah I think I may find out some possible problems...

please let me check with my colleague first, thanks!

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 24, 2021

Ah, it's the Epics.

Epics are not really backlog items, but that's not the point here.  Epics jump into boards when they (could) contain issues that the board selects for.  Any issue can be added to an Epic, so yes, if you associate BB-2345 with A-001, then A-001 will appear on the board for the BB project!

jenny.lee
July 25, 2021

Hi Nic,

After discussion with my colleague, we found out that A-001 issue status should be swithed to "ready to dev" to show on the dev board.

jenny.lee
July 27, 2021

Also, we can adjust the setting in column management. (in board setting)

0 votes
Ashu Tyagi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 23, 2021

@jenny_lee  Check the query with which board in project C is created, Boards display data based on its queries and it is possible that C board might have some query which is pulling that EPIC

Also see query of project Z board   maybe it is not including EPIC in it.

jenny.lee
July 25, 2021

Thank you!

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events