Restrictions for team-managed project

[Maciej Oczoś]

I have set up restrictions for issue types, but these restrictions are only being applied to new issues. How can I apply these restrictions to existing issues as well? I attempted to write a script in ScriptRunner to address this, but I am unsure of the field ID required. 

Cheers

[Nikola Perisic]

Welcome to the community @Maciej Oczoś 

These restrictions will only apply for the new created issues. The restrictions do not apply to the existing issues.

[Maciej Oczoś]

Sure, we know that, but we need a way to automatically add these restrictions to the thousands of existing tasks so that we don't have to do it manually. Can you help with that?

[Nikola Perisic]

Sadly, you cannot apply restrictions to the existing issues. Each restriction is tied to both issue type and a project role. From that moment when you set the restriction only those roles will be able to see those issues. So, no, there isn't a way to apply restrictions to existing issues.

[Trudy Claspill]

@Nikola Perisic 

That is not true.

You can manually set restrictions on issues in Team Managed projects at any time by clicking on the padlock icon on the individual issue. That assumes that you have the Restrict Issue permission.

[Nikola Perisic]

@Trudy Claspill 

Thanks for the correction.

[Trudy Claspill]

Hello @Maciej Oczoś 

Welcome to the Atlassian community.

I'm not sure if it is possible to set issue restrictions on existing Team Managed issues through ScriptRunner.

However if you need to find the name of a field, follow the guidance on this page:

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

You may have to call the Jira REST API to make a change to the Security field.