Backlog not visible in side bar after creating new Enterprise Managed project from an existing one

[Edmond Victor]

I have created a new Enterprise Managed project from an existing project so that all settings will come across from the source project. However when I create an issue I am not able to see the Backlog view for the new project. 

[Trudy Claspill · Accepted solution]

Hello @Edmond Victor 

Do you mean a Company Managed project? It will say at the bottom of the navigation pane on the left.

How did you create the project from another project? Do you mean that through the Create Project feature you checked the box that says "Share settings with an existing project"?

If the answers to both of the above are Yes, be advised that process does not copy the agile board(s) (neither Scrum nor Kanban) settings for boards associated with the source project. It only copies the settings that you see when you go to Project Settings. You have to manually create an agile board for the new project and manually configure it to match the configuration of the board on the source project.

[Edmond Victor]

Thank you very much for your answer Trudy. Yes I meant Company managed project and I selected the checkbox "Share settings with an existing project". I can understand that I might have to create a new sprint but would have expected the Backlog (board) to be available. If I create a new project without selecting the "Share settings with an existing project" checkbox it creates a blank project with the Backlog available. I accept your answer but just find it strange. Thank you again.

[Trudy Claspill]

When you create a new blank project, the process creates a default board and saved filter where the filter is for all issues in the new project.

Also, a board is not a Project Setting. It is its own entity/resource within Jira. Boards are a way to view issues in a project. For Company Managed projects there can be multiple boards set up that display all or subsets of issues in the project, plus boards that reference issues in multiple projects. This is because boards for Company Managed projects are based on Saved Filters, so you can have a variety of boards referencing one project.

Because of that the Share Settings option was never designed to also create a board for the destination project. It would not be able to tell which board it should "copy".

[Edmond Victor]

Great answer Thank you that explains everything