You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi all. I'm setting up Jira Service Desk to manage ongoing maintenance for several web applications. My goal is to create around five issue types that are simple to choose but also allow for some reporting on the type of work we do, which is primarily back-end python. My idea right now is:
Bug - software not functioning as intended
New Feature - adding new functionality to the project
Improvement - no change to functionality, but improvement in speed, stability, elimination of tech debt, etc.
Service Request - default type for issues that are emailed in from customers, can be converted to other type if necessary
Dependency/Service Update - updates to dependencies and external services
Incident - post portem on an outage
I've also considered the ITIL service desk process, which is:
This covers everything well, but I'm not sure it translates well to developers. It also drives the need for subcategories, for example, Change > New Feature, Dependency Update, Improvement.
Anybody using an issue tracker for web maintenance? What categories would you want to see if you were working on these projects?