We are considering moving from Asana to JIRA, the two main reasons being that our workflow schema is of setting up 'Teams' in asana as 'Clients' and then individual projects are created under that client. This suits us but is putting a lot of pressure on the front-end, single view of Asana and it's becoming so slow it's unworkable and will only get worse.
The second reason to want to shift is that JIRA definitely has better agile workflow with swimlanes and Kanban views etc. which would suit us.
When I tested JIRA about 16 months ago that too was very sluggish so I cancelled the test but I'm tempted back by point 2.
Does anyone have any advice on this before we make a shift which could potentially be quite a lot of setup, migration and training time?
If you need an intuitive user interface / easy to use and to administrate with a powerful SLAs, Queues, Customer Portals, Workflows configuration, Automation, Permissions, Knowledge Base, Reporting module, I would invite you to check also JIRA Service Desk
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs