What details should you put in your JIRA ticket

Dev and QA consistently face this issue of not being on the same page, or missing some details in the communication process of bug ticket filing. This causes un-necessary cycles between the Dev and the QA. Its important for the QA engineer to provide as much information as possible in the ticket so that the task is immediately actionable instead of falling in cycles of knowledge gaps.

So this is a quick post to summarise the top details that you should never miss from your JIRA ticket before sending it across.

  1. Title
  2. Priority
  3. Summary/Description
  4. Steps to reproduce
  5. Expected Result
  6. Actual Result
  7. Environment Detail
  • Platform: Android/iOS
  • OS version
  • Brand
  • Screen Size
  • RAM
  • Device type
  • Test mode

8. Screen shots

9. How frequently is it reproducible: Always/Intermittently

Here is my JIRA ticket to show you the details.

If you are a Dev reading this post, please comment your thoughts and/or mention any other details you would like to see on the ticket.

Hope the post is helpful. Cheers

Originally published at confusedcoders.com on April 28, 2018.

Data Scientist | Python programmer