Hi all,
I have an admin of a project that just realize he can accidentally create releases. Now it has been requested of me to try and find "How" he created the release. The only ways I know of are to go into versions and add the release or go into a version field and type the release and click enter to add it.
Is there a way of searching the activity log from two weeks ago?
Is there another way to find out how this bogus release was created?
The audit log tells me who and when but not how.
Thanks,
Robert
People with the right to create versions can also create them when simply editing or creating an issue.
People with board admin rights on a Kanban board can also belt "release" to create a new one.
Hi Nic,
Right, and that's the problem he does not remember how he did it. It was solved by revoking his rights :-) I was wanted a way to find out which issue he did this for.
Thanks,
Robert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's a reasonably reliable way to work it out.
If the version is not on any issues, he did it from project -> versions.
If it's on one issue, it's almost certain that he did it by editing that issue.
If it's on lots of issues, it's the "release" on the Kanban board.
(I'm not 100% sure on the second and third because it is possible that he clicked "release" on a Kanban that only had one "done" issue)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Think the problem is that he did it to one issue and then changed it back, and we have like 7 version fields, so a JQL of any version field that was ever set to version xxx would be cool. Also a way to search all of activity log should work as I know exactly when he did it from the audit log. (Of course I am not 100% sure just editing an issue shows on the AL, so that may not work either). We are good though.
Thanks again Nic.
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.