3 ms·
It's not as bad as JIRA, although JIRA is marginally more useful than LinkedIn.
by porise 6mo ago
It's not as bad as JIRA, although JIRA is marginally more useful than LinkedIn.
- tom1337 6mo agokinda offtopic but as somehow currently outgrowing trellos capabilities, do you have any good suggestions instead of Jira?
- calderwoodra 6mo agoLinear
- maccard 6mo agoThe answer is unfortunately jira.
- menno-sh 6mo agoGitlab has pretty good Kanban functionality. People tend to hate Jira but there aren't a lot of great alternatives
- maccard 6mo agoJira’s problem is that it’s effectively free-form, and there are no enforcements in place. You can have three teams - one using kanban with relative estimates, another using springs with story points, and a third using waterfall with time estimates - all in the same project, with the same workflows, and conflicting requirements. You have 3 different release fields, 2 are required, the third one is the one that your team are generating reports from. That and its dog slow, of course.
- rvz 6mo agoBoth of them are equally garbage.
- eddyg 6mo agoJira (hasn’t been JIRA for a long time) is great when you have proper Jira governance in place, with admins who say “no, you can’t have a new custom field, use this one with a new context”, configure good workflow transitions with validators and conditions, design appropriate create, view and edit screens (instead of using the same one for three separate operations), etc. The problem is always crappy administration, not Jira. Jira can be fantastic when properly managed.
- hsbauauvhabzb 6mo agoIronically if you use jira you probably should be using LinkedIn to escape it.