Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
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

Potential to add watchers that are not a part of the project

Hey!

After looking around in solutions and tutorials- I came to a conclusion that there's no good answer to my question:

Is it possible to add watchers to specific issues that are not a part of the project?

Thanks!

1 answer

0 votes

Hello @zilvinas_mickus

Welcome to Atlassian Community!

Per your description, I understand that you would like to have the ability to add a user as a watcher of an issue where he is not configured with the browser permission to access it. Is that correct?

Indeed, the permissions of a project do not allow you to add someone as a watcher that is not configured with the browser project's permission, since a watcher will receive notifications about the issue that he is not supposed to access.

That being said, if you want some users to access a single issue of a specific project and receive notifications as a watcher but not enabling them to access other issues in the same project, you can use the Issue security level to achieve your goal. These would be the steps:

1 - Create and add an issue security level to all the issues of your project, marking it to be added as default to the new issues created and configuring all the users/groups/roles that should be able to access ALL the issues in the project

2 - Create a user/group picker custom field (multiple-choice), adding it to your issue screens and to the security level you created. 

3 - Add the user/group picker custom field (multiple-choice) to your project notifications, so it will work as the watcher field

3 - In the Project permissions, allow anyone to have the browse project permission. The project restriction will rely only on the security level.

4 - Every time you need someone to access a specific issue, add him in the user/group picker custom field (multiple-choice), so only that issue will be visible for that specific user.

Please, take a look at the links provided and let us know in case you have any questions about the steps.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

335 views 9 7
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