Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to restrict creation of specific issuetype to Automation

SS
Contributor
April 25, 2022

I manage a large system with a lot of automation.

In this situation I have a Parent workflow, which uses ScriptRunner to create linked child issues in other projects. The script is set to run a 'Automation'.

The child issuetype is available in 30 different projects, in 4 issuetype schemes using two workflows.

What we don't want is for users in the projects to create this issuetype manually - it should only ever be created by automation from the Parent workflow.

I can adjust the Create permission validator on the child workflows to prevent users from creating the issue. But this also blocks the automation from working - even though the ScriptRunner clone function is set to 'run as' the Automation user, it still seems to check the permissions of the Current User.

We could use a ScriptRunner behaviour, but as this functions as a whitelist so it creates a maintenance burden.

 

Can anyone suggest a low maintenance solution to prevent users from creating certain issue types?

1 answer

0 votes
Ram Kumar Aravindakshan _Adaptavist_
Community Champion
April 26, 2022

Hi @SS

If you intend to restrict the Issue Types, the best and most straightforward approach will be to use the Behaviour.

An example is already available in the ScriptRunner Documentation.

To control the visibility of the Issue Type and to set it to read-only, Behaviour is the Best option.

There is no simpler approach to this.

I hope this helps to answer your question. :)

Thank you and Kind regards,

Ram

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events