Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

QA process improvements with a checklist in Jira

Oleksandr Siryi_Railsware_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Oct 31, 2022

Even despite the fact that Jira was never made as a QA tool many quality assurance engineers are still ‘stuck’ with it as the need to stay in the same loop as the dev team outweighs the benefits of most dedicated test management platforms. 

That said, Jira is deeply customizable thanks to the plethora of automation rules at your disposal and a wide variety of specific add-ons on the marketplace. 

One of the more straightforward things you can do is to automatically add a checklist to a certain issue types and append checklist items upon issue transition. 

This simple automation that shouldn't take longer than a couple of minutes to set up will automatically (duh) add a checklist upon issue transition. Let’s imagine you are moving a ticket out of the backlog and boom - it has all the necessary steps you need to undertake in order to get it done like assigning the issue and adding the steps to reproduce the bug. 


This neat little trick also adds a bit of reusability as you only need to set up the checklists for your tests once. Then, once the issue is moved from the backlog it is automatically transformed into a test case (well, technically it would still be an issue with a checklist but you could work with it like you would with a test case). 

You’ll need the Smart Checklist add-on and the Automation for Jira app for this trick to work. You can give it a free try for thirty days to see if this fits your process. Once the add-on is installed, simply follow these steps:

  • Go to Automation for JiraAutomation Rules


  • Click Create Rule
  • Set When: New Trigger
    • Choose Issue transitioned 
    • Choose from status (e.g. Backlog) and to status (e.g. Selected for Development)
    • Save


  • Add component New Action

Automation rules_new action.png

  • Set New Action
    • Choose Set entity property


  • Choose Entity type: Issue
  • Set Property Key: com.railsware.SmartChecklist.checklist 
  • Add checklist template in Markdown formatting as the property value and add the following in the beginning {{"com.railsware.SmartChecklist.checklist"}}
  • Save ActionSave and Turn Automation On

You're done! Now every time an issue is transitioned from Backlog to Selected for Development, the proper checklist template will be appended to your issue. If you’d like to go one step deeper - set up the automation in a way that the issue is automatically closed once all the checklist items are checked as done. 



Log in or Sign up to comment