nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Are labels shared across all projects?

Andrew Evans_z1qft2

I did some digging in older community posts that says labels are, in fact, globally shared across all projects but for the life of me I can't prove that with testing project specific access. We have one project we need other project users to NOT be able to see any content for....so I need to make sure labels are in fact project specific vice global.

Is there any way to confirm that?

If labels are in fact global, I suppose a custom, project specific field will have to suffice yes?

Accepted answers

John Funk

Hi Andrew - Welcome to the Atlassian Community!

Yes, Labels are shared across all Company-managed and Jira Work Management Projects. Team-managed projects are self contained to do not share objects with other projects.

All comments

John Funk

Hi Andrew - Welcome to the Atlassian Community!

Yes, Labels are shared across all Company-managed and Jira Work Management Projects. Team-managed projects are self contained to do not share objects with other projects.

Andrew Evans_z1qft2

Thanks @John Funk !

John Funk

You are very welcome!

Worn 'n Torn

This is my trouble also. I think I read that labels are retained to maintain data in issues if they are linked across projects and teams.

However it seems a problem (certainly for JSM and JWM), because picking a label means wading through a decade of labels built up by the dev-team. People constantly want to choose the wrong one.

1. Is the only way **not** to inherit labels from other projects to go with a team-managed one?

2. Are there other attributes that Jira cloud has to share across all the projects in the Cloud instance, in similar ways to labels?

This matters as we rely on Jira's issue collectors to drive our webforms. They don't function in a team-managed project yet(?), but are the only way (beyond email or calling in) that someone can raise an issue without a license. This takes away from our youthful exuberance about Jira in week one. Perhaps this feature is being deliberately left out to force everyone to buy seat licenses?

Ian Randolph_7i7zvm

Followup question:
If a custom field is created with the behavior of Labels, does it start with a clean slate, or will it too share all the labels of the Labels field?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

label