Hide Epics from other projects?

[Allan MacDonald]

Hi! I've been experimenting with different project templates after deciding I'm not really liking our Scrum setup. I found that I really like the Kanban template, but with it set to company managed so I can get the backlog. Before that, I tried the team managed one and couldn't get the backlog on it.

I've noticed now though that I can see the Epics from my first project in the new project, which I don't think I really want. I'm sort of starting fresh here while not yet deleting the other one. 

Is there a way I can isolate the projects from each other? I could imagine I would want this for sure if I was starting a new product under the same company umbrella and wanted their developments isolated from each other.

Any info is appreciated, thanks!

[Trudy Claspill · Accepted solution]

Hello @Allan MacDonald 

The visibility of the Epics is determined by the permissions of the user to view the project that contains the Epic. There is not a configuration option to hide Epics from a project except through the permissions allocated to users for that project.

Also in a Team Managed project you can have a Backlog with a Kanban board. Go to Project Settings / Features and enable the Backlog option there.

[Allan MacDonald]

Oh wow, I thought I tried adding the backlog to the team managed backlog.. it worked! It also in the TM project I can't see epics from my other CM projects, like I can in my CM kanban project, which lets me see our original CM scum project.

Do you see any potential downsides to using the TM Kanban + backlog project?

Thanks for the help.

[Allan MacDonald]

I'm curious though why the team managed project can only see it's own local epics when I go to assign them. Any ideas there? is it also a permissions thing?

[Trudy Claspill]

The advantages and disadvantages of Team Managed projects are in the eye of the beholder and the Jira Admins.

If you want to give your teams more autonomy to customize their projects to their own needs, then TM projects are better.

Do you need to do cross project reporting? That is more difficult when you have Team Managed projects.

Project Admins of TM projects can make custom fields in their projects. Jira doesn't require custom field names to be unique. Your instance can end up with multiple custom fields of various types with identical names. This can cause difficulties in figuring out the right field when doing searches and working with automation rules.

Sometimes third party apps don't support Team Managed projects.

You can't have more than one type of subtask issue type in a TM project.

There are a variety of pros and cons to using TM projects alone, using CM projects alone, or using a mix of TM and CM projects in a Jira instance.

[Allan MacDonald]

Thanks, any thoughts on the last question about Epics visibility between CM and TM projects?

[Allan MacDonald]

nvm I found it in the docs here, near the bottom

"Company-managed project issues can only be added to company-managed project epics, and team-managed project issues can only be added to team-managed project epics." 

https://support.atlassian.com/jira-software-cloud/docs/manage-epics-in-team-managed-projects/