I am looking into expanding the use of JIRA to support ITIL incident management. Initially I want to pair incidents from HPSM with issues in JIRA.
My question is if there are any best practices for using issue types in JIRA to represent incidents from ITIL? I want to differentiate incidents from bugs so I have a view of defects found before/after the product is released. Is it as simple as just creating an incident issue type or ... ?
Secondly I want my solution to be able to support the use of JIRA service desk in the future.
To keep it really simple, yes!
A new issue type of Incident is the most simple, and probably the most clear way to do this. If you go with an incident issue type, you'll be able to give it different fields and workflows to the other issue types as well, if you want. And it will fully support Service Desk in the future too.
I suspect I'm not adding much to @Nic Brough [Adaptavist]'s answer, but I'm reasonably experienced with both tools, so I thought I'd add in my $0.02 worth.
When someone talks about the Incident Management from HPSM, they are often including Service Incident and Problem tickets because they are both often touched by the same Incident management teams. Sometimes they are also talking about Interaction tickets because they are in the "incident" table in HPSM. And very occasionally, it's just Incident tickets.
JIRA doesn't have a simple way of representing the rules of what kinds of tickets can and can't be interlinked (e.g. an problem can't be linked to an interaction unless it's a closure). To be honest, I don't think it's worth caring about this.
I think what will happen is this:
That should sort out your incident sync.
When you start doing Service Desk in JIRA, you will create a new project, which will be a Service Desk project. It will have nothing to do with the Incident tickets in JIRA.
I'll try to write up a bit more detail about JIRA service desk sync to Service Manager Interactions if you are interested, but that will be some time in the future if ever.
I have another customer embarking on a vaguely similar project, so there might be some way of leveraging each others' work. By the way you might find this python code helpful for ( reading from | writing to ) Service Manager: http://www.ifost.org.au/Software/sm-tools/smcli.py
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs