Ingesting Jira Epics and User Stories into Digital Product Release

AllanPG · a month ago

Hello All,

We are trying to capture Jira epics and user stories into ServiceNow Digital Product Release. We've setup the Tool connection and we can get the Jira projects listed under the Plans portion of DPR. But when we open the project in DPR, the Epics or user stories which are in Jira are not there. We were expecting to see them under Work Items or Features that we can associate with Releases.

I hope someone here can provide guidance on how we can utilize DPR, so we can map our Jira epics and user stories to DPR Releases

AllanPG · 4 weeks ago

Hi @rohitroy ,

Thank you for these steps. I tried them in Digital Product Release, and i was able to import the Jira user stories.

Now I created a sample Release in DPR to test if I can apply these user stories now work items in DPR to the release. But, again I could not see them as based on my screenshot below. Hope you could still guide me on this part.

rohitroy · 4 weeks ago

Hi @AllanPG ,

There are few ways in which the Epics, stories (work items) can show up in the Release Scope page.

1. Automatic Enhancements generation: If there are Epics which doens't have any parent epic will be translated as an Enhancements, when you import that data (as you have done in the previous steps you shared). Ideally the enhancements for each of those epics should have been created and will be displayed in the Release planning page and from there can be planned to be kept in any release or backlog. After assigning the enhancements it starts showing up in the respective Release scope page. Suspecting that some sequence of steps might have gone wrong bcs of which it didn't get created automatically.

2. You can manually create enhancements and associate the workitems (epics) to the enhancement. While creating the enhancement there is an option called

3. "Auto-create product versions from plan versions" is enabled at the time of plan association to the product. In this case whenever a new Fix version (unreleased state) is created within your Jira Account then it will automatically create a Version in Digital Product Release and also create a draft release for that version.

Whichever epic (independent) is attached to that fix version in Jira will be created as enhancement and shown to the Release scope page and also the respective stories which are tagged to that fix version will also be shown in the release scope page.

Below are some vital links which you help you achieve it ->

*** search this key in the below page url given -- "Enhanced release planning support with Jira Fix Version automation" >>

https://www.servicenow.com/community/digital-product-release-blogs/what-s-new-in-digital-product-rel...

https://www.servicenow.com/docs/bundle/yokohama-it-service-management/page/product/digital-product-r...

rohitroy · 4 weeks ago

@AllanPG One of the past reply on the similar topic might give you more insights of the technical aspects >>

https://www.servicenow.com/community/digital-product-release-forum/unable-to-import-work-items-that-...

AllanPG · 3 weeks ago

Hi @rohitroy ,

Thank you for the additional information. Unfortunately i'm still not able to apply the imported work items to te release i created. I tried to create an Enhancement, but I'm not seeing the epics . When I looked at the imported work items from the table sn_devops_work_item, i only see Story and Task under the Type column. Could that be the reason? But we do have actual Epics in our Jira, so why are they not included?

I also checked sn_devops_m2m_work_item_plan_version and sn_devops_m2m_plan_version_software_model tables, and these are empty. I created a new release hoping that it could somehow populate the tables, but maybe there is something missing on the process which i cant see.

I hope you have more information i can try to finally get thoses Jira work items mapped with the release records i created.

rohitroy · 3 weeks ago

There are no epics imported as part of your import otherwise it will show up in the Features tab. Below SS is shared by you in your one of the previous comments. Make sure while importing and setting the date range covers your epic creation/updation date then that will get imported.

If still not able to import, with your Jira application do some minor changes to epic like some short description or epic name change and later you can revert it back if you want. This process will fire a new event in the servicnow and it will get processed in real time. (This will only work if you have "configured" your tool and track option is enabled for your Plan in servicneow)

Once you have the epics in the table then you will be able to create the enhancements out of those.