Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Can you set-up a project where users will only have access to the ticket he/she is in?

Can you set-up a project where users will only have access to the ticket he/she is in and is assigned, tagged and made watcher to but not all the other tickets in the same project?

3 answers

2 accepted

4 votes
Answer accepted

@AA_PH 

Hey,

I have another beautiful solution for this requirement..

Please set  the 'Browse Project' permission to 'Current Assignee' alone. (This will allow all users to view the Project name under the List of All projects, but they can't view the issues)

Set the 'Assignable User' permission to 'Application Access (Any Logged in user)' which you can select any user over the Assignee field.

This will work 100%, I am using the same in multiple projects' configurations.

If you want to use any other User Picker 'Custom field' also would be suitable for this type of requirement. Just use that 'Custom Field' name in the 'Browse Project' permission.

That's it.. You will definitely thank me for this.. haha.. just kidding..

Cheers,

Akbar. :)

@Akbar Pasha looks very promising!!!

Will review and feedback.

Thanks in advance! Crossing my fingers this is it! :)

Like Akbar Pasha likes this
3 votes
Answer accepted
Fadoua Community Leader Mar 16, 2021

@AA_PH 

It is a lot of work but yes it can be done by using issue security. For more information please click on the link below:

https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html

If you have any questions let me know

Best.

Fadoua

@Fadoua this is very useful, will review, thanks much!

Do you know the answer here?

If you implem permission scheme and issue security scheme which will be followed?

Both.  The user access to the project is checked at the permission scheme level, and then again at each issue.

Like AA_PH likes this
1 vote
Fadoua Community Leader Mar 17, 2021

@Akbar Pasha  Thank you for sharing this trick! However I see a small problem here if Permission Scheme is being shared with other projects your trick won't work.

@AA_PH  Just something to keep in mind. Please let us know how it goes.

Best,

Fadoua

Thanks for the insight as well @Fadoua 

Like Fadoua likes this

Suggest an answer

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

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

459 views 19 23
Read article

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