How do you link stories with update sets?

[lmoore]

Is there a relationship between update sets and stories (agile)?

I'd like to have an update set created for each story as it is worked.  Is there a way these link together and any way to auto update the update set based on the story being worked on?

[Curtis2]

I just checked to see if there was a related list item for this purpose.  At my company, we have a custom list control field which allows us to link 1 to x update sets with a given story; however, if I were reviewing and approving today, I think I would set up update sets as a related list to stories.

Either way, this would be a customization but would make a good RFE as well.

[SusanWinKY]

I've been thinking about how we can track update sets created for a story, but we haven't put a formal solution in place. Typically an update set is created in a sub-prod instance. How would we link the story (in prod) to a sub-prod update set?

To get around this now, I ask our developers to put the name of the update set(s) in a comment or work note on the story. That is not reportable, so I am considering a free-form text field on the story form to track the update set name(s). That field would only be visible to 'admin' users.

Another thing we do is name our update sets by the story #. For example...

STRY0123456_someDescriptionHere_v1
STRY0123456_someDescriptionHere_v2

And if the story requires work across multiple scopes/applications, we will also add the application name to the update set. For example...

STRY0123456_someDescriptionHere_Global
STRY0123456_someDescriptionHere_Agent Workspace

[John Zhang1]

There are no a relationship between Story and update set table.  We created a new referenced field "Update set" (referenced from update set) on Story table (rm_story) so each story can referenced by this customized field.

[lmoore]

When you say you created a field on the story table you went through the Story and Configured the Form Layout, correct?  What "field type" did you use?