dusk botgive a jira issue to the teammate you name
give the issue an owner before it spends another week in limbo. a bot can find a jira issue, look up the teammate you name and assign it.
you can also choose the project default or clear the owner. put a confirmation step in the routing routine; assignments don't wait for sending approval.
assign issue, in plain words
one vague name can send work to the wrong desk. give the bot the issue and a teammate's name or email. when several people match, have it show who it found before choosing. a separate user search can help.
project default and unassigned mean different things. leaving the person out can clear the owner. if the lookup fails, the bot should stop rather than quietly unassign the issue.
a routine to copy
paste this into a chat with your bot
each weekday at 10, find unassigned invoicing issues mentioning 'tax receipt'. propose devin rowe as owner. show the issue titles and the person you found here. if several people match, show them and ask which one i mean. ask me before you change anything. assign only the issues i confirm, then report the result. never clear an owner or substitute another person after a failed lookup.- when
- weekdays at 10
- needs
- jira connected with read and write
what comes back looks like this (an example)
routing result
inv-51: tax receipt missing for larkspire co.
new owner: devin rowe.
inv-58 remains unassigned; no approval to change it.good jobs for it
- route a new billing bug to the person covering that queue
- hand an issue to a new owner after matching the right person
- return a misrouted issue to the project default
- clear an owner only when the team wants the issue back in the unassigned queue
before it runs
dusk bot counts Assign Issue as a change: it alters something in Jira, and the sending setting does not cover it. a bot you allow only to read can never call it.
the permissions Jira asks for to run it: write:jira-work, write:issue:jira, read:jira-user, read:issue:jira.
how to start
- connect jira with read and write for this bot
- name the project, issue rule and teammate; read the matched person’s details
- allow only issue search, user lookup and assignment; include the ask-first instruction
- open the first issue in jira and read its owner; pause the routine when cover changes
limits worth knowing
- privacy settings can block name or email searches. report the missing match instead of choosing someone else.
- missing person is not permission to clear the owner. stop after a failed lookup.
- keep approval in the routing instruction. the sending setting covers sends, not jira assignments.
- display names can repeat. compare the matches before routing work.
the details it works from
| input | required | what it is |
|---|---|---|
issue_id_or_key | yes | The ID or key of the issue to be assigned. |
account_id | no | The Atlassian Account ID of the user to assign the issue to. |
assignee_name | no | Name of the user to assign the issue to. |
from composio's catalog for Jira (action JIRA_ASSIGN_ISSUE, read 12 november 20264). your bot fills these in from what you tell it.
try it in 2 minutes
- connect jira with read and write
- name one issue and its intended owner
- ask to see the person found before any change
- confirm, then read the saved owner in jira
mistakes people make
routing by first name alone
ask to see the matched person when names overlap.
relying on sending approval
include a confirmation step before assignments in the routine.
questions
can i assign a jira ticket using just an email address?
yes, the lookup accepts email or display name. privacy settings can block it. have the bot show the person it finds.
is the default assignee the same as unassigned?
no, they lead to different queues. default chooses the project’s default owner. unassigned removes the current one.
will it ask me before reassigning tickets?
only if you tell it to ask. jira assignments are app changes. the sending setting does not hold them.
sources
read next
put a clear test update on a jira issuetest evidence where the team can read it.
a jira assistant that explains what changedread the issue history before the verdict.
an ai assistant for product managers with scattered contextbring the evidence to the next decision.
claude connectors: connect the job you actually needpick a task before you connect an app.
an airtable assistant that learns the table before writingread the fields before filling the rows.
an asana assistant for the work between tasksfind the work holding up the handoff.
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].