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,553,276
Community Members
 
Community Events
184
Community Groups

Can I "@" someone in an internal comment on a task that is not already in the project?

I'm wondering if I @ someone in an internal comment on a task, this is not in that project, will they be notified and then able to view that task? Or would they need to be added to the project to view the comment they were tagged in?

Ideally we wouldn't have to add them to the project, because we would only want them to see the task that they were tagged in, where they were asked a question. Is this possible?

Thank you!

1 answer

0 votes
Dan Breyen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 11, 2023

Hi @Daniella_Bina I'm reading into your question a little, so correct me if I'm wrong.  If they are not an Agent in JSM, but they are a Jira Software user, you can setup their access to have Browse and Comment privileges.  Then the @ functionality will work.  They won't count against your licenses because they're not agents.

I did that for my programmers, as they won't interact with customers, but they may be working on customer issues.  This way they can see the interactions going back and forth between agents and customers, and include a comment if they have one.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events