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

Possibility of assigning tasks to people who aren't member of the project

I want to assign a task to people in my organzitaion, but they aren't member of the project, in which the task is that I want to assign. 

These people shouldn't have access in this project but to this specific task. 

I just don't want that some people from my company will have access to hundreds of projects, because there is one task which is relevant for them in these projects. 

 Is this possible?

Thanks in advance for your help.

1 answer

1 accepted

1 vote
Answer accepted
Mikael Sandberg Community Leader Dec 02, 2022

Yes, this is possible if you create an issue security scheme, that would allow you to assign specific tasks to people so that they only have access to the task that they are assigned to.

Thanks for your answer @Mikael Sandberg !

Where could i set up this in the issue security scheme? 

Mikael Sandberg Community Leader Dec 09, 2022

Have a look at this KB. Basically you go to Settings > Permission schemes and create the scheme from there. I would recommend using project roles instead of groups when you can, that way you can control who have access from within the project instead of having to update group memberships. You would also need to change your permission scheme to allow users to set the security level and add the security level field to the screen.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events