How can I create a change management project with the appropriate workflows, custom fields, etc.?

[Tobias Essig]

I had a JSON file created with all the properties, but the challenge is that I cannot import schema or workflows with a JSON file. So I created a PowerShell script that creates the project, but this doesn't work with workflows, schema, issue types, etc. Does anyone have any ideas on the best way to do this? Or is there a template for a change management project where the workflow is already stored with the appropriate issue types and fields and all the properties?

[Trudy Claspill]

Hello @Tobias Essig 

Welcome to the Atlassian community.

There are several built in space/project templates available in Jira Cloud. Each come with a default set of work items types, workflows, and fields/screens.

Without knowing what you consider to be an appropriate configuration, it is not possible for us to recommend to you which one to use.

What types of changes are you trying to manage? Are they changes to software products? Are they changes to infrastructure?

Who needs to be informed about and interact with the change information?

Do you have only Jira available to you or do you also have Jira Service Management?

Do you have the necessary permissions to create a project through the UI? If not, have you consulted with the administrators of your Jira instance?

[Tobias Essig]

Hello @Trudy Claspill 

Thank you for your message!

I can show you an example, as I have already created a JSON file with all the properties.
The project is intended to cover all changes, whether software, infrastructure, processes, etc.
We would like to implement the following configuration:

Project information:
Key: CHG
Name: Change Management
Type: Software project (Kanban template)
Project manager: admin
Description: For change management with extended workflow and all required fields

Process types:
Change: Planned change with special workflow
Task: Accompanying tasks
Epic: Major changes or releases
Problem: Optional cause for a change

Workflow scheme:
Workflow name: Change Workflow
Status: Draft → Under review → Approved → In progress → Implemented → Completed / Rejected
Transitions: e.g., “Forward for approval,” “Reject,” “Back to applicant”

Custom fields:
Change type: Selection field (Standard, Normal, Emergency)
Risk assessment: Selection field (Low, Medium, High)
Approved by: User field
Planned implementation date: Date field
Rollback plan & affected systems: Text fields

Screen configuration:
Change screen: Contains all relevant fields for a change process

I hope this information is more useful to you.