Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Connect GitHub repositories with Jira Service Management
Changes to Free and Standard plans in Jira Service Management
As of October 16, 2024, change management for Jira Service Management will move from Standard to Premium plans. After this point, only Premium and Enterprise plans will have access to this feature.
Existing projects in Free and Standard plans will continue to support existing request types and issue types. Read more about the plan changes.
You can connect GitHub to your IT service project to track your deployments. To map GitHub repositories with your services, you must first setup the GitHub app for Jira. Learn how to add GitHub integration to Jira.
After adding the GitHub app:
From your service project, select Project settings, then Operations, then Change management.
Select Connect Pipeline > Github, then copy the Service ID at the end of the setup flow.
Go to your GitHub account.
Create a folder and name it .jira
Then, create a file in this folder and name it config.yml. You can now map your services in this file.
In the config.yml file, enter the service IDs you want to map into this repository. You can use the following script example:
1
2
3
4
deployments:
services:
ids:
- b:YXJpOmNsb3VkOmdyYXBoOjpzZXJ2aWNlLzQxODczNDgyLTUzZWUtNDczOC1hYmI1LWFiMzRhNmZlNGNlMC8xYmJlYjkwMi05MGNkLTExZWMtOWZhMi0xMjhiNDI4MTk0MjQ=The services you map into the GitHub repository should be in the same service project. You must use a different service project if you wish to use another repository. If there are invalid service IDs, GitHub will discard those, and they will not be mapped.
You can map up to 100 services to each GitHub repository.
Now that you’ve connected and mapped GitHub, you can start using deployment tracking and incident investigation view. Learn how to setup deployment tracking.
Was this helpful?
Still need help?
The Atlassian Community is here for you.