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

MM

[Trudy 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 Claspill 

[Trudy 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?

[Trudy Claspill]

I don't know. I have not had time to actually try to implement it. I am only able to theorize that it might be possible.

 I have not found any posts that show an example of setting issue restrictions in team managed projects. 

I will not be àble to spend time on trying this out until later next week.

[Mimi Peters]

I am looking at this feature but not urgent. It's nice to have and avoid moving back to Company managed. If later this week, you get a chance to have a look would be great, no pressure :) 

[Trudy Claspill]

Unfortunately I have not been successful in finding a JSON structure capable of setting an Issue Restriction for a Team Managed issue via Automation Rule.

It should also be noted that if an Issue Restriction is set on a Team Managed project issue, then Automation Rules set to run as Automation for Jira will likely fail, as per 

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

Before making a final decision about possibly switching to a Company Managed project instead, I recommend that you set up a Company Managed project for testing out that you can set the issue security level via automation and make sure that any other automation rules/functionality will still work as you expect.

I'm tagging @Bill Sheboy who has previously enlightened me about options in Automation Rules of which I was unaware, in case he knows of a way to solve this.

[Bill Sheboy]

Hi @Mimi Peters and @Trudy Claspill 

That does not appear to be possible yet.

I checked the v2 REST API edit metadata and that field was not listed as available for edits.  Then looking in the developer community, I found posts from people trying to read or change restricted issues.  It seems only Forge apps could do it, and there is an open defect for Team-managed projects with the v3 REST API that the issues are not returned either, limiting further investigation on the metadata from that route with v3: https://ecosystem.atlassian.net/browse/ACJIRA-2406

Kind regards,
Bill

[Mimi Peters]

just return from vacation. Thanks for the note