What is Asana?
What is Jira?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Asana?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I have been using asana for a couple years and I have nothing but good things to say... except that it doesn't have a unified inbox and task list across you Organization/Workspaces :(
Amazingly easy task/project management Meetings are great, Type your meeting agenda, notes & next actions directly into asana while the meetig is taking place. Integrates with Dropbox and Google Drive.
This is the easiest project management tool I have ever used and it is very easy to get other people to use it too. I haven't has as much success implementing a habit within an organization as with asana. The biggest problem with Project management systems is that organization members don't use them enough, not with asana. Mobile apps, speedy web app, and integrations galore make it easy for people to stay up to date.
Most of my time in JIRA is spent
- Waiting for pages to load
- Clicking on links, because the information that I need is not available on the first pages I reach
- Looking for the next link to click, because each page has a different layout and the bug title or the latest comment might be placed anywhere on the page
Additionally, any time I search the documentation I get bug reports from years ago that appear unresolved or instructions for modifying the on-premesis installation (we have their cloud service).
Compared to Bugzilla and Redmine, Jira requires a lot of manual configuration which can make project issues not compatible status-wise.
We originally decided to use Trello because GitHub Issues were getting way too crowded and overwhelming. Also, GitHub Issues are great for detailed bits of work, but they're not so great at high-level tasks or buckets of work. The milestones stuff in there just doesn’t cut it.
We love Trello. It's great because it’s super flexible. Almost to a fault. The one thing I wish it had: velocity. Not sure why they don’t add that, but I would so use it. Right now we just add an estimate of hours at the top of the description field. I also wish they had a more robust Calendar and concept of time. Trying to get Trello to act like a product planning tool is almost impossible. And using other tools is a nightmare. So we’re kind of stuck using Trello as-is. But Trello as-is is > all the other PM tools we’ve tried (and we’ve tried a lot).
It is used for bug tracking, issue tracking, and project management The basic use of this tool is to track issue and bugs related to your software and Mobile apps. It is also used for project management. The JIRA dashboard consists of many useful functions and features which make handling of issues easy.
The various projects that we'll have on the go at any point in time, within the R&D team, are internal projects that will prove long term benefits. We use Trello to track individual tasks that comprise those projects, and work with them in an Agile approach.
리스트 목록: Inbox, ToDo, Doing, Done, 얘기해봐야할 것들, 디자인 Preview,런칭 후 개선할 것들, Document(컨플루언스 대신 씀. 로드맵 공유)
원랜 Github issue로 이슈트래킹을 했었는데 첫 개발땐 워낙 바뀌는것도 많고 빨리해야될것도 많고 해서 트렐로로 유연하게 관리하니까 좋음. 앞으로 사용자가 생기고 소스코드 풀면 github issue로 관리할 생각
Trello is the core of our workflow. All tasks to be done go on Trello, and whenever you have to work on something, you go on Trello to check out what you could work on. And it works perfectly for us.
I use Trello for organizing projects. Typically I break a project up into sections, add and prioritize tasks for each section. For largest projects, I'll break it into multiple trello boards.
So much relief as you can track each and every issues, bugs, dev project and maintenance and a time machine when it comes to do that less interesting timesheet or daily status. Its a rescuer.
We keep ourselves out of email as often as possible, thanks to Asana. It keeps in the know, helps us manage sprints and hackathons, and helps us be transparent and productive.
We use a combination of Scrum and Kanban for our tasks. We focus more on the integration with Bitbucket to keep track of tasks and have bi-directional accountability.
We use JIRA because it's a single tool that can be customized to each of our business processes: product development, customer on-boarding, and internal operations
The agile process planing feedback and control is done in JIRA, with integrations in all places, like bitbucket code, confluence pages and build process
I used Asana to manage the tasks, define scope of the project more over to create a learning path that will effect my project.
The central hub where all of our projects live and breath. Without Asana, we would truly be lost.
I use asana for personal projects (to collaborate on event organization) on a weekly basis.