[tekacs]

The decisions feature here feels a lot like Threads (https://threads.com/) and the document feature like Notion (though I see the use of ProseMirror).

I can’t necessarily say that I understand the value of two way syncing the content in Fable doc into the ticket body (rather than simply linking to a Notion doc in the page of a Linear/Jira ticket, which I’ve seen commonly done). That way the entire team can see a spec, collaboratively edit it and engineers just click the link to go across.

I could also very much see Linear adding a Notion integration or support, which would further simplify that process. Notion also added the reverse direction for Jira recently too, so it’s super easy to embed live ticket information on Notion now!

Would love to understand that use case a little better!

[addorai]

The workflow that many teams use (myself included) is to iterate on detailed requirements in a doc, often in a table. They do this so that they can iterate on them in a more collaborative place vs Jira/Linear. It's also more accessible to the broader team (sales, design, marketing, etc).

Then after aligning they copy + paste those requirements into the issue tracker. They often also include a link back to the doc. But then you have two places that show the same requirements, one for eng and one for others and they almost always get out of sync. Plus it's a bit annoying for eng to have to parse thru the spec to map requirements for a specific ticket.

This is the workflow we're solving for!

As for Linear + Notion or Jira integration, it's entirely possible they add it but our approach is to focus on a few product team focused integrations and go deep on them