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!
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!