Most tools in the market are either/or and have a disjointed experience. They're either for documentation/memos/wikis or issue tracking. Yes, Confluence is part of the Atlassian landscape but it's not that tightly coupled (from a user experience perspective) with JIRA. They don't "live alongside" each other so to speak.<p>Notion is a little better but fails pretty badly at being an dev issue tracker.<p>Why does this matter? Because with most teams now remote/async/distributed, I'm seeing a lot more context not easily accessible and spread thin. I can see a lot of benefits from written context + tickets being more tightly coupled.<p>Does it seem to you that there's an opportunity for software that takes a fresh look at this?
What problem are you trying to solve?<p>It's unclear what a tight coupling of documentation and issue tracking look like, or how it's beneficial.