Articles from tickets and problems
Turn the solution of a resolved ticket or the workaround of a problem into a draft article, review it and publish it.
On this page
The best of the knowledge base comes from daily work: a ticket that was hard to solve or a problem the desk already knows how to work around. Elion helps you turn that solution into a draft article so that next time it's solved faster, or without a ticket.
In both cases the result is a draft: nothing is published on its own. A person reviews it, fixes it and publishes it.
From a resolved ticket
Elion reads the ticket and writes a draft with the problem, the cause and the solution.
Before you start
The ticket must be Resolved or Closed.
You need Operate in Knowledge, to be able to edit in the destination space, and your company's plan must include the Elion assistant.
Steps
Open the ticket and go to the Knowledge section of the side panel. It says "Save this solution so next time it solves itself."
Press Turn into an article.
Choose the Space where the draft will go.
Press Draft it.
While it works, the section says Elion is drafting the article…. You can move on to something else.
When it finishes, you'll see Draft ready. Review it and publish it when it's right. Press Open the draft.
Review the draft in the editor, fix it and press Publish (see Publish a page).
The step-by-step from the ticket record is in Use knowledge articles in a ticket.
You can also ask Elion in its panel, giving the ticket and the space key, for example: "Write an article with the solution of INC-000123 in the TI space". Elion asks you to confirm before requesting it. Read Elion assistant.
What the draft includes
The draft follows the shape of the Solución de error (error fix) template, written in general terms and not as the story of one case:
a clear title, which you can change;
Symptom: what the person with the problem sees;
Cause, if known;
Solution, as a list of numbered steps;
Notes, if there's anything else worth knowing.
Elion removes names, emails, phone numbers, RUT (tax IDs) and IP addresses from the ticket when writing.
Always review the draft before publishing it. Elion can make mistakes or let sensitive data slip through, and what you publish in a Portal or Public space will be read by people outside the team.
From a problem in known error
When a problem becomes a Known error, its workaround should be in Knowledge, so the desk applies it and people find it in the portal.
Before you start
The problem must be in Known error, or have the known error checkbox checked with its workaround written.
You need Operate in Knowledge.
Steps
Open the problem and go to the Known error article section of the side panel.
Press Create known error article.
Choose the Space. If there's a space with the key
TI, it's preselected.Check the Title. It comes as "Known error:" followed by the problem title.
Press Create draft.
You'll see Draft created: review it and publish it in Knowledge. Press the article link in the section to open the editor.
Review, fix and press Publish.
The draft is built with the data from the problem record: the symptom (the description), the workaround and, if already known, the root cause. Each problem has only one known error article. The details are in Known errors.
How they stay connected
On the ticket record, the Articles section shows the new article with the Created from this ticket tag.
On the problem record, the Known error article section shows the link to the article and its status.
On the article page, the Used in tickets row counts how many tickets it was linked to. Every time someone links it from a ticket, the number goes up.
Review pending drafts
A draft no one publishes doesn't help anyone. To find them:
In each space's tree, drafts appear dimmed and with the Draft tag.
When you open a page with unpublished changes you'll see There are unpublished changes by and the name of the person who made them, with the Review and publish button.
On the ticket record, the Articles section says Elion has the draft ready. with the Review and publish link.