Creating Relationships

There are multiple types of relationships that can be created in TeamPulse between the different types of entities. There are also multiple ways to create those entities, depending on what stage of planning, development or testing you are currently at. 

 

Story to Story Relationships

 

When defining the User Story requirements in your project, you can use relationships to define how stories relate to one another. The Create a Relationship Between Stories dialog is used for adding new story to story relationships. It can be accessed from the Stories tab while creating or editing a User Story.

 

Relating a Story to another Storyenlarge screenshot

 

To create a relationship, select the Iteration and Area and click the Find Stories button. After the list of stories is loaded, you can further filter the story list by using the Search Within Stories text box. After choosing a story, select a relationship type. There are seven different types of relationships between stories:

  • Affected By
  • Affects
  • Child
  • Parent
  • Predecessor
  • Related
  • Successor

 

All of the relationship types except Related have reciprocal relationships: Affected By/Affects, Parent/Child, Predecessor/Successor. The Create a Relationship Between Stories dialog will prevent the creation of circular relationships when the reciprocal relationship types are selected. There are no restrictions with the Related type other than two stories can't be Related multiple times.

 

The Parent/Child relationships are special types of relationships. When viewing stories in a hierarchy, the parent-child relationship is used to build the hierarchy. Manipulating stories in this view via drag and drop will also create or delete the necessary parent-child relationships.

 

Story to Bug/Risk/Issue/Feedback Item Relationships

 

Relationships between stories and bugs/risks/issues/feedback items are created from the Relate a Bug/Risk/Issue/Feedback Item to this Story dialog. There is only one relationship type, Related, between stories and bugs/risks/issues/feedback items. Using this dialog works the same way as the Create a Relationship Between Stories dialog:

  • Select an Iteration.
  • Select an Area.
  • Press the Find Bugs/Risks/Issues/Feedback Items button.
  • Filter the list by entering text in the "Search Within Results" field.
  • Press the Add Relationship button.

 

Relating a Bug to a Storyenlarge screenshot

 

To add a relation between a Story and Bug/Issue/Risk you need to have permission either for editing stories or for editing bugs/issues/risks.

 

Bug/Issue/Risk/Feedback Item to Story Relationships

 

To ease creating relationships between stories and bugs, issues, risks and feedback items they can also be created from the create and edit bug/issue/risk/feedback items overlays. In the same is only one relationship type, Related, between stories and bugs/issues/risks/feedback items. Using this dialog works the same way as the Create a Relationship Between Stories dialog:

  • Select an Iteration.
  • Select an Area.
  • Press the Find Bugs/Issues/Risks/ Feedback Items button.
  • Filter the list by entering text in the "Search Within Results" field.
  • Press the Add Relationship button.

 

Relating a Story to a Bugenlarge screenshot

 

To add a relation between a Story and Bug/Issue/Risk you need to have permission either for editing stories or for editing bugs/issues/risks.

 

 

Rich Text Relationships Using The Quick Linker

 

Where it makes sense, the Quick Linker allows relationships to be inserted directly into the description of the entity. When the Quick Linker is enabled, pressing CTRL+Space will open the quick linker popup. Also Quick Linker appears when select "TeamPulse Link" option from the Rich Text panel. Initially, the list of available entities that can be linked will be shown. Once you have made a selection, the popup will expand to display the options for that type. Also

 

When the story type is available, you can either select an existing story or type in a new story name. Where available, the type of relationship can also be specified. These types are the same as those that appear in the main story-to-story relationship dialog: Related, Parent, Child, Affects, Affected By, Predecessor, Successor. Only valid relationships are allowed. For example, circular relationships won't be created by the quick linker.

  

Quick Link - Storyenlarge screenshot

   

When the bug type is available, you can either select an existing bug or type in a new bug title.

 

Quick link to bugenlarge screenshot

 

 When the persona type is available, you can either select an existing persona or type in a new persona position. Where linking to a persona from a story, the role of the persona in the story can be specified.

  

Quick link personaenlarge screenshot

  

 When the feedback item type is available, you can either select an existing feedback item or type in a new feedback item name.

 

Quick Link - Ideaenlarge screenshot

 

 When required, the quick linker will create the necessary database relationships at the same time as creating the link in the rich text field. Deleting those rich text links will not affect the database relationships, those must be deleted manually.

 

Relationships and TFS Sync

 

Due to the complexities of relationships in TFS, the standard relationships in TeamPulse are not synchronised to TFS as part of the sync process. The only part of the relationships described above that are sync'ed are the rich text links within the descriptions of the stories, bugs, issues and risks. Feedback items and personas are not part of the sync process and as such, their rich text links are not sync'ed.

 

The Story - Task relationship is an exceptional case. Those parent (story) - child (task) relationships are synced between TFS and TeamPulse.