We're excited to announce two qualitative improvements to the user experience that will help you streamline your issue management processes and better identify the origin of your issues: Jira Issue Relinking and Error Sources!
Jira Issue Relinking
Our Error Signature Algorithm constantly undergoes updates and refinements to better group similar issues. Sometimes, an update to the algorithm results in an error with a given signature being replaced with a new error with another signature. Until now, this has broken the issue's link to Jira, but we've modified this behaviour to relink the new issue to the existing Jira ticket, and make any necessary updates. This should cut down on your time spent modifying and managing integrated tickets.
Please note that this update only accommodates 1-to-1 situations, wherein one issue is replaced by another issue. It does not accommodate 1-to-Many or Many-to-1 situations, wherein one issue is split into two or more issues, or several issues are combined into one issue.
We've added a new heading to the Details section in an issue's Overview tab to identify the issue's Error Source. Error sources point to an issue's origin, which may inform how your development team investigates and resolves the problem. This is not a new behavior from the NoibuJS script. The script has always captured error sources, but this is the first time we've surfaced this data point in the user interface.
For a breakdown of these sources and their meanings, visit our Guide to Error Sources.