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
Highlighted

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
TAGS

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