The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Using subscriptions to notify on JSD Incidents

Rosey
May 8, 2019

We have a data center JSD install - 3 nodes behind an F5.  Each node can easily handle the load we are seeing to date.

We have a request to improve visibility on incidents coming in - right now, if something hits a project and it's unassigned, there is no notification going out.  We are using components, and component leads - but that only works when a component is assigned to the ticket - and that isn't always happening.

The idea is that create some filters to show unassigned, open incidents for a project - and then subscribe to that project.  The notifications would be set to run every 15 min, and only send an email if something hits the filter.

My concern is that I could see 400 of these subscriptions set up for the different teams - meaning I've got 400 JQL queries hitting the farm every 15 min.  While right now our farm is way overbuilt - this would be an easy way to swamp the boat.  Or maybe not - I don't have enough experience w/ JSD to know - maybe this is nothing.  I'd like to think that if it was a risk, Atlassian wouldn't allow you to create it but that isn't realistic.

Anyone have any thoughts on this solution?  I just need a way, out of the box (preferably) to alert teams that they have tickets they need to attend do without having them log into JSD.

0 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events