2 ms·
Linear is much nicer. Very quick issue entry and very nice looking sprint summary/status and roadmap tabs. It's everything I want. Most importantly, it's fas
by jrockway 4y ago
Linear is much nicer. Very quick issue entry and very nice looking sprint summary/status and roadmap tabs. It's everything I want. Most importantly, it's fast. I work with issues a lot, so a slow tool like jira just isn't acceptable.
Jira exists to check every checkbox so you feel serious remorse if you pick anything else, but in terms of day-to-day productivity, it doesn't do too well. "Nice to look at" and "Fast" aren't checkbox items for managers. They're eventual problems for someone to solve when they notice engineers never touch the bug tracker.
At my current org, my advice to use Linear was overruled in favor of jira, and I'm pretty sure I'm the only engineer that regularly touches jira.
(I intentionally write "jira" in all lowercase because I like to call it JIRA, but jira's built-in text editor unconfigurably autocorrects "JIRA" to "Jira". That's the feature they spent engineering time on? Fuck them.)
- epalm 4y agoI looked at Linear and it's very software-specific. The features page says it's "the new standard for modern software development". I do use Jira for software, but also for generic state tracking of non-software processes. E.g. some projects have no use for sprints, or code integration, or user stories.
- enra 4y agoIt's aimed for software teams, but there are also non-software teams using it. Sprints (cycles) are turned off by default, similarly many other features can be enabled or left off if you don't need them. Code integration is also not really visible unless you integrate and use it.