We manage our change documentation using the macro revision history page as described below.
The user publishes the change only at the first creation. At the final editing of the page, the user chooses the option "publish with a comment". then added the related issue change key as a comment to the documentation page.
In this way, we can know for each change documentation what is the related issue change.
Unfortunately, this workflow didn't work successfully. Some users choose the “publish” option every time they edit the page.
Besides, we tried the add-on scroll documents, but it seems not clear enough for managing the changes.
Do you have any suggestions/recommendations on how we can control the change documentation versions?
I will appreciate your help!
Would it be right in assuming that you would like to save versions of pages on demand and not every time some one edits and publishes the page?
If yes, then this is one of the main use cases that Scroll Documents supports and we’re sorry to hear you had some trouble with this workflow in the app.
We’d be happy to chat with you and help get the workflow set up in a clear way for your team. If you’re willing to give the app another try, just reach out to email@example.com and we can advise on the setup from there.
Hello Confluence Community! What if i told you that you could have a healthier life and be 100% meet-less? This month, we're promoting a healthy, balanced work diet with Confluence. We la...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events