Identifying and resolving software issues

A non-transitory computer-readable storage medium having computer-executable instructions stored thereon which, when executed by a computer, cause the computer to:

• obtain data describing one or more characteristics of an unresolved issue with a software component from an issue tracking system;
• obtain data describing one or more characteristics of one or more resolved issues from the issue tracking system;
• identify at least one resolved issue that is similar to the unresolved issue from the one or more resolved issues based upon the one or more characteristics of the unresolved issue and the one or more characteristics of the one or more resolved issues;
• identify, based upon data maintained by a version control system, a plurality of changes that were made to the software component in order to resolve the at least one resolved issue that is similar to the unresolved issue, wherein the version control system maintains a version control graph for the software component that identifies the plurality of changes made to the software component and relationships between the plurality of changes;
• determine a similarity between the plurality of changes that were made to the software component in order to resolve the resolved issues;
• and
• perform one or more corrective actions on the unresolved issue based at least in part upon the similarity between the plurality of changes to the software component by providing a recommendation identifying changes to the software component that are similar to one another.

A computer-implemented method for performing one or more corrective actions with respect to an unresolved issue with a software component, the method comprising:

• obtaining data describing one or more characteristics of an unresolved issue with a software component from an issue tracking system;
• obtaining data describing one or more characteristics of one or more resolved issues from the issue tracking system;
• identifying, from the one or more resolved issues, at least one resolved issue that is similar to the unresolved issue with the software component based upon the one or more characteristics of the unresolved issue and the one or more characteristics of the one or more resolved issues;
• identifying, based upon data maintained by a version control system, a plurality of changes that were made to the software component in order to resolve the at least one resolved issue, wherein the version control system maintains a version control graph for the software component that identifies the plurality of changes made to the software component and relationships between the plurality of changes;
• determining a similarity between the plurality of changes that were made to the software component in order to resolve the at least one resolved issue;
• and
• performing one or more corrective actions with respect to the unresolved issue based upon the similarity between the plurality of changes to the software component by providing a recommendation identifying changes to the software component that are similar to one another.