Better control of your project workflow, all under the same roof…A feature and freedom comparison to help you make your choice.
Better control your project workflow with Tuleap
When submitting a request to your global administrator starts to feel like sending a message in a bottle, it is time for Tuleap! With Tuleap you can get things done in seconds! Need to rename a field with your jargon? Easy!
Standardizing software processes across the organization is something everyone agrees on. However, to be really efficient, project teams need to be able to tailor their workspace to the way they work…not the other way around!
With Tuleap, project teams gain independence and efficiency. Tuleap lets project teams make simple changes that transform the way they work. They can create their own project user groups, add new values to trackers and configure their workflow transitions and development triggers.
Jira can’t do it alone
With Jira, if you want to get a complete agile development platform, you will probably need Bitbucket, Confluence, and Bamboo as well…and the costs quickly add up. With Tuleap, you get everything you need in one package! You can start reaping the benefits of greater efficiency right away.
Tuleap provides all of the tools you need to create smart software: issue tracking, agile, Git, Subversion, Jenkins integration, and a document area. All in a single product. Jira simply cannot do everything Tuleap can on its own.
Features comparison
Available with strong capabilities, 
Limited, 
Not available
Issue tracking
| ISSUE TRACKING | ||
|---|---|---|
| Track any type of issue : tasks, bugs, requirements, stories | |
|
| Unlimited trackers per project | |
|
| Pre-configured trackers templates | |
|
| View issues change history | |
|
| Mass update | |
|
| LINKING-TRACEABILITY | ||
| Link issues backward & forward to other issues (ex: link an incident to a task) | |
|
| Link issues backward & forward to software development items: code, jobs, documents, CI…) (ex: link a requirement to a wiki page; a bug to a revision and to a job, a release to a file) | |
Additional products needed |
| Link issues back to third party tools (ex: link a Tuleap task to a CRM activity) | |
|
| Define artifact link nature (ex: resolved in, satisfied by) | |
|
| TRACKER CUSTOMIZATION | ||
| Create organization tracker templates | |
|
| Create your own tracker templates | |
|
| Freedom for platform admin to customize trackers | |
|
| Freedom for project leads to customize trackers | |
|
| PER TRACKER FIELD CUSTOMIZATION | ||
| Ability to modify tracker fields | Both at platform level and per project level |
At platform level only |
| Ability to choose the rank of a field in the issue form | |
|
| Project Lead can modify fields according to a predefined list | |
|
| Project Lead can add any type of new fields | |
|
| Project Lead can add new values in fields | |
|
| PER TRACKER WORKFLOW | ||
| Ability to modify tracker workflow | Both at platform level and per project level |
At platform level only |
| Define field dependencies (ex: if the resolution field gets the value ” fixed”, then the status field will get the value “closed” | |
Nor in simplified workflow, nor in advanced workflow |
| Project Lead can define authorized transitions | |
Only in advanced workflow, only by the platform admin |
| Project Lead can define their own user groups to be used in the workflow | |
|
| Project Lead can define authorized user groups to make some specific transitions (ex: only group A can move from status “to do” to “on going”) | |
Nor in simplified workflow, nor in advanced workflow |
| Project Lead can define post functions after transitions (ex: when a task moves from “on going” to “done”, then the remaining work is set to “0”) | |
Only in advanced workflow, only by the platform admin |
| Project Team can set cross-tracker triggers (ex: when all the subtasks are “done”, thus the parent task is “closed”) | |
|
| Define triggers on development tools at issue updates (ex: launch a jenkins job when the issue status is “under review”) | |
Additional products needed
|
Agile approaches
| SCRUM | ||
|---|---|---|
| Epics, User Stories, Tasks tracking | |
|
| Release, version, sprint planning | |
|
| Backlog management: populate, prioritize | |
|
| Drag’n drop | |
|
| Selection of one or multiple issues | |
|
| Effort and capacity monitoring | |
|
| Scrum cardwall | |
|
| Fine-grained permissions | |
Project Lead cannot create his specific Scrum user groups on their own |
| Burndown chart | |
|
| Link Scrum artifacts back to code, pull request, documents, deliveries | |
Additional products needed |
| Scrum at scale | |
Additional product needed |
| KANBAN | ||
| Boards with visual cards | |
|
| Drag’n drop | |
|
| Real-time update | |
|
| One Kanban board for multiple projects | |
|
| Multiple Kanban boards by project | |
|
| One Kanban with several trackers | |
|
| WIP limit configuration, per column | |
|
| Swim lanes | |
|
| Configure workflows through columns (ex: limitation to move directly a card from the column « to do » to « closed ») | |
|
| Link Kanban issues to code, pull request, documents | |
Additional products needed |
| Custom columns name, numbers | |
|
| Custom information displayed on cards | |
|
| Filter cards by searches | |
|
| Cumulative flowchart | |
|
| MIXED APPROACHES | ||
| Scrumban, Kanplan, home-made process | |
|
Project Management
| REPORTING and SEARCH | ||
|---|---|---|
| Personalized tables | |
|
| Pie, bars, cumulative flow | |
|
| Cardwall/Boards | |
|
| Gantt chart | |
Additional products needed |
| Charts updated to on-the-fly searches | |
|
| Personal reports | |
|
| Team-shared reports | |
|
| Advanced Tracker Query Language | |
|
| TIME TRACKING | ||
| Dedicated fields (estimated effort, real points, hours…) | |
|
| Timer button (start/stop time) |
| |
| PERMISSIONS DELEGATION | ||
| Per tracker | |
|
| Per field | |
|
| Platform Admin can define generic user groups | |
|
| Project Lead can define their own specific user groups | |
Only by the platform admin |
| NOTIFICATIONS | ||
| Platform Admin can set notifications per tracker | |
|
| Project Lead can define their own notifications per tracker | |
Only by the platform admin |
| Users can choose to receive notifications per issue | |
|
| Per tracker canned (prefabricated) responses | |
|
| Per tracker date reminders | |
|
| IMPORT-EXPORT | ||
| Import/Export issue data in CSV | |
|
| Import/Export all issue data, including attachments and history | |
|
| Import/Export issues with APIs | |
|
| Import/Export Scrum planning and dashboard configuration | |
|
By the way, Tuleap is open source. Jira is proprietary
This is all about freedom. While we are on the topic of freedom, it is important to consider whether or not a tool that you will populate with your organization’s knowledge will let you soar or clip your wings. What will happen to your organization’s data when your paid license ends, for example?
With proprietary tools, if you don’t pay, you can’t build software. With Tuleap, as it’s an open source tool, your freedom is guaranteed
Availability and Services
| AVAILABILITY | ||
|---|---|---|
| Licence | ||
| Freedom to download | |
|
| Installation on your premises | |
|
| In the cloud | |
|
| Managed remotely on your premises | |
|
| DEPLOYMENT | ||
| Unlimited and monthly updates | |
|
| Unlimited upgrades – new users/projects | |
|
| FOR TEAMS AND COMPANIES | ||
| Software Development, R&D | |
|
| Marketing, HR, Operations, Finance, etc. | |
|
| IT, ServiceDesk and Customer activities | |
|
| Start-ups, Small businesses | |
|
| Medium-sized | |
|
| Large scale organizations | |
|
| FLOSS projects | |
|
| Academics, Students, Teachers, Interns | Tuleap-Campus |
|
| All industries | |
|
| PROFESSIONAL SERVICES | ||
| Installation, Consulting, Trainings | Provided by Enalean, the software company |
Not provided by the software company |
| Support with SLA | provided by Enalean, the software company |
|
| Open Roadmap: (crowd)-fund developments you need, integrated into the upstream software, with long term maintenance | provided by Enalean, the software company |
|
