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

team managed project set security level when transit to certain status

Mimi Peters

Hi there,

I would like to for Team managed project, if I want to set the only people I put in specific field can see the ticktet, is this possible?

I tried to transit the ticket a status called "Restricted" then use automation to restriction the ticket security level but its failed as it seems there is no issue with security for a team-managed project. Any suggestions?

The idea is anyone can raise a ticket but I can decide afterwards to restrict certain tickets to only certain groups of people can see.

Regards

Accepted answers

All comments

Trudy P Claspill

Hello @Mimi Peters

In Team Managed projects the security feature is referred to as Issue Restrictions vs. Security Levels.

Are you able to set the restriction on the issue manually through the UI? If not you need to have the Restrict any issue permissions in that project.

I did find a change request to make the Restrict field available in Automation, but it was closed without change due to Low Engagement.

https://jira.atlassian.com/browse/AUTO-480

It might be possible to work around it by using Advanced JSON Editing to set the field, but I have not tried to work out the detail and have not found any other posts that show that workaround.

Mimi Peters

Nice to hear from you Trudy.

It seems there are only 3 options and none of them can do what we want.

The idea is open to all to raise, but when the issue is sensitive we then move the ticket to a restricted view and only allow certain people to follow up further. Perhaps need to go back to Company managed... was hoping the automation can do the trick.

@Trudy P Claspill

Trudy P Claspill

Team Managed project issues can be restricted only to Project Roles. You cannot restrict them to individual users or user groups.

If you can use that as the basis for restricting visibility of the issues then you might be able to set the restriction through an Automation Rule. I have not tried to implement this.

If I follow the instructions here to find the field name

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

...and apply that to the Restrictions field in a Team Managed project issue, I get this for an issue where I restricted the issue manually to the Administrators role.

"issuerestriction":{"issuerestrictions":{"projectrole":[{"restrictionValue":"10667"}]}

Using that information you could try to use the Advanced JSON Editing option in an automation rule Edit Issue action to set the field.

Mimi Peters

Thanks Trudy,

I have read it serval times and would not understand.

Is it possible for me to create four distinct roles based on Jira groups (departments), and then employ automation to ensure that if a person belongs to Jira group A, only users within Jira group A can view those tickets, while excluding others? Similarly, if a person belongs to Jira group B, they can only access tickets created by members of group B.

Is this possible in Team managed jira?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud