Member-only story
LIFE HACKS FOR RESILIENT ENTREPRENEURS
The Problem with JIRA Tickets? You Can’t Recognize Topics and Patterns
Unless you put somebody in charge of managing JIRA tickets rather than just shifting them around.
“Let me create a JIRA ticket for this.”
In my role as product owner of Yonder, that’s the most dreaded sentence in my daily work.
Why?
We use JIRA not just for development work, but for all sorts of other work in the company. So there are lots of people who create JIRA tickets.
Here is what can go wrong.
1. Duplicate Tickets
Creating a ticket in JIRA is easy. That’s a good thing, but it’s also a bad thing. People create tickets without thinking twice if a ticket is needed. Here are some examples:
- It’s easy to automatically create a JIRA bug ticket from any service desk software you might use. So if two of your customers report the same issue, you’ll easily end up with two duplicate tickets — often with different titles and different problem descriptions. How on earth should your product and development teams ever plan their sprints like this?
- People write…
