Ask Rovo to apply your team’s checklist templates

What the Checklist agent can do

When Rovo AI is on, the agent can create and update checklists from the issue, find and apply saved templates, and draft status updates — including from comments and Ask Rovo. Administrators can add site or project guidance for naming and tone. When you ask for a process-style list — Definition of Done, a QA testing checklist, a release checklist — the agent looks up a matching template first.

• Create or update a checklist from the issue summary, description, and comments.
• Find, apply, create, and update saved project or global templates.
• Summarize what is done, blocked, or still open — a comment you can send as-is or edit.
• List the item statuses this project actually offers.
• Follow site or project agent guidance for naming and tone.

Why prefer a saved template

A generic “make a QA list” prompt can invent a look-alike pass that is not your team’s. Product practice is AI for draft, templates for scale. If the team already saved Definition of Done or a QA template, ask Rovo to apply that template. The wording stays the same, Protected structure stays locked, and the automation guide can still require the same list before Done.

Starting lists live in the checklist templates. A short description on the template’s Advanced tab helps the agent tell similar names apart — a “when to use this” blurb for people and for Rovo.

When to use Rovo versus automation

Let the automation guide add the default template on create or status change. Use Rovo when the issue is unusual and a human wants the right saved list in the moment — “which saved QA template fits this bug?” Keep rules for the happy path; keep chat for the exception.

Prerequisites and limits

• Rovo AI must be enabled on the Jira Cloud site.
• Review the proposed list before you apply it — the agent is a teammate, not an autopilot.
• Protected templates can be applied from chat, but they cannot be rewritten there. The agent can tick items and change status, not change the structure. Only one Protected copy is allowed per issue.
• Agent guidance can steer naming and tone. It cannot override Protected templates, workflow validators, or the agent’s safety rules.

Example prompts

1. “Apply our Definition of Done template to this story. Do not invent extra items.”
2. “Which saved QA template fits this bug? Apply it and list anything still open.”
3. “Summarize checklist progress on this issue and draft a comment for the reporter.”
4. “What templates can I use on this issue?”
5. “Create a project template named Release from the checklist on this change, then show me the items.”
6. “What does our site guidance say about naming checklists? Follow that.”

Ask from the issue, then review

1. Open a Jira work item and choose the Checklist agent in Ask Rovo. Checklist for Jira needs Rovo AI enabled on the site.
2. Ask for a use case your team already standardized — Definition of Done, QA, release — so the agent prefers a saved template over a new list.
3. Review the confirmation. The template name is shown before apply, the same as Add → Add from template on the panel.
4. Tick items and set statuses on the issue as usual. Protected lists stay locked; a project or Jira administrator must unprotect the template before chat can edit its items.
5. Let the automation guide keep adding the default. Use Rovo for the odd ticket. Full product how-to is in the product docs.

Pair it with templates and automation

Save the lists you want Rovo to apply in the checklist templates. Auto-add the defaults with the automation guide. Keep Definition of Done Protected so chat cannot quietly rewrite the ship bar. The agent still applies that template; it just cannot change the steps.

FAQ