Relations | Targetprocess - Visual management software

Relations

There are no formal dependencies in agile software development. However, in practice pieces of work are often tied to one another. In Targetprocess you can track such dependencies via Relations.

For example, if the core team is building an API, some or all of the other teams' work may be dependent on the core team's progress. Or, if the infrastructure team is performing technical maintenance, the production team's work is on hold until the maintenance is done. Or, if you have customers who reported a defect and are awaiting a notification that the fix is released. Keeping track of these informal dependencies in your head can be tiresome. Here is when relations are extremely useful.

Entities in Targetprocess can be related to each other within predefined data model links and via Relations. Principles of how these two types of dependencies work are different.

Directions of Relations

Relations have directions. For a work item they can be Inbound or Outbound.

Directions of Relations

Relations always appear in the Relations tab for both of the related entities, either as Inbound or Outbound. When there is a relation from a Request to a User Story then:

  1. The User Story with the relation to it is displayed as an Outbound item for the Request;
  2. The Request with the relation to it is displayed as an Inbound item for the User Story.

Relations. Image 2

Sometimes Relations do not have an obvious inbound/outbound direction, which you choose many cases is a matter of personal preference. Neutral relations are not supported in Targetprocess.

Advanced Filters, Visual Encoding rules, custom calculation formulas and API expressions work with the data model directly. In the model, Inbound relations of an entity are indicated as MasterRelations, and Outbound relations of an entity are named as SlaveRelations. A Relation object indicates an entity on the outbound side (where the relation begins) as Master and a one on the inbound side (where the relation ends) as Slave.

Types of Relations

The relations can be identified as DependencyRelationLinkDuplicate or Blocker at your discretion.

Types of Relations. Image 1

Find more details in the dedicated article: Types of Relations

How to View Relations

Relations in Detailed Views

You can see existing relations for any entity (user story, bug, feature, task, etc.) via the Relations tab in its detailed view:

relations tab

Relations on Views

Relations between entities can be displayed as arrows on Board, Roadmap, List views.

The feature replaces deprecated extension (mashup) named Custom Unit Show Relations. The feature is available in Targetprocess v3.12.5++. Administrators of On-Site Targetprocess installations need to perform update tasks manually to get the feature activated properly.

Relations between items in any state (open, in progress, closed) are displayed. If a card has an arrow pointing away from it, it's an outbound relation. If a card is being pointed at, it has an inbound relation to the other card.

iteration-plan-by-team

To make Relations visible, press Actions > Relations > Show button:

Relations. Image 4

When Relations are visible, you can select with checkboxes types of Relations you'd like to see. Or, Hide all the Relations completely.

Relations. Image 5

The Relations Network Diagram report is one more way to visualize relations between items.

Relations Count on Cards

Customize Cards to add counters of Open Relations to cards on your views.

Relations. Image 8

More on this feature: Relations on cards

Manage Relations as Cards and Lanes on Views

To view and manage Relations of multiple items on the same screen it is possible to create and customize dedicated Board and List views.

New relations can be easily added right from the view via Quick Add buttons. To manage existing relations double-click on a card and navigate to Relations tab in detailed popup view. An alternative option is to use drag-n-drop action to re-distribute cards across lanes or to use 'Add relation...' action from context menu.

More information: Manage Relations as Cards and Lanes on Views

Relations Network Diagram

The Relations Network Diagram helps to visualize the existing connections.

To access this chart, please navigate main (top) menu -> Reports -> Relations Network.

Relations. Image 9

More information: Relations Network Diagram

Add, Edit, Delete Relations

To manage the relations of an entity, open its detailed view and switch to the Relations tab.

relations tab

You can create a relation for any entity (user story, bug, feature, task, etc.) there.

To create a Relation with an existing entity or multiple entities please click on the ‘magnifying glass’(search) button.

search_for_relation

To add a new entity and create a relation with it in one step, you can use ‘quick add’ button.

add relation from tab

You can easily remove a relation if created by mistake. A click on the Unlink button breaks any relation between entities.

Relations. Image 13

Also, the type of relation can be easily changed.

Relations. Image 14

It is also possible to create dedicated Board and List views for relations management. More information: Manage Relations as Cards and Lanes on Views

Since Targetprocess v3.13.8+ it's possible to create a relation between two entities directly in a Board view where these entities are selected as cards. Simply right-click on the needed card, choose "Add relation..", specify what card should the first one be related to and what type of relation is between them.

add relation

Afterward, this relation can be also edited/removed directly from the mentioned Board view. Right-click on a shown relation and decide whether you want to change its direction or delete it from the system.

realtion board

Access Permissions

You can set a relation between any entities in Targetprocess, no matter which Project or Team they are assigned to.

To add a new relation or change/remove one, a user must be able to modify both related entities. More on this requirement: Permissions for Access to Work Items.

When you have top-level managers who should have permission to create relations between any work items in your system consider providing them with Contributor access instead of including them to members lists of all the projects.

Reports

See also

Still have a question?

We're here to help! Just contact our friendly support team

Email us
The more details you can give us the better
Live chat
Prefer instant messaging? Try our live chat
Service Desk
Add tickets, comments and track status in our Helpdesk
Slack Community
Shape the future direction of Targetprocess

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.

Start your free trial

Enter your email
By clicking "Continue", you acknowledge and agree that we will process your personal data in accordance with our Service Privacy Policy and Terms of Service.

We’ve sent you a confirmation e-mail — please, go check it.

Or get a live
product demo