Has anyone seen that the Original Task and not the Enhancement field on a Story record is updated when an Enhancement is pulled into a teams backlog via the Unified Backlog(UBL)?

[Wesley8]

We want to use the new unified backlog (UBL) vs. creating a story from each enhancement record.  However, when you create a personal backlog and add in Enhancements when individual Enhancements are pulled into a teams backlog, the story that is automagically created in the UBL does not have a value in the Enhancement field.  The story's original task field has the enhancement number; however, the enhancement field on the automatically created story is blank.

The impact is that when you view the enhancement record, the automagically created UBL story is not listed.  The enhancement record only shows what stories are created directly from the Enhancement record.

We see value in the using the UBL; however, if we use the UBL, we lose the connection of the new story to the enhancement unless we search on the original tasks.

Is this a bug?  Shouldn't the story created from the UBL populate the Enhancement field and the Orginal Task field on the story record?

Does anyone know if this is a bug and if the bug has been corrected in Marid?

Thanks, Wesley

[Madhu80]

Wesley, what you mentioned is an intended behavior. The Unified backlog can be used against any type of task. So the links provided out of the box are from story to the enhancement through the Original task field and from the original task to the Story record through the Agile Story field.

[Wesley8]

Madhu,

Thanks for the response and I understand.  One thought, since SNow pulled enhancement and defects into SNow Agile 2.0 and introduced the UBL, it would be great if the UBL allowed the story record to be updated with the Defect and Enhancement number similar to how those fields get updated when a story is created directly from the Enhancement or Defect.  

As we are trying to use the capability to create Enhancement / Defect from an Incident, unless I create the story directly from the Enhancement or Defect, the stories don't show up in the Enhancement / Defect record.  Since the story record has specific fields on the record to link to Enhancements / Defects, for me, deductive logic that says if UBL creates an Enhancement or Defect, the UBL should also populate these fields.

Our requirement Story looks like this:

As a product manager, i want to be able to go to my enhancement or defect list and see all my stories tied to the enhancement or defect regardless if I created them from the UBL or directly from the Enhancement or Defect record.  I want this so that I can see if Stories are linked directly to an enhancement or defect as that is the way I track the enhancement requests coming from our user community.

Hope this makes sense.  Wesley