Inspiration
What it does
How we built it
Challenges we ran into
Accomplishments that we're proud of
What we learned
What's next for Asked Before
Inspiration
Every support team answers the same questions every week: sync errors after a change, guest Wi-Fi, new-hire setup. The best answer is almost always sitting in a request someone resolved last month, but agents don't have time to search for it, so they write it again from scratch, a little worse each time, and customers wait longer. Search finds old requests; it doesn't tell you which of their many comments actually solved the problem.
What it does
Asked Before puts the team's earlier answers on the request, the moment an agent opens it.
- Asked before? It compares the new request with up to 300 resolved requests in the same project and shows how many times it was asked before and the median time those took to resolve.
- The reply that solved it. For each similar request it picks the reply that actually fixed the problem, not the agent's first question, the customer's own messages or the final "thanks, closing this". It shows who wrote it and how long that request took.
- Behind-the-scenes context. "Show full answer" also reveals the last internal note on that request (what the team did behind the scenes), for agents only.
- Use this answer. One click turns the reply into a draft for the new requester: greeting adapted to their name, signature adapted to the current agent, fully editable.
- Send or save. Send to customer posts it as a public reply; Save as internal note keeps it private. Nothing is sent until a person presses the button. Every reuse is logged and counted per project.
- Rovo agent "Asked Before": "Has this been asked before?", "What do people ask most in ITS?" (a ready list of knowledge-base candidates) and "What did we reuse recently?". The same tools are exposed through MCP (
rovo:mcp) for external agents. - Atlassian Marketplace. Asked Before is submitted for listing as a free app (review ticket ECOHELP-185644). The judges' install link points to an identical unlisted copy ("Asked Before (Codegeist)"), because a Marketplace-submitted app can no longer be shared by link.
How we built it
- Forge only, Runs on Atlassian: no egress, no remote backend, no external model. Modules:
jira:issuePanel(UI Kit),rovo:agent,rovo:mcp, threeactionmodules, Forge KVS for the reuse log. - Jira Service Management APIs read request comments with their public/internal visibility (
/rest/servicedeskapi/request/{key}/comment) and post the reply or internal note; regular Jira projects fall back to normal comments. - Similarity is a small pure module: TF-IDF cosine over summary (double weight) and description with stop words, light stemming and a support-desk synonym table (wi-fi/wireless/network, laptop/notebook/computer, hire/starter/onboarding, set up/setup).
- Picking the solving reply is a scored heuristic (
src/answer.js, unit-tested on 100 real resolved requests from the demo site): public, not by the requester, long enough to carry an answer, rewarded for instruction and resolution phrases ("we reset", "should now", "restart"), penalised for progress notes ("I'm going to check", "could you share") and short closings. Smart quotes are handled, because real agents type them. - Only the top matches have their comments fetched, so a lookup is a handful of calls.
Challenges we ran into
- Which comment is the answer? Real threads interleave questions, internal escalations, the fix and the thank-you. The first version picked "I'm going to check…" because the real fix began with "Thanks for waiting"; the scoring now separates progress notes from fixes and only penalises closings when they are short. The tests pin those cases.
- Branding rules. The app started as "Answer Atlas"; the Marketplace rejects names containing Atlassian product names, so it was renamed to Asked Before. (The Rovo chat header in the video still shows the old agent name, which Rovo had cached.)
- Link sharing vs Marketplace. Submitting for listing disables install links, so the judges get an identical unlisted copy.
Accomplishments that we're proud of
On the demo site's IT Support project it found the earlier answer for the new Dashloop sync request (asked four times before), produced a ready draft for the requester, and posted it in one click, with no setup at all.
What we learned
The value isn't in finding similar tickets, it's in picking the one comment that solved them. A transparent heuristic that agents can check beats a generated answer they have to trust.
What's next
- Turn the most repeated questions into knowledge-base articles with one click.
- Learn from agents' choices (which suggested answer they reused) to rank better per project.
- Suggest answers at request creation in the portal, before an agent even opens it.
Built With
- forge
- javascript
- jira
- jira-service-management
- mcp
- node.js
- rovo
- ui-kit