Hacker News Reader

Comment by lima | Hacker News Reader

JIRA and Confluence...

A good design is as simple as possible but no simpler. The problem with ticketing and document authoring platforms are that they are arbitrarily complex. I have some sympathy for Atlassian on managing the complexity of these things. We could say that they should limit their features better, but predicting the cost of adding another use case to a pile of them is not a solved problem.

> The problem with ticketing and document authoring platforms are that they are arbitrarily complex. I have some sympathy for Atlassian on managing the complexity of these things.

Many things are arbitrarily complex. But Atlassian constantly gives items of differing importance the same level of attention, in a shotgun blast of UI.

And just when you think you've got it sorted out, they do a major redesign and screw up your workflow (not the ticket flow, your personal one).

+1000 to JIRA as a response to this. I'd probably support confluence here too but every company y I've worked with killed it one the WYSWYG editor became mandatory and all of engineering refused to use it.

There's a plain text option in the Jira I use, that will show formatting in the usual forms, like *, _, etc. I also refuse to use the WYSIWYG editor since it's a pain.

Confluence has no plain text editor, and the WYSIWYG one is horribly broken.

It's a pain to use.

Slack et al work great for arguing and discussing, but confluence is the best Wiki for recording long term conclusions and providing long term structure for projects. Google Docs is a jumbled atrocity by comparison ... confluence linking and navigation just work.

If it's just for devs, I like GitHub Enterprise wikis and readmes.

spend 10 minutes with Rally and you'll be begging for JIRA

Enterprise-scale.

Reply on news.ycombinator.com