3 ms·
I helped a prior employer move to github and asana through JIRA's own APIs. It's actually not that hard and the entire engineering group was very cheerful of th
by zeusk 4y ago
I helped a prior employer move to github and asana through JIRA's own APIs. It's actually not that hard and the entire engineering group was very cheerful of the change.
- threeseed 4y agoBe curious what the size of the engineering team and company was. Asana is great for SMBs but for larger developer teams it lacks a lot of features and integrations.
- daniel_iversen 4y ago(Work at Asana so I might be biased) While Jira may have some unique features for developers, one of Asana’s selling points is how it allows non-homogenous teams (incl whole companies) to work together (and by themselves within individual teams) on a variety of different kinds of work (projects, processes, loose day to day tasks etc). And as for scale we have many customers with thousands of users (one tech customer of ours has 100,000+ users on Asana - most of them I’m sure would be product teams).
- zelos 4y agoReally? Was it easy enough to define mappings between all the various fields/ticket types etc? I guess you could do it per-team across an organisation. It always seems hard enough to get information out of JIRA using JIRA when I watch our PO in planning meetings.
- zeusk 4y agoYup, there was some mess around inexact mapping so we had our own conflict resolution and definition of what and how to interpret respective fields. Honestly, JIRA easily has one of the most sluggish and horrid developer experience so the bar wasn't too high to begin with. Visual Studio Online / Azure DevOps is far better than JIRA ecosystem imo.