2. Create an incident

Tutorial: How Jira issues affect Assets objects (ITSM)

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

After you've created your project, you can start working on it right away. Let's imagine we're working as front-line support, and we're reporting an incident.

Create an incident

  1. Create an issue in your project, and set its type to Incident.
  2. Write a summary. Let's say, "I can't send emails".
  3. Set the Affected business service field to Email service. What you're doing here is actually choosing the affected Assets object.

If you look at the incident you created, you can see that it's linked to an object in Assets. The details of your affected email service automatically appear in the Affected business service field.

Related workflow

Here's the workflow that your project uses for incidents, just so you know how the incident will move through it. You can always view it in Project settings > Workflows.

Get the work going

Let's transition the incident through it's workflow to see what happens to the Assets objects.

1. Confirm the incident

  1. Select Confirm incident to confirm it and proceed through the workflow. The status of the affected object changes to Incident in progress.
  2. Select Investigate incident to start the work. The status of the issue will change.

2. Investigate the incident

  1. Let's assume that you found the culprit, which is hardware failure. Select Hardware failure.
  2. Select the Related Server that you suspect is the source of the incident and confirm. The current user (you) will be automatically assigned to investigate. 
  3. Now that you've identified the culprit, the Related server from Assets is also linked to the Jira issue. Post-functions built into the template have updated the status of the Affected business service and Related server

3. Investigate failure

  1. Proceed to Investigate failure.
  2. When enough information has been gathered, resolved the issue with Resolve. This indicates that you have determined the incident's cause or that you were unable to reproduce the failure.
  3. For the sake of the example, let's assume you can reproduce the incident and have an idea of what's causing it. Change the issue state to Report problem to create a new issue of issue type Problem to begin tracking the underlying cause of this incident.

Next up

When you're ready to solve some problems, go to 3. Work on the problem.

Last modified on Sep 12, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.