Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
Sign up Log in

Automating the adding of stakeholders to incidents?

Rob McBride
Contributor
August 14, 2024

Hi 

We are a cyber security company, and we are using JIRA to manage cyber security events / incidents across our different clients, as part of our SOC service.

We have a use case, which seems simple enough, but does not seem possible to implement... any help would be very gratefully received šŸ™

How we have currently set things up:

1. Customers currently raise potential incidents as a service request.  They are automatically assigned to an Affected Service based upon the URL of the person raising it - we have 1 affected service per customer name.

2. We review the service requests and if deemed to be an incident, we use an automation rule to convert this to an incident (it closes the service requests and creates an incident).

3. Once it is an incident, we perform a review to determine the criticality/classification.  We have a custom field for this which can be set to Red / Amber / Green.  There are 3 automation actions called "Classify as Red", "Classify as Amber" and "Classify as Green".

WHAT WE ARE SEEKING TO DO:

Based upon the classification and affected service, we are trying to automatically stakeholders or watchers to the incident ticket.  These stakeholders are customers, so they are unlicensed, but we have assigned them a stakeholder license in JIRA.  Note: We have premium licenses.

For example, if we have a Ransomware incident (RED) at a specific customer, we want to automatically add certain stakeholders from our customers to the incident ticket and not rely upon a SOC analyst manually adding them.

THE ISSUE:

It appears to be possible to automate the adding of Watchers to an incident, but not Stakeholders?  Whilst Stakeholders can be external / unlicensed, it doesn't appear that watchers can be...

Many thanks for any help in advance.

 

1 answer

1 accepted

3 votes
Answer accepted
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 14, 2024

Hi @Rob McBride ,

If your intention is to share the incident details to unlicensed users, then make use of request participant field which can be updated using automation rule.

Project settings --> automation rule --> THEN: Edit issue --> Request participants. 

Users in request participant field does not consume the license. You can just add any email ID in the field.

Rob McBride
Contributor
August 14, 2024

Amazing! Thank you.  I have to say JIRA do not make this easy with Stakeholders, Watchers, Request Participants... Request Participants is the one I need, though!

Like ā€¢ # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events