Sprints are short for a reason. With that said, it is easy for tickets to pile up in the testing column. Actually, tickets can pile up in any JIRA column quite easily. If the QA team is small, this is even more likely to happen. A simple daily report/scrum can help avoid the chaos of a crowded JIRA column.

Reasons For Monitoring JIRA Columns

  • Allows the QA team to test the tickets that have been ready to test the longest.
  • Shows the Product Owner what is ready for approval.
  • Allows the team to see what is in progress.

With a simple Python script, it is easy to post into Slack the tickets in any column on the JIRA board. The report is easy to modify, and can include many features. Utilizing AWS Lambda, and the Bytelion sample code, https://github.com/Bytelion/JiraChecker/blob/master/how_long_ticket_been_ready_to_test.py, will provide a very easy report setup.

 

How To Setup The JIRA Monitor

Download the sample code, and then replace the values found inside the curly braces {}, with the string you desire. Example: {your team name here}.atlassian.net changes to bytelion.atlassian.net

  1. First, create a Slack webhook integration. If one does not already exist, visit our first article on integrating Slack. Then, see step 1 of that article to learn how.
  2. Then, set up an AWS Lambda, and then paste the modified sample code into said lambda.
  3. Finally, using AWS CloudWatch, create a daily schedule for when the report should be run.

Sample Features

  • How long has the ticket been there.
  • Who moved the ticket.
  • What is blocking that ticket.

Leave a Reply