Issue Type Security Levels for Team-Managed Jira Service Projects

[Michelle B]

Hi All 

Restricting visibility on specific issue types seem to not be available in a team managed JSM project. 

Does anyone have a work around for this until they enable this besides migrating my team managed project into a company one?

[John Funk]

Hi Michelle,

I am not aware of any option that would be available like that for Team-managed business projects. I think you would indeed need to migrate to a Company-managed project. 

[Rebekka Heilmann (viadee)]

Hi @Michelle B 

I don't think there hasn't been any update since this post: How can I associate a Issue Security Scheme to a T... (atlassian.com)

There are feature requests providing that option for Team managed Projects (prior "Next-Gen"). Considering that "Team-managed" projects are meant for Teams and within those there usually shouldn't be any restrictions (in the Agile world anyway) it seems reasonable.

As Service Projects don't have shared Schemes by default anyway.. is there a particular reason why you used a Team rather than company managed project?

[Patrick R]

Hi @Rebekka Heilmann (viadee) I'm not the original poster, but like many others, I am still looking for a solution for this and it's one of the frustrations of JIRA that every slightly different iteration, version and even template has different features.

The reason we're looking to solve this is that we run our software development in JIRA, so we want our management team to also run their daily to-dos in JIRA so there is one system and we can link to items in shared projects. BUT, much of each individual's day-to-day task management must be kept private from broader teams - think "discuss salary with Bob".

Company-managed projects include security restrictions so for any one task, you can allow or disallow people to access that task.  But company-managed projects lack so many features of team-managed projects, like a good list view, a menu across the top of the list and easy addition of color-coded categories that can be different from person to person.  It's also naturally harder to quickly add new categories etc. etc. 

So, it's very hard to task manage with company managed projects.  But team-managed projects are set up so anything you have in your project is visible to everyone else who has access.  And that is probably one of the reasons a lot of people are looking for this feature.  Very frustrating!

[Patrick R]

I'm going to correct my own response above here.  After checking my own projects, seems that team-managed projects CAN have security levels / Restrictions.  But it depends what kind of team-managed project. Team-managed software projects can have restrictions.  But team-managed business projects can not.

So, same problem as my initial comment, but I was mistakenly attributing the issue to whether it was a team or company project. But it's not. Restriction / security access levels differ between team-managed "software" (can have restrictions) and team-managed "business" (cannot have restrictions).

Unfortunately the software project with the restriction capability is missing so many features that the business project has.  Ugh JIRA. Why.

[Rebekka Heilmann (viadee)]

@Patrick R then this is good news for you: Welcome to the next era of Jira - Work Life by Atlassian

Jira Software and Work Management (Business) will move closer together. I'm expecting that many features will assimilate. List view is already available for Company managed software projects.

Also, they are constantly improving Company and Team managed projects so they get more similar when it comes to configuration. 

So maybe just wait a year and your problems might be solved by Atlassian's product development team ;) 

[Patrick R]

Thanks for that link. I guess it will all depend on the execution details.  For instance, recently, team-managed software projects (which have the critical restrictions function) got a list view, like team-managed "business" projects, which lack the restrictions function. However, the software project's list view misses a lot of the reasons it's good in business projects; like menu over the top, ability to customize columns, ability to add color coded categories to those columns, a way to change the background color of the list view to make it easier to navigate around many projects, etc. etc.  So technically they can check off "add list view", but it's not very useful.  It feels kind if like they have siloed developers working on different project types, not learning from the features of what other groups are doing.

[David Klucznyk]

Alternative solution for a Team-Managed Project:

1. Create a net new role that is very similar to "Member"

2. Add users to that role

3. Apply the restriction to the issue. 

Adding the role restriction to an issue will act as the same as Issue Level Security.