Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,677
Community Members
 
Community Events
168
Community Groups

"Restrict to" Field for Automation

Edited

Hi, 

I would like for each new epic created to assign default restriction rules.

This raises two questions:

1. How to apply the rule to epics only. Preferred solution since permissions seem to be inherited.

2. What is the exact name of the `Restricted to` field.

So far, I have tried the following with no success:

Screenshot 2022-08-16 133249.png

Any help will be welcomed.

Thanks

 

1 answer

1 accepted

1 vote
Answer accepted

@Alexandre Teyar 

1. How to apply the rule to epics only. Preferred solution since permissions seem to be inherited.

  • You can use automation with conditionals to trigger only when the issuetype = epic

 

2. What is the exact name of the `Restricted to` field.

I hope I helped you.

If this post was helpful, mark it as Accepted, so you can help others who may have the same difficulties.

If your question has not been resolved, please post again with more details.

It does help indeed, thanks for the explanation!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

An unofficial way to monitor a JSM mail handler for errors

...eturns true if any content is returned for the webResponse.body.data.first s...

718 views 3 20
Read article

Atlassian Community Events