You’re offline. This is a read only version of the page.
584
HI All
Did a quick POC with RSAT and DevOps:
Step 3 is the place I having problems. We use Devops for all of our development and have it so that release pipelines upload to LCS, deploy to Sandbox, etc.
When I sync to DevOps, it creates a ton of EPICs and Issues, when all I want is the tests in many cases. I know you can change the mapping of BPM nodes to DevOps work items, but we're not creating EPICS, Stories, etc for a procure to pay workstream (for example). If we need to to make a mod to a PO we'll just create a story for that.
I did consider linking a different project to LCS, but now we're deploying from LCS, I'm not sure if configuring a different DevOps project for BPM will work
Also, we are using a CMMI process, so why can't I map an LCS requirement to requirement in DevOps (only choice I have is task or bug)?
Wondering how everyone handles this, do you live with all the additional clutter of Epics and Stories created by BPM nodes?
Hi Mark,
The implementation of the integration between LCS and DevOps for test cases isn't a great story. When you read the documentation, you can bypass LCS and manually import test cases in DevOps. docs.microsoft.com/.../rsat-overview
At To-Increase we have an BPM solution add-on within Dynamics 365 called RapidValue where we have a direct integration between RapidValue and DevOps.
Share
Report
All responses (
Answers (
