Issue Links
The Issue link dataset offers a detailed collection of data points related to the relationships between various issues within a work item. This dataset is essential for understanding the interconnections between varied issues while improving the tracking, resolution, and management of issues across projects. It ensures that resources are efficiently allocated across linked issues, reducing bottlenecks and improving workflow. It also provides a holistic view of issues within the project, enabling stakeholders to grasp the broader context and interdependencies.
You need to link this dataset to the issue base dataset to get the issue-related attributes required for blending and analyzing the data by issue link.
You can blend this dataset with the Issue base using the issue attribute to retrieve all assets linked to an issue. Alternatively, you can blend the portfolio item, work item, or request with their respective datasets to obtain those specific details.
The following are the components of this dataset:
| Attribute Name | Description |
|---|---|
| Asset type | Type of the asset link. The examples are epic and story. |
| Issue | Unique identifier for the issue |
| Issue linked end datetime | The closure or removal date and time of an issue for a work item, portfolio item, or request. |
| Issue linked start datetime | The date and time when the issue is linked to a work item, portfolio item, or request. |
| Issue portfolio item | Portfolio item to which the issue is linked |
| Issue request | Request to which the issue is linked |
| Issue work item | Work item to which the issue is linked |
| Link type | It specifies the type of link to another asset, such as links and blocks. Blocks: Issue A blocks Story X, preventing its progress until the issue is resolved. Links: Issue B links to Request Y, showing a relationship but without blocking the request. |
| Sys_source | Unique identifier for the source |
| Metric Name | Description |
|---|---|
| Average duration to link defect | Average time taken to link a defect to the corresponding issue from the time the issue was created |
| Average duration to link portfolio item | Average time taken to link a portfolio item to the corresponding issue from the time the issue was created |
| Average duration to link request | Average time taken to link a request to the corresponding issue from the time the issue was created |
| Average duration to link story | Average time taken to link a story to the corresponding issue from the time the issue was created |
| Duration to link portfolio item | The time taken to associate the issue with its corresponding portfolio item from the time the issue was created |
| Duration to link request | The time taken to associate the issue with its corresponding request from the time the issue was created |
| Duration to link work item | The time taken to associate the issue with its corresponding work item from the time the issue was created |
Use Case: Blocked Work Items from Issue Links
The blocked duration of work items is determined based on the period an issue remains linked to a work item. The calculation starts when an issue is linked to a work item and ends when the issue is either unlinked or closed.
If an issue does not have an end date, the Issue Link dataset considers the last refresh date for calculation.
For example, if an issue is linked to a work item on a specific date, unlinked for a day, then relinked for a few days before being unlinked again, the Issue Link dataset accounts for all these durations when determining the total blocked duration of the work item.