Scroll Versions - set prior version to READ ONLY
Take the scenario we have a software version 1.0 and have documentation for it. Now we come out with 2.0 and have new docs for it based off of 1.0. My doc authors have 1.0 in their version drop down. I as the admin go in and add 2.0 as the new version and set 1.0 to be hidden.
The problem is that all the doc authors still have 1.0 selected in their drop down and can still make edits to 1.0 documentation. They may accidentally write 2.0 information into the 1.0 doc version because they forgot to change the version selector.
Solutions:
- When a prior version is hidden the drop down version selector should automatically change to the next version
- Allow admins to mark a version as read only preventing any changes from this point forward (this is the preferred solution)
We need a way to help our doc authors from wasting time and making mistakes and version management is the biggest problem in the current UI.
-
Hi Neal, thanks for you proposed solutions.
We are aware that a user's context should be switched to a non-hidden version. This is a bug as this doesn't actually happen: https://k15t.jira.com/browse/VSN-3557. I will mention this Jira issue during the next team's sprint planing.
Please sign up at https://k15t.jira.com/secure/Signup!default.jspa to watch, comment on or vote for this issue. We'll then send a notification for every status update.
Feel free to add a comment to the Jira issue above to add more traction for this fix of the behaviour.
Cheers,
Roman. -
Hi,
are there any news on this topic?
We´re also running into issues when an author uses an "old" link which points to a meanwhile hidden versioned page.
It may happen that an author edits a preceding version, which is already delivered and "closed".
RED background in the version picker would be sufficient in the first step.
However, an option to manually set a version as "read-only" would be much better.
Best regards,
Christian
Please sign in to leave a comment.
Comments
3 comments