WARNING: Script is under Development and wasn't tested in any other JIRA environments except the one used in my company
These are scripts which are supposed to be used as an actions in Jira's Project Automation. It performs some basic analyze on incoming Incidents, trying to find if there are any related Incidents, or if this Incident is already being investigated in another issue. Also, based on it's findings, it can automatically create linked Problems for further deeper investigation of the Incidents. All this is required to improve Problem Management process of first and seconds levels of Tech Support.
- Scriptrunner (obviously). I've tested it on 6.31.0
- Jira (obviously). I've tested it on 8.8.0 only, but versions below also should be good.
- Issues must have at least one Component (in our company we set Component to server's hostname, so script's JQL use components to identify the server)
- Component must be unique enough to group all your incoming alerts in rather small group. E.g. Component = Server's Hostname.
- Issues summary must be pretty unique, and should not contain any variables that change for one Incident from time to time, since both Component and Summary are used to group issues. E.g:
//Good for script
Diskspace / on hostname1.domain
Diskspace /var on hostname2.domain
Load Average is high on hostname2.domain
CPU Usage is high on hostname3.domain
//Bad for script
Diskspace / is 68% used on hostname1.domain
Diskspace /var is 11% used on hostname2.domain
Diskspace / is 91% used on hostname2.domain
Load Average is 8.5 on hostname2.domain
Load Average is 9.3 on hostname2.domain
- Jira must have 'Issue linking' enabled. By default script is using link name 'Problem/Incident' with Outward and Inward Description causes/is caused by respectively
- Based on Component and Issue links: finds and reports Incidents and Problems that may be related or which has this issue being investigated in.
- Reports any strange behavior (e.g. there are too many opened Incidents with this component, or there were too many such Incidents in last 12h, etc)
- Automatically link current issue to the problem, if it finds open Problem which already has Incident with same Summary and Component linked to it
- Find Repeatable Incidents (which get created on Daily or Weekly basis at approximately same time)
- Automatically creates a Problem and links all related Incidents to it if it finds repeatable Incident of any kind which has no Problem where it is being investigated
- [Almost] Automatically creates a Problem if it finds any strange behavior (at this point made the code human-friendly and ready to add any additional logic)
- Helper rule to be able to get all linked tickets into the Problem's comment to be able to perform 'human' analyze.
- Helper rule for setting up issue's fields based on ticket desciption.
- At this point it is just a sceleton. Though can be used for some more complicated logic in future.
Since this is not a plugin, but just a couple of automation scripts, some manual steps are required to make it work. Most likely you must have Admin access to Jira, since 'Scriptrunner script' action for automation available only to Admins. All next parts can be done totally independent.
If you worked with Jira Automation before - you probably know what you're doing. If you haven't - please be extra careful. You'd better try some of it's functionallity first to not only follow the instructions but understand what you are doing. 0) Make sure that you fit the requirements in What is required for it to work? section
- Go to Project Settings -> Project Automation and click 'Create Rule' button (from now you can also create the rule on Global Administration, since you can add some custom project-level settings in switch-case part of the code)
- In 'New Trigger' section choose 'Issue Created' and Save.
- In 'Add component' section choose 'New Condition' -> 'If / else block'. Click 'Add conditions...', and select 'Issue fields condition'. Select 'Creator' 'is one of' and type the user or users which are doing automated Incident creation in you Jira. Click Save.
- Click on your created condition on the left, and click on 'Add conditions...' again. select 'Issue fields condition'. Select 'Issue Type' 'equals' and select Incident from dropdown menu (it can be any type, but at the moment script has Incident type hardcoded, though it can be easily be changed). Click Save.
- On the left, click on (+) sign relative to newly created "If: all match" block. Choose New action. Select 'Execute a ScriptRunner script' action.
- On the 'Note' enter any desciption you need. Then copy the content of 'possible_problem_advisor.groovy' and paste it to Script field. Wait for some time till script got analyzed. May get 4 lines with exclamation marks, it's ok. Be sure there are no other Errors. Click Save.
- Name your automation rule and click Turn it on.
If you also need problem analyzer, then create another rule
- Choose Manual trigger and select a group(s) of Users who will see a button in tickets. Click Save.
- Choose New Action and select 'Execute a ScriptRunner script' action.
- On the 'Note' enter any desciption you need. Then copy the content of 'problem_analyzer.groovy' and paste it to Script field. Wait for some time till script got analyzed. You might get one Warning and one error in timeInRed definition. Ignore it and click Save.
- Name your automation rule (note that it's name will appear in Issue menu) and click Turn it on.
- Now all selected groups of users must see additional option in issues' More dropdown list.
Installation process is same as for Possible problem advisor, however I will not describe it, since setCustomFields.groovy is not flexible, and most likely you will modify this rule for your case.