It'd be great if I could re-arrange the order of the articles in the Knowledge Base.

Anyone who provide a service in multi language needs to have a multi language Knowledge Base.

Today Uservoice offers you the ability to have KB in a plenty of languages. But you can only choose ONE language.

I provide a service in Brazilian Portuguese and English. I want to have a Knowledge base in english and another one in Brazilian Portuguese.

I build my own KB with this multilanguage feature in just a week: support.flashping.com and suporte.flashping.com

But this do not compares with having this feature built-in uservoice.

If you have a multilanguage website, vote on this.

Be able to select which knowledge base articles show up in the in the widget. Right now there is no way to select which articles show up as the default articles in the widget.

We currently have all of our documentation in the form of PDFs. It would be a huge PLUS if we could attach files (other than CSVs) to Knowledge Base articles.

Some articles are closely related to other articles. I would like to be able to link from one to the other wiki-style.

I would like to associate an article with more than one "category" and I would like the option to open the widget directly into a "category" via a script

Hi !

If you have different communities, it would be great to add language support for helpdesk.

So I can create a topic 'Library' which could be translated to 'Bibliothèque' in French.

So french users will arrive to the french helpdesk and english users to the English helpdesk.

Right now I can't have 2 helpdesks in separate languages right ?

To really be able to satisfy all our customers that come from the whole world we also have to answer their support request in different languages. Right now all the resulting articles in the different languages just end up in the same big messy knowledge base, which is really confusing to our customers.

So here's our proposition: enable adding articles to different, freely choosable knowledge bases

Ability to sub-categorize Hepldesk Topics

It seems silly that I have to use an external service to host my images when I want to embed them in a knowledge base article. It's a whole extra step that I have to train my customer support reps to do in order to create articles. I'm also worried about having broken links if any of these services, for whatever reason, take down my photos. That would have a material effect on my customers' support experience.

Tenderapp has a really great solution for this. I'm puzzled that this doesn't already exist here.

Knowledge Base articles should have a "Share" button (on Facebook, Twitter, etc).

So if I read an article and find it useful I can share it with my people and contribute to product visibility, awareness, etc.

Thanks

Each knowledge base article has a category, but it can only be seen in "edit" mode. Please indicate an article's category when it's in preview mode (in the right pane of the admin panel).

Please add this category information to the header when it's being previewed in the admin panel.

See screenshot. If the ability to sub-categorize Helpdesk topics is created (http://feedback.uservoice.com/forums/1-general-feedback/suggestions/2315221-sub-categorize-hepldesk-topics) it would be nice to be able to organize them via a drag'n'drop view.

So that users in different languages can be guided to the knowledge base in their respective language

When creating a new help desk article UserVoice should automatically save every 10 or 20 seconds so admins don't loose any work if something goes wrong!

Allow users to subscribe to knowledge base articles so they can be automatically updated when the article changes such as a resolution to problem has been released.

Currently, KB articles are global; however, forums are often used for different products and different products will normally have different KB articles. So, KB articles should really be per forum instead of global.

There are many cases where more than one title worded completely different can point to the same solution. Why can't we have more than one title per article? Or even tag support so they show up in search?