Translating a solved issue into a KB article
when an issue is closed and the resolution is known I would like to create a related Knowledge Base article (automatically?) by reusing some of the information as documented with the issue. Can anybody give me some advise how this process could look like? Is seperate KB management software desirable?
rbecker
· 1 |
|
Tuesday, March 3, 2009, 1:23:29 PM |
0
|
Hello, |
||||
|
0
|
First of all thanks for you reaction Harvey. Our customers (having a support account) are the intended audience for the KB articles. We will post KB articles and relate them to reported Gemini Bugs\Enhancement Requests\Change Requests requests if applicable. The intention is to post them on our support site (SharePoint based). We didn't decide untill now what format to use (HTML, Word, ...). Our intention is to organise the KB articles similar to the MicroSoft KB articles. Currently we're investigting the technical possibilities. We're using Gemini at the moment (max 5 users) to support our development process. The experience is very positive until now. A solution for the KB articles creation would give us an additional reason to buy Gemini licenses.
|
||||
|
0
|
Hi, Finally we have bought Gemini and established our Sharepoint knowledge base environment (Based on the Bamboo solutions Knowledge Base solution). Still trying to find out how the process should look like to create KB articles from "Closed" Gemini issues. Do you have an idea how the process could look like. Are you aware of any Gemini customer who has solved this already?
|
||||
|
0
|
Assuming that the deployed KB solution works on Sharepoint lists, then you could simply update the KB list nightly using closed issues from Gemini. This does mean custom code that pulls Gemini closed issues and places them inside the KB list. The Gemini API will be more than sufficient to do this - you just need to check with Bamboo if you can programmatically insert items into the KB list. |
||||
|