The issue tracking system (ITS) is a rich data source for data-driven decision making. Different characteristics of bugs, such as severity, priority, and time to fix may be misleading. Similarly, these values may be subjective, e.g., severity and priority values are assigned based on the intuition of a user or a developer rather than a structured and well-defined procedure. Hence, we explore the dependency graph of the bugs and its complexity as an alternative to show the actual project evolution. In this work, we aim to overcome uncertainty in decision making by tracking the complexity of the bug dependency graph (BDG) to come up with a bug resolution policy that balances different considerations such as bug dependency, severity, and fixing time for the bug triaging. We model the evolution of BDG by mining issue tracking systems of three open-source projects for the past ten years. We first design a Wayback machine to examine the current bug fixing strategies, and then we define eight rule-based bug prioritization policies and compare their performances using ten distinct internal and external indices. We simulate the behavior of the ITS and trace back the effect of each policy across the history of the ITS. Considering the strategies related to the topology of the BDG, we are able to address bug prioritization problems under different scenarios. Our findings show that the network-related approaches are superior to the actual prioritization task in most cases. Among the selected open-source projects, LibreOffice triagers are the only ones who disregard the importance of the BDG, and that project is faced with a very dense BDG. Although we found that there is no single remedy that satisfies all the expectations of developers, the graph-related policies are found to be robust and deemed to be more suitable for bug triaging.

中文翻译：

---

Wayback Machine：捕获开源软件系统中错误依赖图的进化行为

问题跟踪系统 (ITS) 是用于数据驱动决策的丰富数据源。错误的不同特征，例如严重性、优先级和修复时间，可能会产生误导。类似地，这些值可能是主观的，例如，严重性和优先级值是基于用户或开发人员的直觉而不是结构化和明确定义的过程分配的。因此，我们探索了错误的依赖关系图及其复杂性，作为展示实际项目演变的替代方案。在这项工作中，我们的目标是通过跟踪 bug 依赖图 (BDG) 的复杂性来克服决策中的不确定性，以提出一个 bug 解决策略，该策略可以平衡不同的考虑因素，例如 bug 依赖、严重性和 bug 分类的修复时间. 我们通过挖掘过去十年三个开源项目的问题跟踪系统来模拟 BDG 的演变。我们首先设计了一台 Wayback 机器来检查当前的错误修复策略，然后我们定义了八种基于规则的错误优先级策略，并使用十个不同的内部和外部指标来比较它们的性能。我们模拟 ITS 的行为并追溯每个策略在 ITS 历史中的影响。考虑到与 BDG 拓扑相关的策略，我们能够解决不同场景下的错误优先级问题。我们的研究结果表明，在大多数情况下，与网络相关的方法优于实际的优先级任务。在选定的开源项目中，LibreOffice 分类员是唯一无视 BDG 重要性的项目，并且该项目面临着非常密集的 BDG。虽然我们发现没有单一的补救措施可以满足开发人员的所有期望，但发现与图相关的策略是健壮的，并且被认为更适合进行错误分类。