There's always a few edge cases, but as a general rule, a tracker should log who commented and not allow it to be changed (Jira has a weakness in that it considers the reporter to be the person who logs an issue, and then lets people change that. Reporter != Creator)
Well, kinda. We have "Anonymous" user to create Tickets. Occasionally, someone will get his own account. Now it would be great to associate this comment to the user. Or someone is abroad or forgot to sign in, so he is creating an "Anonymous Comment" which I'd like to change to the users comment (which is not destroying accurate data because this has not been accurate at that time :) )
Ah, mm, my argument there would be that you shouldn't be allowing that at all. I have spent most of my career in heavily controlled area where it's frankly illegal to not know who is making changes to your systems. So anonymous access in most cases is read-only.
Yea, understood. But our JIRA is running inside our own Intranet, so kinda secure anyway. And because I cannot get a license for all our 55000 Employees we set certain Projects to "Anonymous" to have some possibilities. So we do have to allow that. I mean, why else would there be the option for that at all when it should not be done? Because sometimes it is necessary :)
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs