What happens when I link a Pylon issue to a task?
Last updated: June 12, 2026
Question
When I link a Pylon issue to a task (or a task to an issue), does it change either one's status, move something to On Hold, or send a notification or status change when one of them is closed or completed?
Answer
No. The native issue-to-task association is purely informational. Linking simply shows the relationship in both sidebars - the Tasks module on the issue and the Linked Issues module on the task - and does nothing else.
Key details
When you link or unlink an issue and a task:
Neither object's status changes, and nothing is moved to On Hold.
Closing or completing one does not notify anyone or change the status of the other.
No state is synced between the two in either direction.
The link only records that the issue and task are related so your team can navigate between them. The task and issue must belong to the same account in order to be linked.
How this differs from linking a Linear, Jira, or Asana ticket
This native issue-to-task link is different from linking an external product ticket (Linear, Jira, Asana, etc.) to a Pylon issue. With those integrations, linking a ticket can automatically change the Pylon issue's status, and the external ticket's state can sync back to Pylon. That automatic status behavior is specific to external product-issue integrations and does not apply to the native issue-to-task association.