# US 2022/0036014 A1 · Autonomous detection of compound issue requests in an issue tracking system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0036014 A1
- Document ID: US20220036014A1
- Status: Published application
- Kind: A1
- Application number: 17/504,361
- Filed: 2021-10-18
- Published: 2022-02-03
- Earliest claimed: 2019-02-28
- Assignees: Atlassian Pty Ltd.; Atlassian Inc.
- Applicants: Atlassian Pty. Ltd.; Atlassian Inc.
- Inventors: Noam Bar-on; Sukho Chung
- Web page: https://patentgrep.com/patent/US20220036014A1

## CPC

- G06F 40/30: Semantic analysis
- G06F 40/10: Text processing (natural language analysis G06F40/20; semantic analysis G06F40/30; processing or translation of natural language G06F40/40)
- G06F 40/186: Templates
- G06F 40/216: using statistical methods
- G06F 40/289: Phrasal analysis, e.g. finite state techniques or chunking
- G06N 20/00: Machine learning
- G06Q 10/0633: Workflow analysis
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

An issue tracking system configured to determine whether an issue request submitted by a user of the issue tracking system can, or should, be subdivided into two or more issue requests. In some implementations, the issue tracking system is configured to extract a content item of the issue request (e.g., title, description, and the like) in order to perform a semantic and/or syntactic analysis of that content item. Upon determining that the content item includes two or more clauses linked by a coordinating, subordinating, or correlative conjunction, the system can provide a recommendation to the user to submit discrete two or more issue requests, each one of which corresponds to a single linked clause of the content item.

## Claims

### Claim 1

An issue tracking system comprising:
a client device executing a client application; and
a host service operably coupled to the client application of the client device and comprising a processor configured to:
receive an issue request from the client application;
determine a divisibility score based on semantic content of a content item of the issue request; and
in response to a determination that the divisibility score satisfies a divisibility threshold:
generate two or more issue request templates based on the semantic content of the content item, the issue request templates at least partially populated with data extracted from the issue request; and
transmit the two or more populated issue request templates to the client application.

### Claim 2 (depends on 1)

The issue tracking system of claim 1, wherein:
the content item is an issue request description;
the semantic content of the issue request description is a set of lemmatized words extracted from the issue request description;
the divisibility score is increased upon a first determination that the set of lemmatized words includes at least a threshold number of lemmatized words associated with compound issue requests; and
the divisibility score is decreased upon a second determination that the set of words does not include the threshold number of lemmatized words associated with compound issue requests;

### Claim 3 (depends on 1)

The issue tracking system of claim 1, wherein the processor is further configured to:
identify one or more previously-received issue requests that satisfy a similarity threshold when compared to the issue request; and
populate the one or more issue request templates with data extracted from the one or more previously-received issue requests.

### Claim 4 (depends on 3)

The issue tracking system of claim 3, wherein the processor is further configured to determine a likelihood that the previously-received issue requests include data that is substantially similar to the issue request.

### Claim 5 (depends on 4)

The issue tracking system of claim 4, wherein:
a threshold is a first threshold; and
the processor is further configured to determine the likelihood satisfies a second threshold in order to identify the one or more previously-received issue requests that are substantially similar to the issue request.

### Claim 6 (depends on 1)

The issue tracking system of claim 1, wherein:
the client device is communicably coupled to the host service by a network and is configured to receive input from a user to generate the issue request;
the client device is a first client device of a group of client devices each configured to transmit at least one issue request to the processor of the host service;
each client device of the group of client devices is coupled to the host service by the network.

### Claim 7 (depends on 1)

The issue tracking system of claim 1, wherein the processor of the host service is further configured to populate the one or more issue request templates with data extracted from the semantic content of the content item.

### Claim 8 (depends on 1)

The issue tracking system of claim 1, wherein the data extracted from the issue request comprises at least one of:
an issue time to completion estimate;
an issue category;
an issue assignee;
an issue reporter; or
an issue priority.

### Claim 9

A method for operating an issue tracking system to suggest to divide an issue request into two or more issue requests to a client application on a client device that is communicably coupled to the issue tracking system, the method comprising:
receive an issue request from the client application;
extract a content item from the issue request; and
upon determining that the content item satisfies a threshold:
transmitting a signal to the client application, the signal comprising a suggestion to subdivide the issue request into a set of two or more issue requests; and
causing a display of the client application to present the set of two or more issue requests to a user of the client application.

### Claim 10 (depends on 9)

The method of claim 9, wherein the content item comprises a complexity score that corresponds to a time estimation.

### Claim 11 (depends on 10)

The method of claim 10, wherein the threshold is between, and includes, eight hours and twenty four hours.

### Claim 12 (depends on 9)

The method of claim 9, wherein the content item comprises a lemmatized set of words extracted from a description of the issue request.

### Claim 13 (depends on 12)

The method of claim 12, wherein the threshold is a word count.

### Claim 14

An issue tracking system for suggesting one or more issues to a client application on a client device that is communicably coupled to the issue tracking system, the issue tracking system comprising:
a host service; and
a database communicably coupled to the host service;
wherein the host service is configured to:
receive a first content item of a first issue request from the client application;
identify a second issue request comprising a second content item that satisfies a similarity threshold when compared to the first content item;
access the database to identify a third issue request tagged as a subtask of the second issue request;
generate a first issue request template from the second issue request;
generate a second issue request template from the third issue request; and
transmit a suggestion to replace the first issue request with the first and second issue request templates to the client application.

### Claim 15 (depends on 14)

The issue tracking system of claim 14, wherein:
the client application is configured to display the first and second issue request templates;
the client application is configured to receive additional issue data from a user to complete at least one of the first or second issue request templates; and
the client application is configured to generate at least one subsequent issue request based on the completed first or second issue request template.

### Claim 16 (depends on 14)

The issue tracking system of claim 14, wherein the host service is further configured to determine a divisibility score based on semantic content of the content item of the first issue request prior to identifying the second issue request.

### Claim 17 (depends on 16)

The issue tracking system of claim 16, wherein the content item of the first issue request is a lemmatized set of words based on an issue request title or description.

### Claim 18 (depends on 16)

The issue tracking system of claim 16, wherein the content item of the first issue request is a tokenized set of words based on an issue request title or description.

### Claim 19 (depends on 18)

The issue tracking system of claim 18, wherein:
the content item of the first issue request comprises a time estimation;
the divisibility score comprises a numerical value based on the time estimation; and
the first threshold is between, and includes, eight hours and twenty four hours.

### Claim 20 (depends on 19)

The issue tracking system of claim 19, wherein the numerical value is further based on one or more of:
an issue request assignee;
an issue request reported;
a project;
a project type;
an issue request type; and
an issue request category or tag.
