Problem
When managing issues from the CLI, I can delete/trash an issue but cannot archive it.
Archiving is a distinct Linear action: it removes no-longer-relevant work without treating it as deleted. Right now, archiving requires leaving the CLI or calling the GraphQL API directly.
Proposed change
Add a command to archive an issue:
linear issue archive <issue-id>
It should:
- use Linear’s
issueArchive(id: $id) mutation instead of issueDelete;
- resolve issue identifiers consistently with existing issue commands;
- prompt with the issue identifier and title before archiving;
- support
--confirm / -y to skip the prompt; and
- clearly report that the issue was archived.
I’m already working on this and am opening the issue to follow the project’s contribution guidelines.
Alternatives considered
No response
Problem
When managing issues from the CLI, I can delete/trash an issue but cannot archive it.
Archiving is a distinct Linear action: it removes no-longer-relevant work without treating it as deleted. Right now, archiving requires leaving the CLI or calling the GraphQL API directly.
Proposed change
Add a command to archive an issue:
linear issue archive <issue-id>It should:
issueArchive(id: $id)mutation instead ofissueDelete;--confirm/-yto skip the prompt; andI’m already working on this and am opening the issue to follow the project’s contribution guidelines.
Alternatives considered
No response