Digital Product Release - Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
13 hours ago
Hi all,
I gently need some clarifications about DPR integrations:
Change Request
- I got that each Release can contain more than one CR, but why? I thought just one unique CR was created before Deployment.
- All CRs are created before deployment (as in the print below)? Because I read that CRs can be created in any Release phase but I do not understand how it is possible and it does not match with the print below. Can you please provide examples?
- So each release can have more than one CR, but what about the relation between CR and product / version / feature (many CRs per 1 version? many CR per 1 product? 1 CR per 1 feature?).
SPM
- If SPM module is installed, how can I for example link a project to a release product? I only have to do that manually? E.g. I create: Product is Incident Management and Features are portal UI/UX, forms, notifications
Connection tools
- I got that "connection tools" section is used to import Features from external systems such as Jira and SPM.
Can you please provide examples of what is imported and how to reuse the data in DPR? Which can be a possible use case?
Many thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Hi @Tommaso2 ,
Change Request Update:
Currently, we are not enforcing a restriction of one Change Request (CR) per release, nor are we aligning release dates with CR schedules, as we mentioned in your earlier post.
Relationship Between Change Requests and Releases:
The Change Request table includes a relation to capture the associated release product version.
One product version can hold multiple CRs.
Connection Tools:
Using the connection tools, we can import release versions and work items (Epics, Stories, Defects, etc.) created in Jira. Therefore, if a release version has already been imported into DPR, there is no need to create a duplicate release version within DPR.
For better understanding, please refer to the following recording demonstrating Agile tool integration:
Section:
4) Integrate DPR with Agile 2.0 and auto-import Epics and Stories
Recording Link:
https://www.servicenow.com/community/digital-product-release-blogs/what-s-new-in-digital-product-rel...
SPM Integration:
To better understand how SPM integrates with DPR, please refer to the recording below. It illustrates the relationship between SPM and DPR with a practical example.
Section:
3) Seamless release planning to execution experience in ServiceNow
Recording Link:
https://www.servicenow.com/community/digital-product-release-blogs/what-s-new-in-digital-product-rel...