Love it! Thank you for watching and taking a moment to leave a comment! I elaborate a tad bit more on my appreciation in this comment roll-up video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-SSRnomApE6A.html but probably not worth you trying to find that in a 30-minute video.
This is great! Have you tried to set it up with 2 way integration? I would want to close the ADO story and have it update in SN against the SCTASK. We don't want to go to Agile Dev. We want to bypass that and just go from SCTASK to ADO. Right now we don't need to worry about Incidents either.
Hey there, first thank you for watching! My recommendation is always to have Agile Dev in the middle to save you some integration work but if you'd prefer not to, you can accomplish what you're seeking using the Jira Spoke and Flow Designer to build out your own integration. You can watch me talk about this further and show exactly how to create a data driven board in Comment Desk 002: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-NNwENrHrS2E.html
May I know how the assignment group of the Incident is carried over to the assignment group in the Story in the Traige board? Is there a Business rule running on the story form? By the way, really great content!!! definitely a life saver!!
Thank you so much - I appreciate it! Your comment was in my latest comment roll-up video which you can find here: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-SSRnomApE6A.html. After I recorded that, I had one additional thought. Those triage boards are based on an assignment group. So when adding a task to the board I think the system auto-populates the assignment group on the story based on the triage board configuration. But I'm not sure if it's a business rule or a script include or something else that does the auto-assignment unfortunately. Let me know if there's a deeper explanation behind the question - like what you'd prefer be the behavior versus what you saw in the video and/or are experiencing in your instance. And thanks for watching and taking the time to leave a comment!
Nice overview, Justin! It doesn't seem like a lot of additional work to set up this linkage for non-Agile records, apart from creating the necessary Triage Board(s). The work notes flowing back from ADO to SNow appear to be added to the Story record. Are they also replicated to the Incident or Task record?
They are not! That would be some extra configuration too... and you'd probably want to be very careful as last time I looked into triggers or events based on updates to the sys_journal table it wasn't straightforward. I'm adding this to my list for this series and might do the same for the Jira series as I'm sure others are probably wondering too! Thanks for the thought-provoking question!
Very cool your content! Congrats!!! So, could you can explain more how you implemented this solution? In this moment I’m facing this journey and I discovered that some features doesn’t sync between Azure and Servicenow (details of commit and Pull Requests’ records). I’ll be appreciate if you can help. Thanks!
Thank you so much for the compliment and for watching! This particular integration is specific to planning tasks - both in ServiceNow and Azure DevOps. And when I say planning I'm referring to things like Agile concepts of epics, stories and sprints. To get commit and pull request details, there's a different integration between ServiceNow DevOps and Azure DevOps. You can even get fancy and get pipeline visibility and tie it into ServiceNow's Change Management process. This first link is to my playlist detailing that integration in several videos: ru-vid.com/group/PLqU_zPknanavBUriH5ihcugBa8WW8Hwda. This second link is to ServiceNow's documentation for the same integration: docs.servicenow.com/bundle/utah-devops/page/product/enterprise-dev-ops/concept/azure-devops-integration-dev-ops.html. I hope this information is helpful to you!
