 GitLab issues are a powerful tool for discussing ideas and planning and tracking work. However, many organizations have been using Jira for these purposes and have extensive data and business processes built into it. While you can always migrate content and process from Jira to GitLab issues, you can also opt to continue using Jira and use it together with GitLab through our integration. Once you integrate your GitLab project with your Jira instance, you can automatically detect and cross-reference activity between the GitLab project and any of your projects in Jira. In this demo, we're going to discuss the basic integration of Jira and GitLab. Looking at this mock organization, Health Care Provider Incorporated, we have an organization that's set up different verticals or business units amongst the organization. What we're going to do is take a look at the restorative therapies group, dive a little deeper into surgical technologies. These are all subgroups, and then within this surgical technologies subgroup, you have several different projects. The front-end engineering team is going to set up that integration. This can also be done instance-wide, so if I were to go into admin area, if I have admin access and I go to service templates, I'm able to go down here and set up the Jira integration as well. But we'll be doing this at the project level. I can see I have a repository here, and what I'll do is go to settings, integrations, scroll down to find Jira. Once I've found Jira, I'll need some information that I need to populate or create over in Jira, and so that's where I will go. Here we have our project for Health Care Provider Incorporated. This is our Kanban board with several different issues. I will come back to this in a minute. But what we'll need to do is go to our API tokens for our Elassian.com cloud instance, and here we can create an API token, create that, copy that. Now I'm going to bring that back over into GitLab. Here I'm going to have a web URL. This is going to be our company name plus at lassian.net for cloud. I don't need to have anything here. If I'm using Jira cloud, if I am using Jira server, then I'll need to add this API URL here. For username, it's just my username. It's recommended that you have an admin username for your Jira integrations. Something like admin.gitlab.com, or whatever your organization may be, have that. If someone leaves the organization that they don't have an integration set directly to their email. That API that we copied, we're going to put that here. I'm going to enter that there. Next, what we need to do is gather some transition IDs. In the most recent Jira user interface, you can no longer see transition IDs in the workflow administration UI. You can get the ID you need in a couple of different ways by using the API with requests like we'll see here. Where I've put in our instance URL at arrest API slash to issue. Then I've used one of the open issues right now and transitions. What we can do is we'll be able to get IDs out of here. There's a lot here to find the IDs. I can either do it this way, pull the ID transition IDs from this JSON, or I can use something like a JSON formatter. Take this copy that, put it in there, process it, and then it's going to format a little easier where I can get those IDs. These are all our transition IDs. I'll take 11, 21, 31, and 41. Once I have those, I can go back into GitLab, add those transition IDs, populate them here. Test savings and save changes. Jira's activated, so we are now good to go using this basic Jira GitLab integration. If I go over here to my board, let's take this particular issue that I've created inside of Jira. We'll see that there's HPI 34, I have no comments, no activity yet with this. I'll go back to GitLab, let's go to our repository, and we'll make a commit and a merge request, and we'll see how that populates and links back into Jira. I'll use GitLab's built-in Web IDE. Just make a quick change. Commit that, and this is where I will add a commit message and create a new branch. This is where it's important that I will now add that issue ID that we saw here. So, HPI 34 inside of Jira, I put 31, so I actually need to make it 34. Add a commit message, and to keep things consistent, I'll do this with the branch as well. And then we can commit this, and then now what we'll see, once this is done, I'll go over here, commit that, and either it'll refresh itself, or I'll need to refresh it real quick, but we'll have that activity from GitLab here inside of that Jira issue. So, I can see now in the comments section, if I want to click over to this, it'll take me to that specific issue, and if I want to click on that web link, it'll take me back to GitLab showing me that commit. If I didn't finish my merge request, so if I completed this merge request, submitted that merge request inside of GitLab, you will also see that show up here as part of web links. Now I have a merge request, and again that will open up directly into that merge request into GitLab. You can also see here now that there's a Jira link here, and this will take me all to all my projects inside of Jira, and that's going to be part of that left side panel inside of GitLab. So this is a basic integration using Jira and GitLab, have the ability to have visibility into the links, tying back that issue inside of Jira to merge request or to commit that you are working on inside of GitLab. For how to on adding a development panel on the right side for your integration with Jira and GitLab, be sure to check out the next video talking about Jira's dev panel availability using GitLab.