nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Versioning in Confluence with triggers ??

Celik Vedat

hi all,

is there any possibility to configure the versioning of pages in confluence? standard confluence versioning creates a new version if I change anything. For example if I add an point or just one word anywhere.

Do you know addons, plugins or other options to configure wheter a new version is created ONLY if defined templates, includes or text passages are changed?

Hope you understand what I am trying to solve :P

best,

vedat

Accepted answers

Nic Brough -Adaptavist-

No, "losing page revisions" is something Confluence is explicitly designed not to do. It versions every change, that's what it was built for.

All comments

Nic Brough -Adaptavist-

No, "losing page revisions" is something Confluence is explicitly designed not to do. It versions every change, that's what it was built for.

roman_l0djep

Hi @Celik Vedat.

you can create versions on a space-level with Scroll Versions. By the way, Atlassian uses Scroll Versions to manage and publish their product documentation.

Check out the comparison table between page revisions offered by vanilla Confluence and versions created with Scroll Versions here.

Does this help?

Cheers,
Roman.

Celik Vedat

i know this, maybe you understood me a little wrong. the problem i am trying to solve is following:

in order of accounting we have lets call it rules because my english is limited here . E.g. when an auditor checks our documentation you have to make transparent when changes were made within our relevant documentations. In my opinion the possibility of versioning in confluence is not transparent enough because you do not see wich changes where made without comparing versions. And if you have got 30 version after 5 years, how can you guarantee wich changes where made without e.g. descriping versions. I hope it's clear now what i am trying to explain

sure you can say you can provide this within your processes etc. but most people in my opinion do not care about processes or documentation guidelines

But I see that there is no standard confluence setting for this isn't it?

Nic Brough -Adaptavist-

No, I get it, you're trying to ignore "minor" edits. Confluence does not do that, it records a full and (hopefully) accurate log of all revisions. You might not need that, but to a lot of people, it really matters. To most of those who don't need it to be so strict, it also does not matter that there are loads of versions.

You need a secondary layer of versioning, which I'd think of as "publishing". I do a lot of stuff where I edit repeatedly while I think and plan, but the client only sees the stuff I publish. I may write 100 versions (which I need, so I can track actual change) goes to them as 2-4 versions.

I usually work in an environment where I don't need anything to do this (client facing stuff is separate to our internal Confluence) as do 60-90% of Confluence users, but when it needs that second layer, I start with K15t's stuff (and frankly, haven't needed to look any further)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

app

version