 Hi, I'm Tytivus with GitLab here today to show you how to set up a GitLab to Elastian Jira integration using Jira's automation triggers. We'll get right into it here, showing how we can set up a trigger with a commit that moves a transition from open to in progress or in progress to close. You can also set up triggers that shows the merge request and the branch as well in the dev panel within the Jira issue. Let's go. So we start inside the Elastian Marketplace. I'm gonna go search for the GitLab app. And once we pull this up, we're gonna go ahead and download GitLab for Jira. Quickly get that app. Get it now. It's gonna be adding GitLab for Jira. Go to manage app. And once this is loaded up, we go ahead and get started. And this is where we're gonna add the namespace from GitLab. So if we go over to GitLab, we can see that I have the namespace highlighted. I'm gonna copy and paste what's after GitLab.com backslash. I can be as specific as I need to be. I wanted to do tech marketing here. All the subgroups underneath would take on this integration. But in this case, health care provider and corporate is the only one that's gonna be synced with Jira. For Jira, we're gonna go down to project settings, go to automation, and then inside of automation, this is where we're gonna be able to create some rules. And you can see that there's several different triggers located inside of Jira. We're gonna scroll down until we get to DevOps and we'll select commit created, save that. And then we're gonna create a new action. Again, scroll down and we're gonna click transition issue. We're gonna click in progress, save. Let's name this automation. We'll just call it the commit created, create committed move issue. And then turn that on. And now that automation piece has been turned on using that trigger. Go back to the project and we're looking at HPI-43 here. As a user, I want two important versions. We're gonna dive into that. Copy the link to that indicator, the ID. And then if we go inside of GitLab, we'll click over to Jira issues. Look at the issue list and we can see here that we have that exact issue pulling over. If I click onto that, it takes me back over to Jira. So the Jira view list inside of GitLab is just a mirror. Scale back to the project here and once again, looking at that specific issue over in Jira. We're gonna go into our repository and then click into the web IDE. For here, we're gonna make just a quick change. It's a very simple code chain on a very simple project. So in this case, we're just changing the background color for demo purposes, but we're gonna go ahead and commit that. This is where on the commit message, I'm gonna reference that key from Jira and put HPI-43 pound sign in front of that. It's important and just write a commit message to test your automation. As well, I'm gonna put this in the branch so that we have consistency across both. I'll commit that. Then I'm gonna go back into the issue as a user. I want to import versions, actually I'm gonna refresh and then we'll see here that's now moved to the in progress. So based on that trigger that I had, that just moved it to in progress quickly. You can see the web link there to the commit on the development panel side there. You see that that commits now showing. There you have triggers.