 Complementary to our existing Jira project integration, you're able to integrate GitLab projects with the Jira development panel. Both can be used simultaneously. This works with self-managed GitLab or GitLab.com. The Jira development panel will be displayed on the View Issue screen providing functionalities that allow you to view branches, commits, and pull requests. Let's take a look at the Jira dev panel integration with GitLab and how to set it up. Here we start with health care provider incorporated. This is where we're going to see our top-level group and all of the subgroups and projects that fall underneath that parent or top-level group that will help be nested as part of that top-level group and will take on the Jira integration that we're going to set up here. If I'm going to look at restorative therapies group, we can see that this is one of the BU's or verticals and they have several different product areas underneath. If we look at surgical technologies, we'll see that we have several different teams that reside within a GitLab project and have their repositories hosted as well as where they are creating issues. The first thing I need to do is go to my profile picture. I'll go to Settings and then we'll go to Applications. Now, what I'm using here is self-manage GitLab to integrate with Jira.com, so their cloud version, but you can do the different options, Jira server connected to GitLab.com or Jira server to GitLab self-managed. In this particular case, I am again using my self-managed GitLab to connect to Jira cloud. I'm going to give it a name, Jira development panel example, and then a redirect URL where it's going to be your GitLab instance domain slash login slash OAuth slash callback. For self-manage, take the example down here of my callback URL. We'll see that I have gitlab.demo.itp, the online slash login OAuth callback here. If you're using gitlab.com, this would be gitlab.com slash login slash OAuth slash callback. I'll select the API scope and I'll save this application and now it's providing me some information around application ID, a secret, and the callback URL. From there, I'll head over to Jira. I can see inside of Healthcare Provider Incorporated, our organization. This is one of our Kanban boards. Up top, I'm going to select the gear icon. If this is the new modern UI for Jira, it's in the bottom left. So I'll click products. Go to integrations, find a DVCS accounts, and then I'm going to choose the link GitHub Enterprise account, which will work for GitLab. And here, I'll see a couple of different choices. So I have team or user account. This is where we're going to take that top level group that we see here, Healthcare Provider Incorporated. Make sure it matches that URL group. We'll take that and that is what we're going to add to that top level. And all the subgroups will take on this integration underneath because they are nested under that top level group. The host URL is going to be my URL for myself managed. And then we'll take that client ID, which is going to be the application ID instead of GitLab. So those are the equivalent of one another. I'll add that in. Same with secret. And then we'll add, we'll get a couple of dialogue boxes here. Continue. It's going to kick me back to GitLab admin. I'm going to authorize this and then it's going to start to sync those groups and the projects and the repositories that are part of all under Healthcare Provider Incorporated top level group. Once this has been completed, it's now pulled in all the repositories for all the different projects of part of all the subgroups and groups within Healthcare Provider Incorporated. I want to ensure if we're going to use smart commits that these are initiated. It's going to show last activity with specific repositories. In this particular case, we can see that there's commits, pull requests and issues going on here. If I don't need to use a repository, I can simply delete that and remove it from the integration and I won't have to have that viewed or convoluting any of the other integrations that I wish to see. Going back into our organization's JIRA instance, looking at Healthcare Provider. This is our con bond board for a specific project. This is where we're going to see how that integration is now built out. In this particular case, let's take a look at an issue. This is the issue that I want to start working on as a developer. I see my ID here, HPI-28. This is going to be important once we go into GitLab and I begin my work and I make my commit. I go over to GitLab. This is the team that's working on that particular issue. This is where I'm going to go, let's say, into that repository or make the changes to the existing code that is already there. As an example here, we'll just add a very simple, non-specific file as an example. This is where we will use that commit message that we just had. We're going to go back. We see that HP-28, that's what we need to reference. I reference that, HPI-28. This is where smart commits will come into play. I can comment. This is going to match what transitions we have here. We have selected for development, backlog, and progress and done. It needs to match those exactly. Once you've gone in and you've customized it for your organization, just when you're doing your smart commit, that's what needs to be referenced when writing out the commit message. For consistency, I'm going to make my branch have the same name, or at least the ID is going to be similar so I can reference the two. I'm going to commit that change. It's going to kick off a pipeline inside of GitLab if we have our CI CD setup. It's going to also open a new merge request. This is where I'm going to fill out any information around that merge request that I need. I'm going to submit that. I will also see that merge or pull request reference back inside of JIRA. I have my issue here. If I go ahead and refresh that, what I'll see is that some web links and activity and comments have come through. This is stuff that it comes with the basic JIRA GitLab integration. What I need to see is that dev panel over here. I need to see that transition move from select from development to in progress. Now, with the integration that we set up, every 60 minutes it's going to refresh. We need to go in there and make this refresh ourselves. This is an extra step, not necessary if you don't need that. As it stands right now, every 60 minutes JIRA is going to refresh those repositories. If I go over here, refresh my repositories. This is the one that I want. I'm going to go ahead and click that. Now that has refreshed, we can come back over here and reload this page. Now we can see that that development panel here gives us information that's directly connected to GitLab and the branch that we created, the commit that we made in the pull request. I could go to that branch and it's going to open that up. Give me the option to go into GitLab, look at that branch. If I want to see the commit, it's going to allow me to go to that commit, go back into GitLab, and same thing for that pull request known as a merge request instead of GitLab. So I can go there, see that pull request, and get any information that I want and see how the activity is going or collaborate within that merge request and comment or talk to that developer and see if there's any help or how progress is going. Now something I want to show is that that transition also moved this issue to end progress. So the smart commit that we made, it moved it to end progress and now I didn't have to do that manually as a developer. By just putting that in my commit message, it moved it automatically. So once this pipeline has kicked off, sorry not kicked off, once this merge request that was just created runs and it's ready to be merged, I can merge this and it's going to merge in the pipeline succeeds. What that's going to do is it's going to come back into Jira here and it's going to close. It's going to show that this pull request has been merged and it's going to close this issue. So again, taken away from that manual work that has to be done. What that does is it closes it, it makes the less work that the developer has to do going back and forth from tools and gives a nice integration between these two tools that teams are using within their own team or their own organization. Next, we're going to talk about how we can take these issues into Jira and import these into GitLab so you can get your project management into one single application just using GitLab and having all of that information in one place and not have to go back and forth between the tools. In addition to using the DVCS connector as described in this video you can use the GitLab for Jira app which is recommended when using GitLab.com and Jira Cloud because data is synchronized in real time while the DVCS connector updates data only once per hour. You can integrate GitLab.com and Jira Cloud using the GitLab for Jira app in that Lassian marketplace.