 I'm Ty Davis with GitLab. Today, here to talk to you about how Alassi and Jira and GitLab CICD come together to have visibility from a project management perspective from using Jira into GitLab CICD capabilities and how you could bring those together using both tools. Let's jump in the demo and see how we can do that using Alassi and Jira's deployment capabilities within Jira Cloud. So here I am in Alassi and Jira. We're looking at my board right now. And on the left side, we have a panel with a few different options to choose from. What I want to do is enable deployment. So I'm going to go to project settings, down to features, and then I'm going to enable deployments. If I go back to my project, I should now see deployments here. In this case, if I click on deployments, it's going to allow me to add another CICD tool. That's what I want to do for GitLab. So if I go in here, give me two options, connect to other providers. I'll take you down to gitlab.com for Jira Cloud. I'm going to go ahead and click that. And what this is going to have me do is install the GitLab app as part of Alassi Marketplace. So let's get started. In this case, I already have it. It's installed. And so what we need to do now is align a namespace with that project that we have inside of Jira. You can see I have two different namespaces here where I can get a very specific using instead of GitLab, where I go down to groups and subgroups and to a specific subgroup that will have a cadence of projects underneath it. I can go to a specific project. Or in this case, I have just tech marketing, which is the parent, the top level group. And by adding that namespace, it's going to give me access to all subgroups and projects that fall within that tech marketing parent group. If I go into add namespace, you'll see a little bit more what I mean by the different choices that I have. I can link specific groups here. Let's say in this case, healthcare provider incorporated. If I link that, you can see that now I have access inside of Jira to that group and specific project of 501c3 billing inside of GitLab. So from here, I can go back into my project. Again, I have this building to that board. I have deployments, but still, I don't have anything connected here. And that is because I haven't done some configuration instead of GitLab. So I navigate back into GitLab. If I go down the settings, this is where I can go to integrations. And this is where I can enable the Jira integration that's specific to my project. So I'm going to enable Jira transitions. You can have move to done so automatically transition Jira issues to the done category. Let's say once a merge request is completed, we can also use custom transitions. So each of these transition IDs will be directly related to transition within Jira. So that could be in progress or done. What we can use is smart commits. When we're doing a commit or merge request within GitLab to help move something from one transition to another. Down here, we need to grab the web URL. Once we have that web URL, we can add that in here. So next we go to Jira API URL. This is if it's different, the web URL. You can insert that there. In this case, I'll leave it blank because the web URL is similar. We have a username and email. And then now we need to generate a password API token. What I can do is go to id.atlastian.com. And this is where I can create an API token to insert there. I'll put, let's go API. Copy that. And then back over to GitLab. I'll paste that. Then here we have a View Jira Issues in GitLab. So you can see your Jira issues from within GitLab. If I enable that to GitLab as you can now enable Jira issues. And you can create vulnerabilities from security reports that you find in GitLab. And if there's a vulnerability reported and found, what you'll see is you'll have that capability to create a vulnerability specific issue that will be created over in Jira. And that's where you need the project key right here, which is required to generate those issue types. So if I go back over to Jira, I go the issue key is LAR. Come back over here. And I add that in. Let's test the settings. Connection successful. I can see here that this is just Jira issue type. There's different choices I can have. If I want to make this custom, I can create a vulnerability back in Jira so that it comes through as a vulnerability in Jira when there is one detected within GitLab. I'm going to save those changes. Now we have that set up within GitLab. We have that integration activated and we can begin doing some work or changes inside of GitLab kicking off our CI CD. And what we'll see is that Jira will bring over that visibility into the deployments that we're doing. So let's go ahead and this is just real, real simple. I can import some issues. I'll create an issue here. Let's go back into Jira and take this here. Demo purposes. I'm just going to take that and add that to the title. And then we have a couple of different things that we can get here. So what we can do is create a merge request. And what I'm going to do is create a merge request that's tied to this issue. And if I open up that Web IDE, we're going to make a nice simple change so that we can see that a pipeline has been kicked off inside of GitLab. And then we'll have that visibility back in Jira. So in this case, let's just change this color. Now, this is an important piece. We talked about smart commits earlier. This is where I can now connect this commit, this branch, and what's next is this merge request to that Jira issue. So if I go back in here, I see this LAR-1 is the ID for this issue. That's what I'm going to put inside my commit message that's going to be a smart commit and that's going to connect this commit to that issue within Jira. Let's go ahead and say that it's in progress. Let's go over to that merge request that's associated to that commit. Here I can see that a pipeline's been kicked off. And if I go back over into Jira, I can now see that the issue moved from to-do to in progress. If I click into this, I'm going to have visibility in the comments sections. This is going to pull from GitLab the activity. Over here in the development, I can see that I have a commit. If I connect into that, here's that commit. This will redirect me over back into GitLab, but I still don't see my merge request. So what I'm going to do here is I'm going to go back to the deployments and then I'm going to see, oh, I still don't have anything on the deployments page. And why is that? That's because that merge request needs to be connected. And what needs to be done is we go back in and we edit that. Again, the smart commits piece. I believe there's LAR-1. Let's see if that changes. You can see that it's now an issue in Jira. If I come back over here, click into this, that specific issue. I now have that pull request that's tied directly to the LAR-1 issue in Jira. It's going to have, again, a connection to GitLab. If I were to go back over, opens it up in GitLab. Now let's go back to deployments and see if I have any visibility over there. Over in deployments, we can see that the issue is now connected. It's now showing the results from the pipeline that was ran within GitLab. We can see more information if we'd like. It takes us to the deployment section. If I want to click into this, this is going to take us back to that specific project within GitLab. It's going to give me visibility into the pipeline. I can see that it failed at the review stage. And so now you have that traceability from both Jira and GitLab. If you're using your project management inside of Jira and you want visibility into that CI CD piece with an issue that may be a developer's taken on and they've built some code around it. Maybe they had a vulnerability submitted and it's being worked on. That change is made in its kick that's committed and it kicks off a pipeline. You now have that visibility using Jira deployments and pulling in that GitLab CI CD information. This has been Atlassian's demo den. I'm Ty Davis with GitLab. Thank you for taking the time to watch this video and to find out more information on how GitLab and Jira work together. You can either go to gitlab.com and search GitLab Jira or go on Jira and do the same as well. Thank you again.