Jira Ticket best practices



  • I've been with two very different companies that both use JIRA Tickets to track work done. The first was corporate company with some high standards when it comes to defining Tickets in Jira, the second a startup that merely writes down a description of needs to be done (Usually a one liner).

    Now the second has caused some issues around defining what is expected, information relating about the work, finding out exactly what needs to be done and so forth. I am currently in a position where I can strongly hint or suggest better practices.

    My question is - Is there a defined format/standard practice guide when creating Jira tickets to improve workflow?



  • User story best practices by Mike Cohn

    Here are some user story best practices by Mike Cohn:

    • Write user stories from the perspective of the person who desires the new capability in this format: As a < type of user >, I want < some goal > so that < some reason >.
    • Discussions are more important than whatever text is written.
    • Add detail by splitting a user story into multiple, smaller user stories.
    • Add detail by adding conditions of satisfaction which is simply a high-level acceptance test that will be true after the agile user story is complete.

    In addition, in Jira you can link them to related stories.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2