Design a site like this with
Get started

Should wiki/documentation + issue tracking really live alongside each other?

Most tools in the market are either/or and have a disjointed experience. Eg, gdocs, linear, Monday, JIRA, Confluence etc.

They're either centered around documentation/memos/wikis or around issue/ticket tracking. I suppose you could say Confluence and JIRA being part of the Atlassian landscape go together but they're really not that tightly coupled (from a user experience perspective). They don't "live alongside" each other so to speak.

Notion is somewhat better where connecting docs to tickets is somewhat better but Notion itself fails pretty badly at being a true 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 has a fresh perspective on this?

submitted by /u/blizkreeg
[link] [comments]

from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this:
search previous next tag category expand menu location phone mail time cart zoom edit close