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; } } }

Can I ringfence Jira tickets in any way for sub-projects with NDA's in place?

Paul Scarlett

Some of our projects are either secret or have a sub-project that has an NDA (Non-Disclosure Agreement) in place.

In the vast ocean of our company Jira system, is there a way to ringfence these projects or sub-projects so that only authorised personnel can access them until they reach a certain point in their maturity?

I'm hoping I can apply a 'component' or 'label' or something else with rules that allow only a reference sub-set of personnel to view until being removed or unlocked...

Accepted answers

Trudy P Claspill

Hello @Paul Scarlett

Welcome to the Atlassian community!

Jira does not natively support a hierarchy of Projects. How have you achieved a "sub-project"? Is that just a Jira Project, or are sub-projects issues within Projects?

In general access to Projects is managed at the Project level for each project.

If you are talking about issues within a project then for Company Managed projects there is Issue Security to control the visibility of issue. In Team Managed projects there is a related feature called Issue Restrictions.

All comments

Trudy P Claspill

Hello @Paul Scarlett

Welcome to the Atlassian community!

Jira does not natively support a hierarchy of Projects. How have you achieved a "sub-project"? Is that just a Jira Project, or are sub-projects issues within Projects?

In general access to Projects is managed at the Project level for each project.

Paul Scarlett

Sorry Trudy - that went completely over my head...

Trudy P Claspill

What part went over your head? Do you still need guidance?

The first thing to clear up is terminology. You mentioned Projects and "sub-projects". In Jira a Project is a container for issues. A Project has a name (i.e. My Project) and a key that (i.e. MP). All the issues in the project get an unique ID comprised of the project key and a number (i.e. MP-123).

Given that terminology Jira does not have the concept of a "sub-project". You may have groups of issues in a Project and you may refer to that as a "sub-project" but that is not a term defined by Jira.

In order to offer guidance specific to your situation it is necessary for us to understand what you mean by "sub-project".

It would also help us to know if you have any level of administrative access. Are you an administrator for your Project? Are you an administrator for the entire Jira system?

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-cloud