Its more that we dont allow non-privileged users to edit the issue itself. I am pretty sure a user can edit their own comment.
Anyway, I heard back from Atlassian. Sadly, this seems to be intermittent and they are having trouble isolating the cause :( I had pointed them here for additional details. Initially they were seeing the permissions issue, but then:
{quote}
In the middle of the investigation, we were puzzled that all of sudden we could not reproduce this problem anymore. In other words, we could not identify the root cause of this problem.
{quote}
I have asked them what we need to do the next time this happens to finally get this resolved.
For my reference later: https://support.atlassian.com/browse/JST-89193
P.S. Has anyone played with the permissions in the meantime? Maybe that would explain the change?
|
