Tuleap is a top alternative to Jira as it is an all-in-one solution for Agile Management and DevOps. To help make the transition from Jira to Tuleap as easy as possible, we’ve developed an importer for Jira data. Use it to move your Jira issues to Tuleap Trackers in just a few small steps.

Easily import data from Jira to Tuleap

Jira and Tuleap concepts

First, how are Tuleap and Jira different? Let’s run through some of the most notable differences, so your team can keep right on focusing on important work during and after the transition without skipping more than a couple of beats.

Jira projects ≠ Tuleap projects

In Jira, a project is a collection of issues. A sum of stories, tasks, bugs. They can be viewed in the form of a board or charts.
In Tuleap, a project is a workspace that hosts team members and tools. Among the tool, there is the Tuleap Tracker, that store a collection of issues (or artifacts). Project, artifacts, you can learn more on the key concepts of Tuleap Tracker, the unique open source issue tracker is the dedicated article.

Why this difference of concept ?

Originally, Jira was designed as an issue tracker. It has grown patch by patch into a project management solution by the acquisition of companies, tools and a third parties plugins system.
In the early design, Tuleap has been conceived for managing projects on a companywide scale. This requires a focus on central management of workflows , security and access controls with a good balance to provide enough freedom to unleash the potential of teams. Compare hereafter Jira and Tuleap, the open source alternative to Jira.

Jira issues  = Tuleap artifacts

Artifacts in Tuleap are the equivalent of issues in Jira. Both are a work item, a task, an incident, a story…to be short any entity you would like to manage and track. In some things, they are the same: they look like a form, include information. They are created by someone, assigned to a team member…and move through statuses to completion.
The difference is in the tools themselves. Tuleap Tracker and Jira work differently and are not flexible the same way.

Workflow management

The module of issue tracking in Tuleap offer a very large range of settings, automation and adaptations. With Tuleap, workflow management is “haute couture”.
In Jira, you have to configure your project to either Scrum or Kanban methodology. Within Tuleap, you can select a ready-to-use tracker configuration to get started faster, but you can choose no configuration and create it on the fly, because Tuleap tool naturally supports the way your team works. If you have a very specific approach with a home-made workflow, Tuleap Trackers are flexible enough to adapt to your team’s needs.

In Tuleap, trackers’ configuration can be done at two levels:

  • at the platform level, by the global IT administrator, for building ready-to-use tracker templates,
  • at the project workspace level, by the project leader, to fine-tuned configuration and make them perfectly suit team’s jargon, users groups and activities’s workflow.

This is how you will take back control of your workflow.

You know the WYSIWYG? With Tuleap, “What you Want is What You Set.” Do you want a very specific workflow? Just design it: choose your transitions and change  the words.

Pierre-Yves Colle, IT Program Manager, STMicroelectronics

Importing issues from Jira to Tuleap

To ease your transition from Jira to Tuleap, we’ve built an automated importer. In just a few short minutes it can turn your Jira work into Tuleap artifacts and workflows. You won’t miss a beat… or at least more than a few beats.

Importing from Jira is as easy as 1-2-3

Take a look at the video to see how easy and fast it is to import data from Jira to Tuleap:

4 steps for the import

  1. 1. Users make their email addresses publically readable in Jira, 
  2. 2. In Tuleap, Jira project administrator imports issues creating a new tracker,
  3. 3. Tuleap automatically imports Jira issues replicating a very large number of fields (text, string, date, select box, radio, status…), attachments, comments and history,
  4. 4. Tuleap maps Jira users and Tuleap users (creator, updater, users in field values…)

Take a look at the Tuleap documentation if needed.

And then?

Start managing projects in Tuleap as if you’ve simply been using it this whole time. Adapt your issue workflow, create reports and agile charts…and go ahead with DevOps tools as well.

More than just issue tracking

Any successful product or feature launch involves collaboration across all teams as the work moves from ideation through execution. So software teams need more than a bug and issue tracker. Tuleap provides native integration with agile management, development and testing tools for end-to-end traceability. With a full-featured solution as Tuleap, you can get instant visibility into your development pipeline. And, you can go ahead and automate processes with Tuleap’s robust set of APIs.

You’re ready 💪

We’ve covered the essential concepts for a successful transition from Jira. Tuleap is full of powerful features, workflows, and tips that aren’t covered here, so we’ll leave you with a few more resources. Nest steps? Join a webinar: Agile management, Test Management, we talk about the actual teams’ challenges.

tristique sit Donec Aliquam quis, Praesent felis mattis ut accumsan