[Music] [Applause] [Music] hey everyone it's justin thanks for watching in this video i want to talk about microsoft azure devops integration for agile development and servicenow that's right this is a plug-in that you can install in your instance if you're a microsoft azure devops shop and what it will do is it'll synchronize the servicenow agile development with azure devops and i was really pleased with how easy this was to configure yes there's a bunch of steps you have to follow for authentication and credentials and kind of pointing things around and connecting them in the right places in servicenow but it is definitely a lot easier than it used to be i even added a custom field um so that it would pull over something that wasn't there out of the box and it was easy to do i tested it out it worked great so i want to get into it i want to show you this is what it looks like in the store behind me and we're just going to hop straight into it so i have on the right hand side of the screen i have azure devops on the left hand side of the screen i have service now and i'm using a team that's connected with this project a team in service now an agile team that's connected with the project in azure devops so that's at the project level they are integrated and so i'm going to walk through a couple of things first thing i want to do is create an epic and so i want to show that the epic and issues can pass over the store service now as epics and uh and stories that's kind of the connection that you can change that configuration however you want but we'll just do a um demo epic in azure devops i'll just call it ado for now and i'll copy this over to the description oops that's a screenshot let's try copying that again i didn't know i could do a screenshot imagine that that's pretty cool and i'll save that and the next thing i'm going to do let's get my head out of the way for this one is i'm going to create an issue directly from this particular epic so i'm going to create a relationship between the issue and the epic and i want to see that that carries out over in service now so we're going to call this an issue linked with my new um epic in ado and this is going to get older you see me put in ado in the idea but i want to differentiate between what's coming from where in the two systems so i'm going to click ok and now i've got an issue we're going to go ahead and um let's go ahead and put a description in there too description of my issue we'll save that and close it and now everything's done to my satisfaction on the azure devops side i want to see what this looks like on the servicenow side now when you set up the configuration you have control over the scheduled jobs for how often that stuff is imported once it's imported it's going to keep things up to date automatically you don't have to do any extra config other than some custom fields you have to just map them over so no big deal but i have my job running once a day and i really don't want to wait on this demo for all this stuff to come in for an entire day because that would be really boring for you so let's go ahead and we'll just start that import this is giving you a little bit behind the scenes look of how it's configured we can see a history here of what's running so it imported sprints and imported work items and the next thing it should do is kind of link those all right everything is completed so what i want to do is head over to my board here and i'm just going to switch between sprint planning and the backlog and we should see everything is now there right so that's my essentially my refresh now what i want you to see um let's pull this over just a bit i've got my story that came through it was an issue linked with epic and ado and it's already linked to the epic so if i open that story we can see what that looks like i'll just shrink this back here now i want to show you the live updates going back and forth between them so if i open the issue in azure devops i'm looking at the story over in servicenow i'm just going to real quickly i'm going to post a work note so this is a work note from servicenow and we'll just post that and we should see that pop over on the right hand side in the discussion right there it goes it just came through that fast um oh there we go that just came through that fast that work note is there and it's accessible now and everything looks good as far as that's concerned if i wanted to put one back into servicenow i can just say here's a comment from azure devops and save that and that should populate in the work notes over on the servicenow side so if you look over there it should update here in a second there's that work note from servicenow that went over to azure devops and they make up a comment from ato that came from there over to servicenow so that all happened i didn't have to do any extra config this is how the plugin works it's out of the box and the same thing works for things like the short description and description so if we were to change this to a better description of the issue and i'm going to go ahead and put in some acceptance criteria this better work before you complete the story and i will just save that in service now and we should see those two things respectively updates a better description of the issue came through on that side and i don't have acceptance criteria actually passing back and forth i could i could put that somewhere on the azure devops side if i wanted to have that passed back and forth last thing i'll show you i'm going to move this to work in progress so i'm changing the state of the story in that in service now and we should see the state here as to do on the azure devops automatically change doing and likewise if i change doing to done on the azure devops side we should see that state eventually update here on the servicenow side when that call comes we'll actually have to hit save another live demo fail but we'll do it there now and we should see in a second here that state will automatically update we'll get the little blue indicator and it'll update the state from work in progress to complete just like you saw there so that's out of the box servicenow agile development and microsoft azure devops syncing back and forth making sure your epics or issues or whatever work items that you're working on come through and stay in sync what does that mean that means your project management team that might be in service now doing hybrid work like project tasks and looking at stuff that's happening on the development side can now have visibility into azure devops and where things are and relate that to their projects they can keep a pulse on what's going on leave the developers alone so you don't have to bother for status updates and everybody's happy everything saves them sync i got one tip for you though that i learned when i set this up this probably wouldn't apply to an enterprise environment but don't set it up with your account um if you're one of the users of azure devops and you use your account the updates back and forth don't work i've learned that right before recording the video um so i made a couple of changes and made sure the person i'm logged into is azure devops isn't me because that wasn't going to update on the service now side so there's a conflict um if that happens so i hope you found this video helpful if you did please like please subscribe or share with somebody you think might be interested until next time i'll see you in the next one [Music] you