Knowledge Base Article Versioning and Version Picker

[Kyle Ouellette]

Atlassian documentation has a version picker to easily switch to the documentation pertaining to the specific version of the product. Is there a way to include a similar version selector to our JSM knowledge base? We support multiple versions of our product but currently, there doesn't seem to be a way to integrate this into our KB articles. It would be nice if users could search for articles via the help center or project-specific portals and then be able to select the version of the page they'd like to view based on the version of the tool they are running.

I know there are plugins such as Scroll Documents, however, it's not clear if this would work in the context of a JSM knowledge base.

Are there other solutions or recommendations for implementing a similar behavior into our KB articles? 

[David _K15t_]

Hi Kyle,

this is David from K15t, we're the team behind both Scroll Documents, which you mentioned, and Scroll Versions and Scroll Viewport, which Atlassian is using in the screenshot you shared.

From the tags in this post, I'll assume you're using Atlassian Cloud. Using the JSM <> Confluence integration, the customization is very limited and a version picker is not something we as app developers can include into the KB article view as of now.

Using Scroll Documents returns the version number in the page title:

In the near-term future, we're looking into possibilities to add a macro that renders links to other versions of the page, which would be technically part of the page content and thus should be visible and usable in the KB article view in JSM.

You can track the issue here: https://k15t.jira.com/browse/DOCS-136

Cheers,

David

[Kyle Ouellette]

Hi David,

Thanks for taking the time to answer. Yes, your assumptions are correct about Atlassian Cloud and the JSM and Confluence integration. Having scroll documents return the pages with their version certainly seems a step closer to what we'd like.

We got feedback from our customers that navigating the KB with the search functionality was difficult so we now use categories that features an article with the table of contents of the KB so they can see what articles are available and follow the links. What would this look like if we were to use scroll documents for versioning? Would it be possible to add articles to a category and target a specific version (e.g. (1.0) ToC, (2.0) ToC, etc.)? Ideally, our customers could view the ToC pertaining to a single release and following links rather than searching for an article and then having to choose the version that is associated with what they're using. 

We will most likely request a demo for scroll documents and my questions may be answered just by poking around at it, but I figure it doesn't hurt to ask the source!

Thanks,
Kyle