There are no formal dependencies in agile software development. However, it often comes that way that one piece of work is tied to another piece of work. In Targetprocess you can track such dependencies via Relations.
Relations can be identified as Dependency, Relation, Link, Duplicate or Blocker at your discretion. Dependencies Dependency means that a user story,task, etc. depends on another user story, task, or any other entity. For example, the core team is
It is possible see if there’re any relations for User Stories, Features, Bugs and other entities, looking at their cards on a board.
Entities Relations can be visualized as Lanes and Cards on a View.
The primary visual graph to track informal dependencies between work items.
In this article we gathered examples of useful Advanced Filters for Views and Visual Reports that help to select, hide or highlight data by Relations and related entities such as Inbound and Outbound user stories, bugs, features, epics, requests. Relations in Targetprocess
As you spotted bug duplicates, you can choose which bug is primary and which one should be marked as duplicate. You can mark a bug as a duplicate following 3 alternate ways: Using the Actions > Find Duplicate menu
As you spotted duplicates of requests, you can choose which request is primary and which one should be marked as duplicate. You can mark a request as a duplicate following 3 alternate ways: Using the Actions > Find Duplicate menu item of the Request view
Productivity tip that suggests a handy way to refer to another entity