Currently, when a Sentry issue is archived, any linked Linear issue is automatically marked as "Done". This behavior doesn't align with our workflow, where we archive issues for various monitoring purposes (e.g., waiting for re-occurrence, monitoring frequency, or user impact) rather than indicating resolution. Archiving is used as a temporary state, not a resolution state, and shouldn't automatically close linked Linear issues. The current behavior incorrectly suggests that archived issues are resolved, leading to premature closure of Linear issues.
Solution Brainstorm
A configuration option that allows to specify whether archiving a Sentry issue should affect the status of linked Linear issues. This would:
Maintain the current behavior for teams that want it
Allow teams to keep Linear issues open when archiving Sentry issues
Better support workflows where archiving is used as a temporary state rather than a resolution
Problem Statement
Currently, when a Sentry issue is archived, any linked Linear issue is automatically marked as "Done". This behavior doesn't align with our workflow, where we archive issues for various monitoring purposes (e.g., waiting for re-occurrence, monitoring frequency, or user impact) rather than indicating resolution. Archiving is used as a temporary state, not a resolution state, and shouldn't automatically close linked Linear issues. The current behavior incorrectly suggests that archived issues are resolved, leading to premature closure of Linear issues.
Solution Brainstorm
A configuration option that allows to specify whether archiving a Sentry issue should affect the status of linked Linear issues. This would:
Product Area
Settings - Integrations