Creating a Change Request related to a Story - "Agile Story" field or "Parent" field?

[Duncan Pederse1]

We are creating a UI Action on a Story record to "Create Change Request."

We are trying to select a field on the Change Request to relate it to the Story: the Parent field, or the Agile Story field.

Parent appears to be baseline on the Task table. Creating a Change Request from a Demand, for example, will populate the Parent field with the sys_id of the Demand.

Agile Story is a field that comes installed with the Agile Application. I know it is populated with a Story sys_id when you add an item to a Backlog using a Triage Board. However, I am not sure of its other uses.

Which field would be preferable? Does either field have functionality that would make it a good or bad choice? Looking for advice.

[lanyang · Accepted solution]

I would recommend not to use Agile Story field. The field is inherited from task table which represents the story created from the task. 

This field is introduced by Agile Development 2.0 - Unified Backlog. Using this field might break functionalities in the unified backlog plugin.

Please view: https://docs.servicenow.com/bundle/newyork-it-business-management/page/product/sdlc-scrum/concept/un...

[Steve Kelly]

Hi Duncan,

We are about to look into implementing a similar integration between Stories and Change requests. I was thinking of using the Parent field for this on the Change Request. Did you end up implementing the UI Action, and any lessons learned or feedback on the approach?

Thanks,

Steve

[Duncan Pederse1]

Hey Steve,

Agile Story was definitely not the correct choice, so we used the Parent field, because other records like Demands also use the Parent field when they create Change Requests.

Parent has worked great for us. No complaints. No hiccups. We think it was the right choice.

[Steve Kelly]

Awesome, thanks Duncan!