Add an acceptance criteria checklist to Jira issues

Want to give software teams a clear and easy way of determining when a story is ‘done’?
Add an acceptance criteria checklist to Jira issues

Standardize checking off acceptance criteria

Developers and quality assurance (QA) testers want to check off a list of acceptance criteria on Jira tickets. They don’t want to update descriptions or add comments to confirm when criteria have been met. The problem is that Jira doesn’t offer a way of adding checklists to issues.

With Didit, you can create an acceptance criteria checklist ad hoc during backlog grooming and add it to your user story ticket. You could also create an acceptance criteria checklist template that gets added automatically to the story issue type. The app works with Jira automation if you need a more complex trigger.

See how stories are progressing at a glance

Everyone working on a project needs to see at a glance how their user stories are progressing. But opening issues one at a time is inefficient and a pain.

Didit allows you to add checklist custom fields to Jira board cards that show the progress on a checklist. Product managers, developers, and QA testers will all be able to see the percentage of acceptance criteria confirmed from the board view.

You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

More Information

Ensure issues are only closed if they’re truly ‘done’

It’s common for Jira issues to be moved to ‘done’ even if not everything is really done. But with Didit, you can set a validator on the transition, requiring that the acceptance criteria checklist be completed before the issue is closed. That way you can make sure you’re delivering the outcomes your customers expect. Learn how to do this, here.

Content

Related use cases