HN Explorer

Ask HN: Is there a gap in the wiki/docs+issue tracking space?

2 points by v1l ↗ HN
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.

Notion is a little better but fails pretty badly at being an dev issue tracker.

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.

Does it seem to you that there's an opportunity for software that takes a fresh look at this?

2 comments

[ 2.9 ms ] story [ 14.0 ms ] thread
clintonb
What problem are you trying to solve?

It's unclear what a tight coupling of documentation and issue tracking look like, or how it's beneficial.

v1l
I see you work at Stripe, which is probably the gold standard for the culture around capturing things in writing and having them be accessible to folks across the company.

But in lesser teams (which is most), I see that even around a single initiative, documents and notes are very dispersed and disconnected (to the point of being undiscoverable) and have no link to the actual "work to be done", i.e., tickets.

The problem is how do you have a more cohesive boundary around initiatives? Can I go to one view and get a full picture and understanding of an initiative, a problem, a decision and its current status?