Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

automtically set epic restriction level to all children issues

Hi, 

I would like my issues inherit restrictions access from their parent epic. Is that possible? 

As of today, the only way is set Epic restrictions, and do the same for each created issue. 

1 answer

0 votes

Hello @Adil

Thank you for reaching out.

Today, all the issues in your project have the same restrictions added under project settings > Permissions and this is applicable for ALL issue types in your project (Epic, Tasks, Story, etc).

Explaining better, the users added to the permission scheme of your project will have the exact same permissions for Epics or child issues, and there is no way to add any restriction based on the issue type with the project permissions.
P.S: This scenario is not applicable only when you have Epics and child-issues in different projects, where each issue will have the restrictions of their respective projects.

That being said, the only way to restrict access to a specific issue-type in a project would be by configuring an security level. In that case, you can configure an automation rule to properly copy the security level from the Epic issue to its child issues when they are created. This would be the steps:

  1. Navigate to your Project > Project settings > Automation
  2. Click to create a rule. If the Epics and child issues are from different projects, click on Global Administration > Create a rule
  3. Create the following rule:
    Screen Shot 2020-07-22 at 15.50.41.png

Let us know if you have any questions.

I'm trying the same thing in a next-gen project and I can't get it to work. I also tried using Parent instead of Epic, but the condition is always false.

 

chrome_m0dFAztRmc.png

@Petter Gonçalves could you please confirm that automation in next-gen supports the Epic or "Parent exists" condition?

Hello @Maurizio Margiotta

Thank you for reaching out.

I cannot remember if I was able to make the condition "If: Parent Exists" work in Next-gen project before, however, Security Levels are not available for Next-gen Projects, so I believe your rule will not work unless you decide to use a classic project.

We have the following feature request to implement this feature on Next-gen:

Limiting issue visibility to certain users (security levels) 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Let us know if there is anything else we can help with.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,193 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you