4

We "use" JIRA as our ticketing system, but "use" is a real stretch. We have no standards, no templates, no "best practices" documentation for writing a proper JIRA ticket. So I'm spearheading the movement to create such a doc.

It's bad. Real bad. Sometimes, the reporter just copies-n-pastes a stacktrace and submits the ticket without providing any context, backstory, or directions to reproduce.

I was wondering if anybody had some good input for what format/template we could use and enforce so that I never get a lousily-written ticket assigned to me ever again! Thanks in advance!

herpylderp
  • 2,017
  • 3
  • 21
  • 27

1 Answers1

5

The basic information needed in any error report:

  • What exactly did you do?
  • What exactly did you expect to happen?
  • What exactly happened instead?

There's a bunch of other information that can be crucial, but depends on the specifics of the system and your environment - things like what user account was used, what domain objects were being worked on, what server the error occurred on, etc.

But also be careful that your effort to increase ticket quality does not end up discouraging people from submitting tickets at all - that's what happens when you cram everything you can think of into a template and force people to fill out all fields even when most of them don't apply to every ticket.

Michael Borgwardt
  • 51,037
  • 13
  • 124
  • 176