Issue tracking system using a similarity score to suggest and create duplicate issue requests across multiple projects

1. A device operable with an issue tracking system and comprising:

a memory allocation; and

a processor allocation configured operate with the memory allocation to instantiate an instance of a client application providing frontend functionality of the issue tracking system, the client application configured to:

communicably couple to a host providing backend functionality of the issue tracking system;

submit, to the host, a request to create a first issue record in a first project;

receive from the host, a message comprising:

information that the first issue record exhibits a similarity exceeding a threshold to a second issue record, the second issue record among a cluster of interrelated issue records in a second project, each issue record in the cluster of interrelated issue records in the second project corresponding to a discrete task related to the second project; and

a suggestion of at least one other issue record to create in the first project, the at least one other issue record based on a third issue record selected from the cluster of interrelated issue records in the second project;

display an issue creation request in a graphical user interface of the client application, comprising:

the suggestion received in the message; and

a set of user-editable fields configured to receive user input; and

in response to a user confirmation input provided to the request, submit, to the host, a request to create a fourth issue record in the first project based on input received in the set of user-editable fields and the suggestion.

2. The device of claim 1 , wherein the suggestion comprises a set of other issue records to create in the first project, each based on a respective one issue record selected from the cluster of interrelated issue records in the second project.

3. The device of claim 1 , wherein the first project is associated with a first software platform and the second project is associated with a second software platform.

4. The device of claim 1 , wherein the first project is associated with a first operating system and the second project is associated with a second operating system.

5. The device of claim 1 , wherein the client application is configured to populate at least one user-editable field of the at least one other issue record based on at least one field of the first issue record.

6. The device of claim 1 , wherein the information includes an indication that a description field of the first issue record and a description field of the second issue exhibit the similarity exceeding the threshold.

7. The device of claim 1 , wherein the information includes an indication that a title field of the first issue record and a title field of the second issue record exhibit the similarity exceeding the threshold.

8. The device of claim 1 , wherein the information includes an indication that a first field of the first issue record and a second field of the second issue record exhibit the similarity exceeding the threshold, the first field different from the second field.

9. The device of claim 1 , wherein the information includes an indication that the similarity is determined by one of:

determining a cosine distance between the first issue record and the second issue record;

determining a Jaccard similarity between the first issue record and the second issue record;

determining Euclidean distance between the first issue record and the second issue record;

determining a Manhattan distance between the first issue record and the second issue record; and

determining a semantic similarity between a first field of the first issue record and a second field of the second issue record.

10. A device operable with an issue tracking system and comprising:

a memory allocation; and

a processor allocation configured operate with the memory allocation to instantiate an instance of a host service providing backend functionality of the issue tracking system, the host service instance configured to:

communicably couple to a client application instance providing frontend functionality of the issue tracking system;

receive, from a client application instance, a request to create a first issue record in a first project;

compare at least one field of the first issue record to at least one field of a second issue record, the second issue record among a cluster of interrelated issue records in a second project, each issue record of the cluster of interrelated issue records in the second project corresponding to a discrete task related to the second project;

determine that the at least one field of the first issue record and the at least one field of the second issue record exhibit a similarity that exceeds a threshold;

select, from the cluster of interrelated issue records in the second project, at least one other issue record;

modify at least a portion of the at least one other issue record based on the first issue record;

transmit, to the client application instance, an issue creation form comprising a set user-editable fields, at least a portion of the set of user-editable fields including the at least the portion of the at least one other issue record; and

in response to a user confirmation received from the client application instance, send, by the host service, a request to create the at least one other issue record in the first project using content of received in the set of user-editable fields.

11. The device of claim 10 , wherein the similarity is determined by one of:

determining a cosine distance between at least a first portion of the first issue record and at least a first portion of the second issue record;

determining a Jaccard similarity between at least a first portion of the first issue record and at least a first portion of the second issue record;

determining Euclidean distance between at least a first portion of the first issue record and at least a first portion of the second issue record;

determining a Manhattan distance between at least a first portion of the first issue record and at least a first portion of the second issue record; and

determining a semantic similarity between at least a first portion of the first issue record and at least a first portion of the second issue record.

12. The device of claim 10 , wherein the at least one other issue record comprises three or more issue records.

13. The device of claim 10 , wherein:

the similarity is a first similarity;

the threshold is a first threshold;

the at least one other issue record is a third issue record;

the cluster of interrelated issue records is a first cluster of interrelated issue records;

the host service instance is configured to:

compare at least one field of the first issue record to at least one field of a fourth issue record, the fourth issue record among a second cluster of interrelated issue records in a third project;

determine that the at least one field of the first issue record and the at least one field of the fourth issue record exhibit a second similarity that exceeds a second threshold;

select, from the second cluster of interrelated issue records in a fourth project, a fifth issue records;

modify at least a portion of the fifth issue record based on the first issue record; and

the suggestion comprises the fifth issue record and the third issue record.

14. The device of claim 13 , wherein the first project is associated with a first operating system, the second project is associated with a second operating system, and the third project is associated with a third operating system.

15. A method of generating an interface for an issue tracking system at a device comprising a memory allocation and a processor allocation, the processor allocation configured to operate with the memory allocation to instantiate an instance of a client application providing frontend functionality of the issue tracking system, the method comprising:

submitting, to a host providing backend functionality of the issue tracking system, a request to record a first issue record in a first project;

receiving from the host, a message comprising:

information that the first issue record exhibits a similarity exceeding a threshold to a second issue record, the second issue record among a cluster of interrelated issue records in a second project, each issue record of the cluster of interrelated issue records in the second project corresponding to a discrete task related to the second project; and

a suggestion of at least one other issue record to record in the first project, the at least one other issue record based on a third issue record selected from the cluster of interrelated issue records in the second project;

displaying, via a graphical user interface of the client application, a set of user-editable fields, at least a portion of the set of user-editable fields including at least a portion of the suggested issue record the suggestion to a user of the client application; and

receiving, from the client application, a confirmation input to create a new issue using content of the set of user-editable fields.

16. The method of claim 15 , wherein the first project is associated with a first operating system and the second project is associated with a second operation system.

17. The method of claim 15 , wherein the first project is a associated with a first software platform and the second project is associated with a second software platform.

18. The method of claim 15 , wherein the cluster of interrelated issue records comprises at least three issue records in the second project.

19. The method of claim 15 , wherein the suggestion comprises an indication that a first field of the first issue record and a second field of the second issue record exhibit the similarity.