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
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
I noticed we can edit the comments created by other team members, making it look like it was their comment in the first place. This can be very misleading, how can we prevent this?
I just did this to add a searchable hashtag to a comment and Jira is pretending the user themself did the edit.
This is a huge bug in my opinion. Basically Jira is lying about who did something and that makes me think what else is it lying about and can I trust it about anything.
Another example: Cloning a ticket will clone the reporter field, making it appear that the original creater also did the cloning of the new ticket. If the reply to this is "oF cOuRsE, It'S a ClOnE!!!", that kind of proves my point that bugs are often ignored by atlassian and they put the onus on the user for "using the software wrong".
Where in the code did things go so wrong that you can pretend to be another user just by touching their existing stuff?
There is a usefulness in editing anothers comment, but all that usefulness goes out the window if the software can't track who made the edit. This is one of those things that could result in people being fired or worse, and I could see this as a huge lawsuit if any big company did a huge layoff based on Jira comments.
Jira is issue and project tracking software, so what are we all paying for here if it can't do that correctly?
Josh is correct, only space admins can edit other people's comments: Edit Comments Permission in Confluence
Could you let me know more details of your use case so I can see if the dev team will let me open a suggestion to change the way the permissions work?
For example, if you could let me know a case where you may need to give space admin permissions (so the person could control permissions or...?) but you would not want that admin to be able to edit other people's comments.
My ideal would be jira-style permission schemes that have pretty granular permissions. "edit own comments," "edit all comments," etc. But I know that is complicated for newer admins.
I'm just in favor of more granular permissions in general. I have people who are space admins just so that they can create/manage user templates, or to use the page reordering (drag and drop) but they ideally wouldn't have the ability to alter permissions.
Getting off topic but it would also be helpful if I could standardize default permissions across sets of related spaces. Like if a permission scheme was shared with multiple jira projects. Feel free to ask me offline Ann if you would like to discuss.
After testing one more time, you are correct. However a user still has the "edit" option present and when they try to edit a comment the submission window simply spins. It would be a little bit more straight-forward to remove the "edit" option completely from users who are not able to edit comments posted by others.
Also, is it possible to prevent space admins from editing the comments of other space admins? Allowing a space admin "John" to edit the comment of another space admin "Joe", resulting in misleading information. Is there change history for comments, similar to pages?