Request for converting the GiS templates to Normal Non-GiS templates

[Anuradha Yadav]

Hi Team,

We have request from Clients to convert few of our GiS projects to non-GiS projects.

Here is the difference between GiS and non-GiS:

GiS (Group Information Solutions):

Project are created using the DSM IT Templates.

Boards are the template board from the team template project "DSMIT Team".

Installed workflows and configurations.

Script runners are used under GIS for portfolio management.

Confluence connection enabled.

Wo–rkflow scheme is being shared by multiple projects.

Software Simplified Workflow for GiS:

DSMIT Team: Workflow for Story:

• Story
• Bug
• Design Story
• Service Request

DSMIT Team: Workflow for Epic:

• Epic

DSMIT Team: Workflow for Sub-Task II:

• Incident
• Sub-task

NON-GIS:

Standard JIRA setup.

Reports are in separate dashboard.

Default Kanban Board and Scrum Board.

Confluence connection enabled.

No templates used.

No script runners used.

Software Simplified Workflow for Non-GiS:

Issue Types:

• Story
• Bug
• Epic
• Task
• Sub-task

Could you please provide any solutions for conversion of GiS portfolios to non_Gis?

Regards,

Anuradha

[Walter Buggenhout _ACA IT_]

Hi @Anuradha Yadav,

Technically, the main things you'll need to do is:

• replace the issue type scheme from GiS to non-gis
• replace the workflow scheme from GiS to non-gis
• review your dashboards
• disable scriptrunner scripts (if necessary)

Before you do so, be aware that non-gis projects apparently are missing issue types that you have in the GiS projects. Issue types like design story, incident and service request do not exist and must be converted into existing issue types.

The same goes for workflows. They are obviously not the same between the 2 project types, so check up front what statuses from GiS you want to translate into non-GiS.

When updating the schemes, wizards will help you set those mappings during conversion.

If you have issues in your GiS projects that you can't convert to existing non-GiS issue types, an alternative may be to create a new empty non-GiS project (create a new project using shared configuration with an existing project) and then move the issues from the old GiS project into the new non-GiS project.