Feature #164
add a knowledges database
| Status: | New | Start: | 03/10/2010 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | Patrick Guiran | % Done: | 0% |
|
| Category: | Visible | Spent time: | - | |
| Target version: | 0.9 | |||
Description
When a issue is solved with a patch (for example), we have to repeat how to apply the patch.
We need a "knowledges database" where we can put "process" :- a knowledge item = { id, tag, status, title, description}
- tag = varchar(50)
- status = activ / inactiv
- title = varchar(200)
- description = text
- an expert / manager can access to the list of knowledges
- an expert / manager can add / edit knowledges
- a manager can inactive a knowledge
- a customer / viewer can access individual knowledge page
- when an expert / manager put tag
- it puts the link to the individual knowledge page. the text of the link is "title" of the knowledge
- it check that the knowledge item exist, and warm the expert / manager if it doesn't exist
History
03/10/2010 04:56 PM - Michel Loiseleur
I like this feature. But I don't understand what's a tag is doing here ? There's already a tag system, BTW.
03/11/2010 10:04 AM - Patrick Guiran
Why add a tag system with knowledge database ?
When you want to link a issue to an other, you put a #1234 in the description of a comment.
You don't go to the issue 1234, copy the link from your browser, go back to you comment edition, write "#1234" and put a link on it with the tiny_mce fonctionnalities.
I want the same system with "knowledge".
If I put "??patch??" in a comment, it put a text "How to apply a patch" with a link to the knowledge item.
May be the "??tag??" syntax is not good. We can change it to "#<word>" for example.
03/11/2010 10:26 AM - Thibaut Deloffre
I agree with Patrick for tag feature like linked issues. It can be really useful to have a knowledge db. Expert and manager won't waste time anymore.
03/11/2010 10:45 AM - Michel Loiseleur
so, since "tag" means in the real world "keyword", I am ok for it but lateR. 0.8.2 comes first.