Re:How Atlassian Built a $10B Growth Engine
by dmitriid on Tuesday January 02, 2018 @01:19PM
(#16053916)
I also "love" how they re-designed the issue UI. What do you need in an issue? Obviously, issue description. Now even on largest monitors issue description starts below the fold. Everything else is taken up by nice crisp white-space-separated "important" information: the sprint name, the epic link, number of hours projected, who it is assigned to, etc. etc.
[ Parent
| on HN ]
Re:How Atlassian Built a $10B Growth Engine
by quasse on Tuesday January 02, 2018 @04:14PM
(#16055714)
The create issue button (you know, the one we're all guaranteed to need, always) is also not just an unlabeled "+" in the sidebar by default.
Re:How Atlassian Built a $10B Growth Engine
by liveoneggs on Tuesday January 02, 2018 @01:47PM
(#16054207)
how many points is this outage going to be to fix? we'll need to bring it up to the project committee to see if we can allocate it out of the next sprint
Re:How Atlassian Built a $10B Growth Engine
by justinator on Wednesday January 03, 2018 @12:54AM
(#16058824)
"Points" the gateway drug of JIRA. It's honestly the most difficult/simple concept to understand, since it's all about "don't think intuitively, because in JIRA that's the wrong way to think."
Re:How Atlassian Built a $10B Growth Engine
by softawre on Tuesday January 02, 2018 @03:11PM
(#16055108)
You can reorder the issue fields can't you?
Re:How Atlassian Built a $10B Growth Engine
by wwalser on Tuesday January 02, 2018 @06:08PM
(#16056748)
Yes.
There is an enormous amount of hate directed at JIRA that is a side effect of customizations created by admins. People abuse the customizability and their own internal users suffer the consequences.
Atlassian's own public issue tracker is using a near-default issue display screen. Nothing is "below the fold" for me on this issue and on a small monitor: https://jira.atlassian.com/projects/CORE/issues/CORE-1055
Re:How Atlassian Built a $10B Growth Engine
by albedoa on Tuesday January 02, 2018 @10:07PM
(#16057971)
Is this a side effect of customizations created by admins?:
> Last commented: 1 year, 13 weeks ago
> There are no comments yet on this issue.
Maybe a large part of the hate is genuinely about the default configuration and UX.
Re:How Atlassian Built a $10B Growth Engine
by wwalser on Wednesday January 03, 2018 @02:17PM
(#16064095)
That's actually one of the few non-default things on that instance. Because it's a public issue tracker (which few companies outside Atlassian are willing to do to themselves), some comments by employees are hidden to the outside world.
It appears the issue in question was commented on 1 year, 13 weeks ago. But the comment isn't visible to the public, thus the "no comments yet" message.