1.2 Deployment Scenario

Dozens of our customers have made the move to completely migrate from ClearQuest to JIRA. Many of them have imported their entire defect database into JIRA and configured workflows, schemes and fields to perfectly match their business processes. Yet, especially in the beginning, when the organization is still evaluating a new tool or even later on, co-existence is absolutely a viable option. For this cookbook, we list four different scenarios:

Scenario

Co-exist with ClearQuest/ClearCase

Co-exist with ClearQuest as archive and keep ClearCase

Co-exist with ClearCase only

Total migration

Source Code Management

Remains in ClearCase

Remains in ClearCase

Legacy remains in ClearCase, New project in Subversion / Git/ other

Migrate to another solution like Subversion or Bitbucket (Git)

Issue and Task Management

Keep current projects in ClearQuest, new projects in JIRA

Keep inactive and old projects in ClearQuest but migrate active projects to JIRA

Migrate all projects from ClearQuest to JIRA

Migrate all projects from ClearQuest to JIRA

Support for Integration

ClearQuest/JIRA by experts, ClearCase integration up to version 2.7 of FishEye

ClearQuest/JIRA by experts, ClearCase integration up to version 2.7 of FishEye

ClearCase integration up to version 2.7 of FishEye

SVN/Git integration with FishEye / JIRA is supported by Atlassian

Feasibility

Feasible, common scenario

Feasible, common scenario

Not recommended

Feasible, common scenario

Suitable for Trial Goals


Adopt Agile Methods
Bring All Into The ALM Process

Decrease Costs

Improve Productivity And Collaboration
Adopt Agile Methods
Bring All Into The ALM Process

Decrease Cost

Improve Productivity And Collaboration
Adopt Agile Methods
Bring All Into The ALM Process
Easier Extensibility
Decrease Cost

Improve Productivity And Collaboration
Adopt Agile Methods
Bring All Into The ALM Process
Easier Extensibility
Decrease Cost

Step in the adoption lifecycle Evaluation / Pilot First phase of production Preparing ClearCase sunset Total adoption

Co-exist with ClearQuest/ClearCase in production

In this scenario, your organization's main branch of development remains on the Rational product suite. However, new projects, for example the development of entirely new products are tracked in JIRA. One common scenario is the introduction of JIRA together in accordance with the adoption of agile methodology. These projects would work with Atlassian's JIRA Agile built on JIRA and most likely run on a newly installed source control system such as Subversion or Git.

On the business side, it is already worth migrating one project over to a new JIRA instance. That way, you would be able to remove 2 floating ClearQuest licenses which would free more budget than you would need for a hundred user licenses for JIRA (Or 50 users if you want to include JIRA Agile). As a result, this scenario already supports the trial goal to decrease costs.

Co-exist with ClearQuest as archive and keep ClearCase

There might be the situation that your organization is running projects on ClearQuest that have a long history and very high degree of customization. If additionally, there is very low activity on these projects, then the effort to migrate these projects including their history to JIRA might not be justifiable. In these cases, you can keep these projects in ClearQuest and at the same time reduce the number of floating licenses drastically as all active projects are migrated to JIRA.

Co-exist with ClearCase

If your organization has made the decision to move off ClearQuest but keep ClearCase for source code management, then it is possible integrate both applications using FishEye. However, after version 2.7 of FishEye, the integration is not supported by Atlassian anymore. If you still wish to pursue this option, then we would be happy to refer you to one of our Experts.

Total migration

Migrating off ClearQuest and ClearCase together provides the organization with the highest flexibility to select a new solution. Organizations of all sizes are making a switch from ClearCase to alternative Source Control Management (SCM) systems such as Subversion, Git or Perforce. An often stated decision factor are for example the lower administration effort and lower costs, the flexibility, ease of use and openness of the system (SVN itself is open source). With this move, many companies take the opportunity of the ClearCase migration to also re-evaluate their change management / issue tracker system.

Today, projects like the Apache projects show that Subversion is able to handle the largest of software projects. Many of our Experts have built considerable experience and tools to support such a migration.

Next to other commercial products such as Perforce, Git has evolved into an increasingly popular alternative within the last years. Git is a Distributed Version Control System (DVCS) and although first leveraged by smaller teams, enterprise organizations are now adopting it further. Atlassian fully supports Git and has released its own enterprise-grade Git management tool: Bitbucket Server (previously known as Stash, and first released May 1st, 2012).

More information:

Last modified on Sep 22, 2015

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.