change a linear issue without replacing the wrong details

fix the deadline while the rest of the ticket stays intact. the bot finds and reads a linear issue, then changes the date, owner, priority or description you name.

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

labels replace the whole label list. edits skip sending approval, so put a preview-and-agree step in the job before giving it write access.

pixel art: a lime pixel bot and a purple pixel bot beside the Linear mark on a white tile, a notebook and an alarm clock and a calendar, on a grassy meadow in front of sand dunes by the sea, one saying "correct the due date"

where it helps

correct a delivery date after its owner confirms the new day
replace an old description with agreed steps to reproduce the problem
hand an issue to a new owner after matching the person to your team
set an agreed priority without touching the project or labels

the short version

name the ticket and the exact field to change. the bot finds the existing issue and reads it before editing. new owners and states need lookups in your workspace and that issue's team.

labels replace the full list; they do not append
a team move with state, project or cycle changes takes two stages
a failed second stage can leave the team changed; inspect before retrying

step by step

connect linear and give the corrections bot read and write.
allow issue and field lookups plus issue updates. leave unrelated tracker changes out.
try one date correction. ask for the old and new date together, then agree to the edit.
schedule the weekday overdue review once the saved date is right. Pause stops future runs.

send this to your bot

paste this into a chat with your bot

each weekday at 4:30, find open linear issues in the ops team whose due date has passed. show me each one here with its title, owner and current due date, and ask me what the new date should be.

ask me before you change anything, change only the due dates i give you, then tell me the saved dates. never change teams, labels, owners or priority.

when: weekdays at 4:30
needs: linear with read and write; allow team issue lookup, required field lookups and issue updates

what comes back looks like this (an example)

after your confirmation
ops-62: packaging check for orin at mossvale studio
- previous due date: 18 november
- saved due date: 20 november
no other changes.

what can go wrong

labels replace labels. an empty list removes them all. read the existing list before changing it.
team details must fit. states, projects and cycles need lookups for the issue's team.
read the issue before retrying a failed move. the team may have changed even if the second stage failed.
keep the date review supervised. write access permits edits without a sending approval card. the routine above tells it to ask.

permissions and asking first

dusk bot counts Update issue as a change: it alters something in Linear, and the sending setting does not cover it. a bot you allow only to read can never call it.

inputs

input	required	what it is
`issueId`	yes	Identifier of the issue to update.
`title`	no	New title for the issue.
`teamId`	no	UUID of the team to move the issue to.
`cycleId`	no	UUID of the cycle (sprint) to assign this issue to.
`dueDate`	no	New due date in ISO8601 datetime format or YYYY-MM-DD TimelessDate format (e.g., '2024-12-31' or '2024-12-31T23:59:59Z')
`stateId`	no	UUID of the workflow state to transition the issue to.

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

try it in 2 minutes

connect linear with the lookup and update actions
name one ticket and ask for its current due date
give a new date and ask for a preview
agree to that change, then open the issue and read the saved date

quick checklist

the title and owner match the issue you meant
only the intended fields appear in the proposal
the routine asks before it changes anything
the saved issue has the agreed values

mistakes people make

sending just the new label

ask the bot to keep the old labels in the replacement list.

retrying a failed team move immediately

read the issue first. the team move may already have happened.

questions

can it add a label without losing the others?

yes, if it keeps the complete list. read the current labels first, then include every label you want to retain.

does changing a date ask me first?

put the ask-first step in the instruction. sending controls do not cover date edits. read only blocks the edit entirely.

can i describe the owner or state in normal words?

yes. you name them; the bot looks them up. if a name fits several people or states, it should ask you to choose.

sources

dusk bot docs: files and apps
dusk bot docs: routines
dusk bot docs: sending and approval settings
composio, Linear toolkit (catalog version 20261101_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].