put a clear test update on a jira issue

give the next person enough detail to repeat your test. a bot turns your notes into a jira comment with steps, links and a clear result.

by the dusk bot team · checked 12 november 2026 · how we made this

it finds the issue from the project and problem you name. posting counts as a send and asks first by default. read the wording and audience before you approve.

pixel art: a coral pixel bot and an indigo pixel bot beside a tile saying Jira, two chat bubbles and a shield with a tick, on a grassy meadow in front of snowy hills and green fields, one saying "test update ready"

where it helps

show how checkout failed. include the steps and observed result.
leave a release check people can follow. use links with descriptive words.
keep an investigation within its audience. confirm the existing project role first.
answer with evidence. separate expected behaviour from what you actually saw.

the short version

put the evidence beside the issue. the bot finds the work through jira search, then prepares a comment. it supports lists, bold text and mentions. clickable links need words attached, not bare web addresses.

you can limit a comment to a project role or group. check the actual names first. group restrictions need an administrator to enable them. if the audience can't be confirmed, stop.

step by step

connect jira with read and write access so the bot can add comments.
set sending on your behalf to ask every time. try one comment on an issue you can inspect.
careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.
read the issue, audience and links before allow. schedule the weekly review once that looks right.

send this to your bot

paste this into a chat with your bot

every thursday at 4, find issues in the payments project that moved to done this week and have no comment from the last seven days. for each one, write a short comment asking the person assigned what they tested and on which device. show me the issue and the comment here and post only the ones i allow. never mention anyone else, add customer details or limit who can see a comment unless i ask.

when: thursdays at 4
needs: jira connected with read and write access for this bot

what comes back looks like this (an example)

comment proposal for pay-73
what did you test, and on which device?
no mentions or customer details. no visibility restriction requested.
post this question to pay-73?

what can go wrong

group restrictions need setup. an administrator must enable them. role and group names can differ between projects.
bare web addresses won't become clickable. ask for links with descriptive words.
use ask every time to review each comment. a daily sending amount lets comments go out within that limit.
put the update on the right issue. match the project as well as the title.

permissions and asking first

dusk bot counts Add Comment as a send: it reaches people or moves money, so it waits for your Allow (unless you set a daily amount, or the bot is on Full access with no sending rule, which lets it send up to 25 a day). a bot you allow only to read can never call it.

the permissions Jira asks for to run it: write:jira-work, read:comment:jira, read:comment.property:jira, read:group:jira.

inputs

input	required	what it is
`comment`	yes	The comment text.
`issue_id_or_key`	yes	The ID or key of the issue to add the comment to.
`visibility_type`	no	Specifies the type of visibility restriction for the comment.
`visibility_value`	no	Name of the group or role that can view the comment (required if visibility_type is set).
`additional_properties`	no	Additional properties to include in the comment request body.

from composio's catalog for Jira (action JIRA_ADD_COMMENT, read 12 november 2026⁴). your bot fills these in from what you tell it.

try it in 2 minutes

name one issue and the test result
ask for a comment draft without posting
read who can see the comment and open its evidence links
approve only the comment you read

before you post

the issue belongs to the right project
observed and expected results stay separate
links have words people can click
mentions and audience match your intent

mistakes people make

writing 'tested' with no device or result

say what you tried, where you tried it and what happened.

asking for 'internal' without an audience

confirm the project role or group. stop if it can't apply the restriction.

questions

can the bot make a jira comment internal?

it can request a role or group restriction. those names must fit your jira setup. ask it to confirm the audience before posting.

can it mention a teammate in the comment?

yes, by username or display name. ask for the mention only when you mean it. review the person alongside the proposed text.

does it support a test checklist?

yes, with lists and emphasis. say what passed, what failed and what nobody tried. give the next tester something they can repeat.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: sending and approval settings
composio, Jira toolkit (catalog version 20261104_00), checked 12 november 2026

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].