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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,456,734
Community Members
 
Community Events
176
Community Groups

How to make a security scheme common to a task and its sub-task?

I have security scheme for task:

hr_viewers
  • User custom field value (Technical Experts) (Delete)
  • User custom field value (SMD) (Delete)
  • Project lead (Delete)
  • Reporter (Delete)
  • Current assignee (Delete)
  • Project Role (Project Managers) (Delete)
  • Project Role (Developers) (Delete)

but subtasks doesnt has this custom fields, and if we create subtask under task this filed cant copy own information to a subtask. How to make a security scheme common to a task and its sub-task?

2 comments

You don't need to do anything. 

The security level for a sub-task is inherited directly and automatically from the parent (and the scheme applies to every issue in the project)

@Nic Brough -Adaptavist- 

 

Yes, but I do not ask about it. People who access the request under this scheme will not see the subtask. Or am I wrong?

We're talked about custom fields, which are cant auto copy from parent issue

I think you have misunderstood.  The short answer to your question is actually "it already is common, sort of"

A security scheme applies to the issues.  When a sub-task belongs to an issue, it takes on the same security as the parent.   It might be more clear to say it has the same visibility.  If you can see the parent, you can see the child.  If you can't see the parent, you can't see the child either.

Okay, thank you. I will test this and update you.

@Nic Brough -Adaptavist- 

 

You're wrong.

I can't see subtasks under other user if set security level

 

User TEST from field SMD

2020-01-16 12.35.55 jira5.sam-solutions.net ec5ad0600f9c.jpg

 

 

User TEST if I add him manualy to fileld SMD in subtask2020-01-16 12.36.31 jira5.sam-solutions.net 91ab4586f3f0.jpg

@Nic Brough -Adaptavist- I will create a new request so that it is more understandable

This seems to support what I said earlier, I don't see what is inconsistent.

Not correct question, i rebuild this

I think it's a good question already, but asking again, phrased differently, is never a bad thing, it should help get more people to look at it.

Comment

Log in or Sign up to comment