-
Suggestion
-
Resolution: Unresolved
-
None
-
17
-
7
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
When using Jira Service Management with Confluence, you can only create articles using the built-in "Troubleshooting" and "How-to" blueprints from Confluence. It'd be great to give customers the ability to control the templates more - for example, selecting which templates are shown, or selecting which global blueprints to use (not just the ones in the linked space).
Having this configuration on a per-service desk basis would also be helpful, and would give Agents more control over knowledge curation. As a workaround, it's possible to create articles using different Blueprints from the Sidebar - so having this on the ticket would make life easier for Agents.
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
- links to
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-460] Customizing Knowledge Base article types
According to me this is no suggestion, but a bug.
When I link Jira SM to a Confluence space that is not a KB-space, in which I made a template myself and promoted it, then in Jira, starting from the KB, I can choose to create a KB article. Then my self-made promoted template is suggested as only template.
When I start from an issue, and choose there to create a KB article, only troubleshooting and how-to are suggested – EVEN IF I disable these template in the Confluence space!
That's a bug according to me, not a suggestion-issue here.
Hi Atlassian, please do give us an update on this feature request. There is certainly a real use-case for this request, and regardless of the potential difficulty & cost implementing it I think I can speak for everyone who has voted that we would appreciate some form of response. Thanks.
This STILL isn't available after 8 years since the issue was created? Seriously Atlassian? I want to create Internal KBs with a look and feel that are much different than the standard How To or Troubleshooting template so the support staff knows they are not to be shared with customers but without the ability to modify/add CSS to an article and the fact that I can't create my own template, this is impossible.
I spent hours trying to figure out how to do this thinking that it must have just been somewhere in the maze of options. Glad I can at least give up on this.
This tool is very expensive but not very flexible. This call is now 7 years old!
Otherwise, authorize creators to add css to their articles or at least respect the css used on edition view (centered images, info bullets, etc...)
yes, please. make your customers happy...