When viewing history for a edited page, I keep seeing edits that aren't edits, they are normally url links, so i get 50 edits when there are only actually 3
Hi Ryan,
I could reproduce this on a test page. Confluence saves a new version when a link’s display changes, even if the text stays the same. For example, switching a URL between URL, Inline and Card does this. In the version history with “Highlight changes” on, the same URL shows struck out and added back right next to it. The edit counter counts that as 2 edits. A page with a lot of links can collect many of these “edits” that aren’t real content changes.
Other things that create versions without visible changes:
Two questions:
Hey, thank you for the rapid response.
And for replicating. It's a normal page.
I see this:
v16
v17
both are
Thanks Ryan, that helps. I tried it with links to other Confluence pages inside a table. I changed only one sentence under the table, and the version history still highlighted two of the page links in green, just like in your v17. The counter said 3 edits instead of 1. I checked the page source of both versions and those links are exactly the same, so nothing was actually edited. It looks like the same issue you’re seeing.
Atlassian already has bugs for this behavior with other elements in the new version history. Unchanged content gets flagged as changed and adds to the edit count:
Thank you! Ok that's good, those are definitely related, though one is closed but they are still issues. Is it worth a ticket for this specific case?
Thanks for the quick insight 🙏🏻
@Ryan Lee you can always submit a support ticket to Atlassian to ensure that they are aware of the issue. If you look at their know bugs / issues there are several outstanding around page history. One thing to consider is if you are using live docs then you will always have more than standard pages. I believe you mentioned above that you had standard pages. One thing you should look at is if it is happening on all pages or just the one using the link macro before submitting a support issue to Atlassian.
Hi @Ryan Lee
Just one thing to clarify. 🙂
CONFCLOUD-85162 was closed as a duplicate of CONFCLOUD-84445, not because the issue was in fact fixed.
https://jira.atlassian.com/browse/CONFCLOUD-84445
I'm down with Brant's suggestion that you can open a support ticket. include your screenshots and reference both of the JAC issues so Support can link your case to the existing investigation.
Cheers,
Arek🤠🧙♂️
Thanks chaps, will try to raise.
And pointing out the duplication.
Cheers.
I can raise a support ticket, i'm not admin…
It appears, and it's too long to go through whoever my admin is; hopefully they fix it soon.
It looks like you're new here. Sign in or register to get started.