Look up work to do


We are planning to use scroll versions for our technical documentation. We have to maintain documentation for multiple releases and multiple languages.

When we start with a new version of the documentation for a new release, we want to start from an existing version, and modify the appropriate pages (of the features which have been changed).

What is the best approach to manage 'this page still needs to be translated', or "this page still needs to be reviewed'.

A basic documentation set (one release, one language) contains about 160 pages.
Could we use the workbox in combination with scroll versions ?


1 answer

1 accepted

0 votes
Answer accepted

Hi Francis,

I've created a feature request for the integration of the workbox in Scroll Versions: https://k15t.jira.com/browse/VSN-456

Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, to comment or to vote for this issue.

FYI: At K15t, we are using labels (in combination with the content-by-label macro) and "@-mentions" as workaround to manage the workflow. Maybe this works for you too.



The problem with labels is that these are free for users to create.

How about @-mentions in combinations with workbox? This is just a workaround, but we plan to have a better integration with the workbox in the future.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


278 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you