IP Library › Granted Patent US 12,561,294
Granted Patent B2
US 12,561,294 · App. 18/242,464 · Granted Feb 24, 2026

Software quality ticket enrichment

Inventors: Peter Groenewegen (Sammamish, WA); Nikola Minkov Mihaylov (Redmond, WA); Larissa Marie Cox (Seattle, WA); Nicholas Taylor Mullen (Seattle, WA); Mark Alistair Wilson-Thomas (Mercer Island, WA); Paul Chapman (Seattle, WA); Kshama Gajraj Bafna (Woodinville, WA); Abhishek Kumar (Folsom, CA); Jason Chlus (Hoboken, NJ); Holly Mitchell (Bellevue, WA)
Assignee: Microsoft Technology Licensing, LLC
G06F16/215G06F16/24578G06F16/951
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,561,294
App. No.
18/242,464
Filed
Sep 5, 2023
Granted
Feb 24, 2026
Kind
B2
Art Unit
2153
USPC
707/709
Abstract

Searches based on an incoming ticket identify quality ticket enrichment data using a vector database. Language model prompts target particular kinds of quality ticket data. The incoming quality ticket, or a search result ticket, or both, are enriched using enrichment data, such as a user intent identification, a workaround suggestion, a resolution description, a target audience description, a relevance description, an impact description, a description of missing resolution facilitation information, an association between the incoming quality ticket and the search result ticket, a user sentiment identification, a tag suggestion, or a feedback utility estimate. The enrichment reduces engineering and support burdens, and facilitates faster more effective resolution of the problem or the request that is stated or implied in the incoming quality ticket. Duplicate tickets are merged or removed. Tickets are prioritized. Missing problem resolution information is identified and requested sooner.

Claims (113)

1 . A quality ticket enrichment method performed by a computing system, the method comprising:

calculating an embedding vector from at least a portion of an incoming quality ticket;

searching a vector database, the vector database having associated quality ticket data, wherein the vector database searching comprises searching for quality ticket data which relates to the incoming quality ticket, and the vector database searching is based on at least the embedding vector; and

enriching, with a data enrichment, the incoming quality ticket by displaying at least a portion of the data enrichment in the incoming quality ticket;

wherein the data enrichment is based at least on the quality ticket data which relates to the incoming quality ticket; and

wherein the data enrichment comprises at least one of: a user intent identification, a workaround suggestion, a resolution description, a target audience description, a relevance description, an impact description, a description of missing resolution facilitation information, an association between the incoming quality ticket and a search result ticket which is a result of the vector database searching, a user sentiment identification, a tag suggestion, or a feedback utility estimate.

2 . The method of claim 1 , further comprising:

harvesting at least a portion of the data enrichment from the search result ticket;

wherein the data enrichment comprises at least one of:

the workaround suggestion;

the resolution description;

the target audience description;

the relevance description;

the impact description; or

the description of missing resolution facilitation information.

3 . The method of claim 1 , wherein enriching the incoming quality ticket comprises:

submitting at least a portion of the incoming quality ticket to a language model with a prompt that targets data enrichment, and in response receiving at least a portion of the data enrichment from the language model.

4 . The method of claim 3 , further comprising:

filtering an output of the language model and excluding a portion of the output from the data enrichment.

5 . The method of claim 1 , wherein calculating the embedding vector comprises:

basing the embedding vector on at least one of:

a user set identification; or

a ticket set identification.

6 . The method of claim 1 , wherein enriching the incoming quality ticket comprises:

harvesting at least a portion of the data enrichment from the search result ticket; and

wherein the method further comprises:

prioritizing the incoming quality ticket or prioritizing the search result ticket or prioritizing both, wherein prioritizing is based on at least a result of harvesting.

7 . The method of claim 1 , comprising:

getting at least a portion of the incoming quality ticket via a user interface, wherein the embedding vector calculating and the vector database searching each chronologically overlap the getting; and

displaying at least a portion of the search result ticket.

8 . The method of claim 1 , wherein enriching the incoming quality ticket comprises:

submitting at least a portion of the incoming quality ticket to a language model with a set of prompts that individually or collectively target an aspect of the data enrichment, and in response receiving at least a portion of the data enrichment from the language model; and

wherein the set of prompts targets at least three of:

a set of steps for reproducing a problem;

a condition for reproducing a problem;

a feature title;

a feature description;

an offering identifier;

a problem description;

a suggestion;

a description of missing resolution facilitation information, the description including a log request;

a description of missing resolution facilitation information, the description including a screenshot request;

a request that missing resolution facilitation information be obtained when signed into a product;

a description of missing resolution facilitation information; or

a guide to collecting missing resolution facilitation information.

9 . The method of claim 1 , wherein the incoming quality ticket has a problem summary;

wherein the data enrichment comprises a remedy, the remedy comprises a workaround suggestion, a resolution description, or both; and

wherein the method further comprises:

submitting at least a portion of the remedy and at least a portion of the problem summary to a language model with a prompt to assess the remedy relative to the problem summary, and in response receiving an assessment of the remedy from the language model.

10 . The method of claim 1 , wherein the data enrichment comprises the association between the incoming quality ticket and the search result ticket; and

wherein enriching the incoming quality ticket comprises at least one of:

displaying a suggestion to merge the incoming quality ticket and the search result ticket; or

merging the incoming quality ticket and the search result ticket.

11 . A quality ticket enrichment computing system, comprising:

a digital memory;

a processor set comprising at least one processor, the processor set in operable communication with the digital memory;

a vector database interface which upon execution by the processor set accesses a vector database which is associated with quality ticket data; and

a data enricher which is configured to, upon execution by the processor set, calculate an embedding vector from at least a portion of an incoming quality ticket, submit the embedding vector to the vector database interface, receive a search result from the vector database interface, and enrich with a data enrichment the incoming quality ticket using the search result by adding at least a portion of the data enrichment in the incoming quality ticket;

wherein the data enrichment comprises at least one of: a user intent identification, a workaround suggestion, a resolution description, a target audience description, a relevance description, an impact description, a description of missing resolution facilitation information, an association between the incoming quality ticket and the search result ticket, a user sentiment identification, a tag suggestion, or a feedback utility estimate.

12 . The quality ticket enrichment computing system of claim 11 , wherein the data enrichment comprises at least one of:

the user intent identification;

the user sentiment identification; or

a user identification.

13 . The quality ticket enrichment computing system of claim 11 , wherein the digital memory stores a list of predefined user intent identifications; and

wherein the data enricher is configured to, upon execution by the processor set, enrich the incoming quality ticket with at least one of the predefined user intent identifications.

14 . The quality ticket enrichment computing system of claim 11 , further comprising:

a language model interface;

wherein the system upon execution submits at least a portion of the incoming quality ticket to the language model interface with a prompt that targets an aspect of the data enrichment, and in response receives at least a portion of the data enrichment from the language model interface.

15 . The quality ticket enrichment computing system of claim 14 , wherein the prompt targets at least one of:

the feedback utility estimate;

the user sentiment identification;

a set of steps for reproducing a problem;

a condition for reproducing a problem;

a feature title;

a feature description;

an offering identifier;

a problem description;

a workaround;

a solution;

a suggestion;

a description of missing resolution facilitation information, the description including a log request;

a description of missing resolution facilitation information, the description including a screenshot request;

a request that missing resolution facilitation information be obtained when signed into a product;

a description of missing resolution facilitation information; or

a guide to collecting missing resolution facilitation information.

16 . A computer-readable storage device configured with data and instructions which upon execution by a processor cause a computing system to perform a quality ticket enrichment method, the quality ticket enrichment method comprising:

searching a vector database for quality ticket data which relates to an incoming quality ticket, the vector database having associated quality ticket data; and

enriching, with a data enrichment, the incoming quality ticket by displaying a suggestion, which suggests editing the incoming quality ticket to include the data enrichment;

wherein the data enrichment is based at least on the quality ticket data which relates to the incoming quality ticket; and

wherein the data enrichment comprises at least one of: a user intent identification, a workaround suggestion, a resolution description, a target audience description, a relevance description, an impact description, a description of missing resolution facilitation information, an association between the incoming quality ticket and the search result ticket, a user sentiment identification, a tag suggestion, or a feedback utility estimate.

17 . The computer-readable storage device of claim 16 , wherein enriching the incoming quality ticket comprises:

submitting at least a portion of the incoming quality ticket to a language model with a prompt that targets data enrichment, and in response receiving at least a portion of the data enrichment from the language model.

18 . The computer-readable storage device of claim 16 , wherein enriching the incoming quality ticket comprises:

submitting at least a portion of the incoming quality ticket to a language model with a prompt that targets an aspect of the data enrichment, and in response receiving at least a portion of the data enrichment from the language model; and

wherein the prompt targets at least one of:

a set of steps for reproducing a problem; or

a condition for reproducing a problem.

19 . The computer-readable storage device of claim 16 , wherein enriching the incoming quality ticket comprises:

submitting at least a portion of the incoming quality ticket to a language model with a prompt that targets an aspect of the data enrichment, and in response receiving at least a portion of the data enrichment from the language model; and

wherein the prompt targets at least one of:

a feature title;

a feature description;

an offering identifier;

a problem description; or

a suggestion.

20 . The computer-readable storage device of claim 16 , wherein enriching the incoming quality ticket comprises:

submitting at least a portion of the incoming quality ticket to a language model with a prompt that targets an aspect of the data enrichment, and in response receiving at least a portion of the data enrichment from the language model; and

wherein the prompt targets at least one of:

a description of missing resolution facilitation information, the description including a log request;

a description of missing resolution facilitation information, the description including a screenshot request;

a request that missing resolution facilitation information be obtained when signed into a product;

a description of missing resolution facilitation information; or

a guide to collecting missing resolution facilitation information.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 5, 2023
From: GROENEWEGEN, PETER; MIHAYLOV, NIKOLA MINKOV; COX, LARISSA MARIE; MULLEN, NICHOLAS TAYLOR; WILSON-THOMAS, MARK ALISTAIR; CHAPMAN, PAUL; BAFNA, KSHAMA GAJRAJ; KUMAR, ABHISHEK; CHLUS, JASON; MITCHELL, HOLLY
To: MICROSOFT TECHNOLOGY LICENSING, LLC
Reel/Frame 064800/0726 →
Continuity (1)
Related Publication 20250077487A1 · Mar 6, 2025
References Cited (34)
US 6741959B1 · Kaiser · 2004 [cited by examiner]
US 10938678B2 · Ghosh · 2021 [cited by examiner]
US 20150006519A1 · Jain · 2015 [cited by examiner]
US 20180121808A1 · Ramakrishna et al. · 2018 [cited by applicant]
US 20180275986A1 · Ghosh et al. · 2018 [cited by applicant]
US 20190073293A1 · Sharma · 2019 [cited by examiner]
US 20190318204A1 · Mishra · 2019 [cited by examiner]
US 20200065151A1 · Ghosh · 2020 [cited by examiner]
US 20200151583A1 · Mueller · 2020 [cited by examiner]
US 20200304364A1 · Tapia et al. · 2020 [cited by applicant]
US 20210157985A1 · Rotkop · 2021 [cited by examiner]
US 20210158146A1 · Singh · 2021 [cited by examiner]
US 20210166081A1 · Storey · 2021 [cited by examiner]
US 20210328888A1 · Rath · 2021 [cited by examiner]
US 20220036370A1 · Rodman · 2022 [cited by examiner]
US 20220215328A1 · Chen · 2022 [cited by examiner]
US 20230100605A1 · Singh · 2023 [cited by examiner]
CN 103246603A · 2013 [cited by applicant]
CN 102629230B · 2015 [cited by applicant]
CN 113721960A · 2021 [cited by applicant]
CN 115357288A · 2022 [cited by applicant]
EP 4107622A1 · 2022 [cited by applicant]
WO 2017041372A1 · 2017 [cited by applicant]
Ahsan, et al., “Automatic Software Bug Triage System (BTS) Based on Latent Semantic Indexing and Support Vector Machine”, In Proceedings of Fourth International Conference on Software Engineering Advances, Sep. 20, 2009… [cited by applicant]
Eriksson, et al., “NLP-Assisted Workflow Improving Bug Ticket Handling”, In Thesis of School of Electrical Engineering and Computer Science, Sep. 6, 2021, 17 Pages. [cited by applicant]
Liu, et al., “Ticket-BERT: Labeling Incident Management Tickets with Language Models”, In Repository of arXiv preprint arXiv:2307.00108, Retrieved Date: Apr. 4, 2023, pp. 1-12. [cited by applicant]
Mishra, et al., “Automatic Title Generation for Text with Pre-trained Transformer Language Model”, In Proceedings of IEEE 15th International Conference on Semantic Computing, Jan. 27, 2021, pp. 17-24. [cited by applicant]
Sobania, et al., “An Analysis of the Automatic Bug Fixing Performance of ChatGPT”, In Repository of arXiv:2301.08653v1, Jan. 20, 2023, 8 Pages. [cited by applicant]
“Automatic summarization”, retrieved from << https://en.wikipedia.org/wiki/Automatic_summarization >>, Jul. 23, 2023, 15 pages. [cited by applicant]
“Content similarity detection”, retrieved from << https://en.wikipedia.org/wiki/Content_similarity_detection >>, Jul. 24, 2023, 12 pages. [cited by applicant]
“Sentiment analysis”, retrieved from << https://en.wikipedia.org/wiki/Sentiment_analysis >>, Jul. 22, 2023, 16 pages. [cited by applicant]
“Large language model”, retrieved from << https://en.wikipedia.org/wiki/Large_language_model >>, Jul. 31, 2023, 21 pages. [cited by applicant]
“User intent”, retrieved from << https://en.wikipedia.org/wiki/User_intent >>, May 17, 2023, 3 pages. [cited by applicant]
McKay Christensen, “How to Write an Effective Bug Report That Actually Gets Resolved (and Why Everyone Should)”, retrieved from << https://www.lucidchart.com/blog/how-to-write-an-effective-bug-report-that-actually-gets-… [cited by applicant]