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

Limiting visibility for Jira Service Desk project for internal use

Kat Marketplace Partner Oct 03, 2018

I want to be able to track action items from goal setting meetings. Some actions need to have the visibility restricted to the leader ship team and others need to be visible to a single team member.

Could this be with a Jira Service Desk project that is only visible to the leadership team and setting the team member as a customer on the tickets they need to see?

I understand this means the tickets would not be in their queues to action.

I'm concerned using issue level security on a standard Jira project will not prevent different team members being able to see each other's tickets

I'm open to suggestions.

1 answer

0 votes

Hi @Kat 

I would work with Jira software for this and issue security scheme. This would work well. I'm not sure I understand your concerns about using it. Can you please elaborate on this?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events