Software-issue graphs

A tangible, non-transitory, machine-readable medium storing instructions that when executed by one or more processors effectuate operations comprising:

• obtaining, with one or more processors, a plurality of software-issue reports, each software-issue report describing a software bug to be fixed or feature to be added to a software application;
• obtaining, with one or more processors, a pull request identifying a branch of source code of the software application in a version control system;
• forming, with one or more processors, a software-issue graph having a plurality of nodes corresponding to the software-issue reports and a plurality of edges indicating relationships between the software-issue reports, wherein forming the software-issue graph comprises at least one of the following:
• determining that a first software-issue report must be addressed before a second software-issue report and, in response, adding an edge to the software-issue graph indicating the first software-issue report must be addressed before the second software-issue report;
• determining that a third software-issue report is a duplicate of a fourth software-issue report and, in response, adding an edge to the software-issue graph indicating the third software-issue report is a duplicate of the fourth software-issue report;
• or
• determining that a fifth and a sixth software-issue report each are a species of a seventh software-issue report and, in response, adding a pair of edges to the software-issue graph indicating the fifth and the sixth software-issue report each are a species of the seventh software-issue report, wherein
• the software issue graph is formed with a machine-learning model obtained trained by obtaining a log of historical workflow instances addressing software-issue reports and training the machine learning model used to form the software-issue graph with the log of historical workflow instances, and
• the machine-learning model is updated based on user adjustments to previous outputs of the model indicating incorrect edges;
• determining, with one or more processors, that the pull request addresses a given software-issue report;
• selecting, with one or more processors, a subset of nodes in the software-issue graph addressed by the pull request based on the subset of nodes sharing a respective edge with the given software-issue report and respective relationships indicated by the shared edges;
• designating, with one or more processors, in memory, the pull request as being associated with the given software-issue report and the plurality of software-issue reports corresponding to the selected subset of nodes.