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

Notifying groups of agents on issue creation/updates/resolution

We have one large project for our entire IT department in JSM Server today. By using the "Bug Watcher" app, we ask IT staff to create filters for the things they want notifications about, and then watch that filter. Watching a filter will send them notifications when something matches that criteria. We primarily use the Component field, which is based on HR teams or IT services.

Bug Watcher isn't available in JSM Cloud, so we're exploring other ways of allowing IT staff to create their own filters to base their agent notifications on. Our organization is too big to individually assign or add people as Watchers, so we need a system that can take a ticket and assign it to a team that will then route it internally.

How are you handling notifying different teams of people in JSM Cloud?

0 answers

Suggest an answer

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

Atlassian Community Events