How can we automate weekly QA ticket reviews in Jira

[Ravikiran Nagasetti]

We want to set up an automated weekly QA process in Jira where:

• A weekly QA task is created for each employee

• The task is assigned to a QA reviewer

• Each task includes 4 tickets to review:

  • 2 tickets created by the employee

  • 2 tickets actioned by the employee

• A standard questionnaire is completed for each ticket

The goal is to replace ad-hoc reviews with a consistent, measurable QA process to improve ticket quality and documentation.

What’s the best way to implement this in Jira—using Automation, custom fields/forms, or Marketplace apps? 

[John Funk]

Hi Ravikiran,

You can probably do most of this with Automation rules. You can set up a recurring task by following the guidance in this article. 

https://community.atlassian.com/t5/Jira-articles/Creating-a-Flexible-Recurring-Task-Issue/ba-p/2040862

You can supplement the automation rule by adding in actions to create the additional tickets. 

For the questionnaire, you will need to provide more information as to what that looks like/process.

[Ravikiran Nagasetti]

We want to implement an automated weekly QA process in Jira where:

Acceptance Criteria

• A QA ticket is automatically created for every active employee each week
• Each QA ticket links 2 “created” tickets + 2 “actioned” tickets from the review period
• A mandatory questionnaire is completed for each linked ticket
• QA reviewers are assigned automatically
• QA ticket cannot be completed until all questionnaire fields are filled
• Edge cases (e.g., not enough tickets) are handled with a defined rule
• QA results are stored in structured fields for reporting

Optional Reporting / Metrics

• QA completion rate per week
• Average quality score by employee/team
• Common failure patterns
• Trends over time

Assumptions

• We can reliably identify “created by” and “actioned by” in Jira
• Employees are identifiable as a consistent Jira user list
• Jira supports the required automation (rules, forms, custom fields, issue linking)