Anonymously closing JIRA issues

We run a script that analyzes commit messages and closes tickets. It uses JIRA'sREST API to do so. Since it needs to login somehow, it uses the "anonymous" user.
Not sure we can do something about it. Probably not through the REST API.
In crucible, for creating the review request, the plugin can do it through an instanceof the "ImpersonationService" class.
Lukas
On Fri, May 27, 2011 at 16:04, Gilles Dubochet <gilles.dubochet@epfl.ch> wrote:

Hello Scalions.
I noted that issue SI-4642 is marked as having been closed by user "anonymous", although I think it was fixed by Paul. Is Paul's user name "anonymous"? Or is JIRA configured to allow unlogged users to close issues? In the latter case, I think it should be disallowed. This doesn't seem like something we want anyone to be able to do. Also, it makes understanding the history of an issue much harder.
Cheers,Gilles.

On 5/27/11 7:04 AM, Gilles Dubochet wrote:
> I noted that issue SI-4642
> is marked as having been
> closed by user "anonymous", although I think it was fixed by Paul. Is
> Paul's user name "anonymous"? Or is JIRA configured to allow unlogged
> users to close issues? In the latter case, I think it should be
> disallowed. This doesn't seem like something we want anyone to be able
> to do. Also, it makes understanding the history of an issue much harder.

Yes, I wanted to bring this up too. It's the auto-close script,
reacting to my commit message. The script is a godsend: I am guessing
it just needs a little tweak to properly supply the identity of the closer.

(I don't think actual anonymous persons can run around closing issues,
though I could be wrong.)

I would guess that the commit action triggered a script that does this, that's why it says it's anonymous.

Alex

On 27/05/11 16:04, Gilles Dubochet wrote:

Hello Scalions.
I noted that issue SI-4642 is marked as having been closed by user "anonymous", although I think it was fixed by Paul. Is Paul's user name "anonymous"? Or is JIRA configured to allow unlogged users to close issues? In the latter case, I think it should be disallowed. This doesn't seem like something we want anyone to be able to do. Also, it makes understanding the history of an issue much harder.
Cheers, Gilles.

I think we need to create a dedicated service user for each script that's able to take action in Jira like this, so it's more obvious exactly what's going on.


On 27 May 2011 15:20, Aleksandar Prokopec <aleksandar.prokopec@epfl.ch> wrote:

I would guess that the commit action triggered a script that does this, that's why it says it's anonymous.

Alex

On 27/05/11 16:04, Gilles Dubochet wrote:

Hello Scalions.
I noted that issue SI-4642 is marked as having been closed by user "anonymous", although I think it was fixed by Paul. Is Paul's user name "anonymous"? Or is JIRA configured to allow unlogged users to close issues? In the latter case, I think it should be disallowed. This doesn't seem like something we want anyone to be able to do. Also, it makes understanding the history of an issue much harder.
Cheers, Gilles.

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra

In crucible, for creating the review request, the plugin can do it through an instanceof the "ImpersonationService" class.

And I guess there is no ImpersonationService in JIRA?
Kevin's idea of running a "personal" script for each Scala commiter may be a solution, albeit not very elegant. Lukas, is this doable?
Cheers,Gilles.

On Fri, May 27, 2011 at 16:49, Gilles Dubochet <gilles.dubochet@epfl.ch> wrote:

In crucible, for creating the review request, the plugin can do it through an instance of the "ImpersonationService" class.

That I don't know, but I know it's not exposed via REST. If it exists, we couldwrite a JIRA plugin instead of the current script, that should be doable.  

And I guess there is no ImpersonationService in JIRA?
Kevin's idea of running a "personal" script for each Scala commiter may be a solution, albeit not very elegant. Lukas, is this doable?

To login via REST you need the password, so this won't work. I think what Kevin meant was having a different username than "anonymous", something like"review-commenter-script".
Lukas

On 27 May 2011 15:55, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

On Fri, May 27, 2011 at 16:49, Gilles Dubochet <gilles.dubochet@epfl.ch> wrote:

In crucible, for creating the review request, the plugin can do it through an instance of the "ImpersonationService" class.

That I don't know, but I know it's not exposed via REST. If it exists, we couldwrite a JIRA plugin instead of the current script, that should be doable.  

And I guess there is no ImpersonationService in JIRA?
Kevin's idea of running a "personal" script for each Scala commiter may be a solution, albeit not very elegant. Lukas, is this doable?

To login via REST you need the password, so this won't work. I think what Kevin meant was having a different username than "anonymous", something like"review-commenter-script".

Exactly.
and if other scripts should be introduced into the mix, then we'd create a separate user for each of them.

 

Lukas

--
Kevin Wright

On Fri, May 27, 2011 at 4:55 PM, Lukas Rytz <lukas.rytz@epfl.ch> wrote:

On Fri, May 27, 2011 at 16:49, Gilles Dubochet <gilles.dubochet@epfl.ch> wrote:

In crucible, for creating the review request, the plugin can do it through an instance of the "ImpersonationService" class.

That I don't know, but I know it's not exposed via REST. If it exists, we couldwrite a JIRA plugin instead of the current script, that should be doable.

Maybe we should look at SOAP then. :) Maybe this could be used directly..
http://stackoverflow.com/questions/1501853/jira-code-validation-commit-hook-for-git  

 

And I guess there is no ImpersonationService in JIRA?
Kevin's idea of running a "personal" script for each Scala commiter may be a solution, albeit not very elegant. Lukas, is this doable?

To login via REST you need the password, so this won't work. I think what Kevin meant was having a different username than "anonymous", something like"review-commenter-script".
Lukas