[Music] thank you hey everyone it's Justin thank you for watching and welcome to my house that's Justin's house in this video it's more Azure devops and servicenow and in this video I'm going to show you how to skip the backlog and automatically get an incident over to Azure devops without adding it to your backlog without using a triage board and we're going to use flow designer to make all that happen so in the previous video I'll link to it up above if you haven't seen it I basically go into the triage board and I grab an incident add to the backlog and it automatically syncs that over to Azure devops and believe it or not for some people that's still not good enough they want the an agent someone who's managing an incident like a service desk agent or a customer service person to be able to create an incident and it automatically go over to that team and you can do it and never have to go into this agile backlog and we're going to do that using flow designer so info designer I have a flow here I'm going to swing this open just a little bit I've got Azure devops open in the background but we'll get to that in a second first thing I've done in this is I've said hey if there's an incident created in service now and the state is not closed resolved or canceled and the assignment group is my Agile development team or my Azure devops development team here we've got servicenow sprinters then this flow will automatically execute right so you can set up whatever conditions you want here it doesn't have to be like I did it it could be P1 incidents it could be stuff that affects a particular service or a CI you are the master of what you set for your conditions but once you do then all you have to do is create a story record and when we create that story record we can use the fields on the incident in order to populate that story record so look what I did here I have assignment groups short description and parent if I use my right annotation tool um already set and populated using information about the incident so let's take a look at the incident record I have in the incident record a strong short description so there is my short description I just drag that over and that automatically populates the story short description I also have a description which is right here I drag that over and it populates the description and I want to go ahead and set the parent of this to the incident number so I just grab the instant record and set the parent of the story to the incident record that binds and connects the story and the incident together so they show up correctly if someone were to go look in that backlog once that's done we're going to go ahead and sync the story with Azure devops now I'm using a custom action here stay tuned for a future video I'll show you how easy it is to make this custom action it's not a big deal at all but we're basically just saying go ahead and sync that even though we're creating this in a workflow otherwise it wouldn't actually sync it because it thinks it might get stuck in a loop so we had to create this special custom action here then once that's done we're going to go update the incident record and set the correlation display and correlation ID to that what got created in jira so when we sync it over to jira we get back the number and the sys ID and we're just going to go ahead and sync those things actually is that I think this is sync in the story sorry I misspoke there so when we use this update incident record we're updating the incident to be aware of the story when we created the story we made the incident record the parent but now we're going to tell the story that it has a related record in the incident by updating the correlation display and correlation ID so what we do is we just grab it from that story record I'll just show you here we've got the story number which is just the number field of the scroll down here we drag that over that sets the number or the correlation display what people see and the ID is going to be this this ID of that record for the story so I'll just scroll down here there's assist ID and we drag it in there so that's those two things and then we'll just go ahead and be nice let people know that there's some automation going on in the background and we'll say that this story number has been created and assigned to the assignment group name for servicenow sprinters really really clean there and now we have a flow that is what four steps in order to automatically skip that backlog activity that we showed the previous video so let's get to it let's go to incidents and show you how easy this is to do I'll just pull up all my incidents and I'll just go to I think it's incident.list that'll get me there faster that's the table name of the incident table instead of looking for the menu item I'm just going to create new and we'll go ahead and swing this window back over so that we can see Azure devops over here on the right when we create that incident over here in servicenow so let's go ahead and set the short description incident in service now for servicenow sprinters and the YouTube you want to make sure this is just for you guys incident um auto sync example and remember the only thing that's really important is we need to set that assignment Group which I'm not seeing someone's got a weird form on here oh I'm in the service operations workspace form let's go ahead I don't know how I got in that view you know what I did um let's go because I don't have I can't set this oh no here's assignment group okay let's go and set this time right through there it's just a little bit different than I was expecting but that's okay um all right so we got all that yeah and you could do all this from the surface operations workspace you don't have to do it here um I don't have a collar we'll set Abraham Lincoln as the caller and now I'll save and that is automatically going to run that flow or that workflow in the background create the story associated with it add a work note if we scroll down here we should see wherever the work notes are I'm not sure is it going to show do I have work notes in this view I don't have write notes in the service operations workspace view let's go to uh default view and we should see uh the worker the comments I think we did additional comments or what you know I can't remember um there we go and there it is story zero zero one zero zero two nine has been created just like our workflow is supposed to do so now if I come up here to Azure devops I'm just going to click on there and we should see that issue or story automatically come through I'm not seeing it yet so let's scroll down make sure I don't have multiple Pages Here There It Is incident and service I don't know why the last time I did that too incident service now for surface house printers and the YouTube we'll just go ahead and add a comment here uh we see it and are on the case to fix and that's how easy it could be to communicate with those teams that are using Azure devops and get information to them and back into servicenow very quickly without ever having to use a backlog or a triage board like I showed in my previous video we should see that comment come over here in a second to our not our incident but actually our story so I don't have stories showing here so tell you what you're going to see something new we're just going to configure a related list on this default view and we're going to add stories so that we see those show up at the bottom list there so I'm going to go ahead and edit this View and we'll scroll down to the s's where we should see story and I want the parent to be that so we had parent set as the story where the story has its parent value set to the incident when we set up our workflow so if we scroll down here and look at stories now there's our story for servicenow sprinters and we can open that up and see that that work notes that have come through where we see it and are on the case to fix it's that easy and you know what I really feel obligated now that I got tied up into that service operations workspace view let's go ahead and hop over to service operations workspace I wasn't planning on show you this but I want you to see that we can do all that and see all that from within these new workspaces we don't have to be in the regular UI here's my service operations workspace we'll just hop over to Mario list View and basically I want to pull up all my incidents and we should be able to see that come through so there's incidents we'll just go open uh because we did create that new incident and that should show all the open incidents there we go it pulled up you can actually see it there internet and service now for servicenow sprinters and the YouTube so no different here just a different user interface to look at what an internet looks like and uh that's it we should be able to look at related records and see maybe the story without having to do much work I'm actually not sure I didn't test this out before before I recorded I wasn't planning on using service operations workspace um yeah it doesn't show up here but that's just something we configure in the workspace we can have those stories show up so don't fret that's definitely doable but if you still needed to create an incident and assign it to the service now support team service now sprinters team you could do that from here so I'm just going to do it and roll with it uh here's the new incident from so w for the YouTube and uh demo from sow and then we just need to set the set the color again let's grab all over your hand Lincoln and let's set the assignment group and this is the key thing right the assignment group is really what's filtering and doing all that so I hit save there and that should automatically create that and then we should see in the work notes show up here live um unlike we did in the other view where I had to change views and everything we should oh no we're not going to see it here because it's on the story record that's okay let's go ahead and make that a little bit smaller um we'll get down there we see a new incident from us from sow for the servicenow sprinters group and I'm just going to go back to my work items here and um let's just see here click there and last time I had to scroll down and scroll up and then it showed up I don't know if that's an Azure devops bug but you see it worked new internet from sow for the YouTube and now those two things are syncing back and forth so that's incidents automation using a flow and flow designer to synchronize incidents in servicenow with issues in Azure devops I hope you found this video helpful if you did please like Please Subscribe or share with somebody who you think might be interested in integrating servicenow and Azure devops and until next time don't forget to always be learning foreign [Music]