Skip to content
This repository was archived by the owner on Apr 11, 2025. It is now read-only.

Latest commit

 

History

History
105 lines (78 loc) · 7.64 KB

File metadata and controls

105 lines (78 loc) · 7.64 KB

Integrated Task management tools

This documents tries to list requirements for task management systems, and the tools some of us have tried. It also has another section concerning communication/chat tools and integration with the task management.

All tools reviewed below should satisfy the requirements called Mandatory. There are some Optional requirements. The tools satisfying these optional requirements are listed in the table.

Task management tools requirements

The idea is to not only solve the unpleasant RT experience, but also to integrate user issues, project management, communications and possibly other tools we are using or should be using. Hopefully that would make both the user and our own experience more pleasant and efficient.

The requirements are vague enough to let us have the possibility to switch not just to another RT system, but to switch to a different procedure than an RT-like process.

Mandatory

The tool:

  • must have user issue management features: reporting, tracking, assigning, searching (for CADC users)
  • provides project management (agile style was assumed mandatory) integrated with issue tracking
  • can manage task grouping: project, epics, user story, task, issue...
  • can do reports and/or task analytics
  • can manage task dependencies
  • tracks task time (or "point")
  • has an interface we can access everywhere (meaning a web interface to a server hosted on a public IP VM)
  • integrates with git, i.e. in the form of a web repository viewer
  • integrates with a chat tool: the table will list in the column Chat the integration with chat tools, and if it integrates with all, a subjective indication to which one it integrates best with

Optional

The tool can support:

  • Support: issue creation should be possible via email (such as: submit issues to support@blah.org) or a web form. They also might have a knowledge base or FAQ integrated.
  • GitHub: most tools use commit based references. Some use bidirectional with issues and commits
  • Mobile: both Android & iOS apps are supported

Notes:

  • Cost: reported costs are in USD / 30 internal users / year. Open Source Software (OSS) means the cost is our labour, or in all those cases, a paid service tier can maintain it for us.
  • Examples : see links for some projects using those tools
Solution Cost Chat Support GitHub Mobile Demo Comments
GitHub 300 all, Gitter gitreports, bidirectional: zendesk with tissueapp all yes demo Task Management: ZenHub, waffle, codetree, HuBoard, overv
Yodiz 1,800 slack email commits yes demo free for academic
YouTrack 1,500 XMPP, slack form, email, search commits yes demo free for OSS
Rally 10,000 Flowdock need user registration yes yes need user registration
JIRA 2,040 all, HipChat email, form with desk commits yes demo,cern need JIRA Agile + JIRA Service Desk + Confluence for knowledge base. free for OSS
GitLab OSS slack, Flowdock, gitter no yes yes SSC agile project management and helpdesk need extra software
Taiga OSS slack need user registration yes no demo
PivotalTracker 3,000 all, Flowdock no commits yes projects free for public or academic
Tuleap OSS XMPP yes commits no demo demo url unaccessible at HIA network. one stop solution for all CADC
OpenProject OSS via bot yes no redmine? community chat integration seems with a chat bot only
Redmine OSS HipChat, Flowdock, XMPP yes commits yes no most complete solution. painful to get friendly (but possible)

Other useful links:

Communication tools requirements

####Mandatory: The tool must:

  • supports multi users (doh)
  • supports multi chat rooms (also called channels, or flows)
  • supports Linux and OSX access, outside from CADC as well
  • allow non-public chat rooms
  • bi-directional integration with one of the task management system above
  • integration with a deployment platform

####Optional: The tool can integrate with:

  • Email to the chat clients
  • a calendar (Cal)
  • git activity
  • a monitoring platform (Mon)
  • continuous integration and deployment (CI)

The tool:

  • can be accessed from standard chat clients via XMPP or IRC Protocols
  • has native Desktop clients, standard means an all-protocols chat client such as adium (OSX), pidgin (Linux), etc...
  • has native Mobile clients, both Android and iOS
Solution Cost Email Cal git Mon CI Desktop Mobile Protocols Comments
Flowdock 1,080 yes yes yes yes yes OSX all IRC splitted views, threads
Slack 2,400 yes yes yes yes yes OSX all IRC, XMPP
HipChat 720 no no yes yes yes all all XMPP allow guest users
Gitter 720 no no yes yes yes all all IRC splitted views
Sans free yes yes yes yes yes all all all revolutionary
OpenFire OSS yes yes yes yes yes standard standard XMPP some integrations need work

Other useful links: