You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As mentioned in the question, why the inline comments are - in some cases - resolved when revising a page? This happens randomly. In every case I have seen, the inline comments was resolved with following message:
Resolved because the text was deleted by XXX YYY yesterday at 7:15 AM
I found some bug reports from the past but I wasn't able to find any explanation why is this happening? I have a doubt that this might have something to do with inline comments added to a H1 heading but I can't be sure this is the case.
While this issue keeps existing, we need to enforce the usage of page comments instead of inline comments which is sad because the inline comments would be such a great tool for pointing out "things" from the documents.
Hi @Jussi Sarén
Perhaps User A adds inline comment 1 while in edit mode (without publishing) and User B also edits and published a new version of the page in the mean time?
No, this is not the case. I'm 100% sure about this.
What I know is that the pages contain a Table of contents macro. The user is adding a new H1 header to the page and then when publishing the page inline comment added to another H1 header is being resolved.
Don't ask why, but in this case the H1 headings are within a table cell.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.