Feature Summary

I often link Emdash tasks to external issues, but the linked issue stays stale as work
progresses.

For example, when I create an Emdash task from a Featurebase post and later open or merge a
PR, I still need to manually go back to Featurebase and move the post from Planned to In
Progress or Completed. The same problem exists for Linear, Jira, GitHub, GitLab, and Forgejo
workflows.

This creates duplicate status tracking: Emdash knows the task/PR state, but the source issue
tracker does not get updated.

Problem or Use Case

Add optional linked-issue status sync.

In settings, users should be able to enable issue status sync and configure mappings from
Emdash task/PR lifecycle states to provider-specific statuses.

Example mapping for Featurebase:

• task started or PR opened → In Progress
• PR ready for review → In Progress or Planned, depending on user preference
• PR merged → Completed
• task cancelled/closed → Rejected

The UX could live in the integrations/settings area:

• global toggle: Enable linked issue status sync
• per-provider capability display
• per-provider status mapping controls
• clear non-blocking error feedback when sync fails

The feature should integrate with existing linked issue behavior. Providers that support
status updates should opt in through provider capability metadata. Unsupported providers
should remain read-only and should not show unavailable controls.

Proposed Solution

I currently work around this by manually updating the linked issue in Featurebase/Linear/
Jira/etc. after creating tasks, opening PRs, and merging PRs.

Another workaround would be automation outside Emdash, but that requires separate scripts or
third-party automation for each provider. Since Emdash already knows the linked issue, task
state, and PR state, it seems like the right place to coordinate this.

Alternatives Considered

I currently work around this by manually updating the linked issue in Featurebase/Linear/
Jira/etc. after creating tasks, opening PRs, and merging PRs.

Another workaround would be automation outside Emdash, but that requires separate scripts or
third-party automation for each provider. Since Emdash already knows the linked issue, task
state, and PR state, it seems like the right place to coordinate this.

Additional Context

This would be especially useful for the new Featurebase integration, where posts commonly
move through statuses like Planned, In Progress, Completed, and Rejected.

A good implementation could start with Featurebase only, then expand to other providers
behind capability flags such as canUpdateIssueStatus.