You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Mike Edwards <mi...@gmail.com> on 2006/01/16 17:23:59 UTC
JIRA: How to get priviledges to enable updating status of Issues
Hi,
I've got a JIRA ID (edwardsmj) but this is just at regular jira-user
priviledge level. How can I get my ID to have the priviledges to enable
me to update / assign issues, please?
Yours, Mike.
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Mike Edwards <mi...@gmail.com>.
This sounds good to me.
Yours, Mike.
Jeremy Boynes wrote:
> On 1/31/06, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
>>Yes, we shouldn't allow anonymous users to raise issues, we got the same
>>recommendation from Paul who ran into problems with this in the Synapse
>>project, but logged on users should be able to work with the issues they
>>create.
>>
>>Do the other people in the group agree? Jeremy is there a way to
>>configure JIRA to work in this mode?
>
>
> Right now any authenticated user can create issues, add comments or
> add attachments. Workflow tasks (like closing issues) can be done by
> anyone in the "tuscany-developers" group; the original proposal was to
> open this to active contributors not just committers which would
> address many of the scenarios listed. This is fairly typical.
>
> JIRA does have the concept of a "Reporter" role which would allow
> users to close/edit/link their own issues; we can grant that if
> desired.
>
> --
> Jeremy
>
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Jeremy Boynes <jb...@gmail.com>.
On 1/31/06, Jean-Sebastien Delfino <js...@apache.org> wrote:
> Yes, we shouldn't allow anonymous users to raise issues, we got the same
> recommendation from Paul who ran into problems with this in the Synapse
> project, but logged on users should be able to work with the issues they
> create.
>
> Do the other people in the group agree? Jeremy is there a way to
> configure JIRA to work in this mode?
Right now any authenticated user can create issues, add comments or
add attachments. Workflow tasks (like closing issues) can be done by
anyone in the "tuscany-developers" group; the original proposal was to
open this to active contributors not just committers which would
address many of the scenarios listed. This is fairly typical.
JIRA does have the concept of a "Reporter" role which would allow
users to close/edit/link their own issues; we can grant that if
desired.
--
Jeremy
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Mike Edwards wrote:
> I suppose this would mean that any authenticated contributor could
> raise , assign, modify and close issues. I suppose this isn't really
> a problem - as long as the person doing the changes is known and
> recorded. It is probably better to allow this than to burden the
> committers with the chore of keeping the JIRA list clean.
>
>
> Yours, Mike.
>
> Jean-Sebastien Delfino wrote:
>
>>
>> I agree that only committers can resolve issues as fixed (since only
>> committers can check-in fixes).
>>
>> Now what about the following cases:
>> - I want to cancel an issue that I created by mistake
>> - I opened an issue yesterday, and just found that it's fixed today (by
>> a change tracked under another issue, or by a change that doesn't
>> correspond to a JIRA issue at all)
>> - I opened an issue, and the nature of the issue has changed, I want to
>> add more info to it, maybe assign it to a different JIRA component
>> - I opened an issue, somebody contributed a fix for it, a committer
>> committed the fix, but I'm the only one who can verify that the fix
>> effectively solves the issue (because I'm the only one with the
>> environment to reproduce the problem for example), so I want to test the
>> fix myself and only then allow the issue to be marked resolved.
>>
>> Do I have to be a committer to do all of this? or should other
>> contributors/testers be allowed to participate in the resolution of the
>> issues in these cases?
>>
>> Any thoughts?
>>
>> --
>> Jean-Sebastien
>>
>
Yes, we shouldn't allow anonymous users to raise issues, we got the same
recommendation from Paul who ran into problems with this in the Synapse
project, but logged on users should be able to work with the issues they
create.
Do the other people in the group agree? Jeremy is there a way to
configure JIRA to work in this mode?
--
Jean-Sebastien
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Mike Edwards <mi...@gmail.com>.
I suppose this would mean that any authenticated contributor could raise
, assign, modify and close issues. I suppose this isn't really a
problem - as long as the person doing the changes is known and recorded.
It is probably better to allow this than to burden the committers with
the chore of keeping the JIRA list clean.
Yours, Mike.
Jean-Sebastien Delfino wrote:
>
> I agree that only committers can resolve issues as fixed (since only
> committers can check-in fixes).
>
> Now what about the following cases:
> - I want to cancel an issue that I created by mistake
> - I opened an issue yesterday, and just found that it's fixed today (by
> a change tracked under another issue, or by a change that doesn't
> correspond to a JIRA issue at all)
> - I opened an issue, and the nature of the issue has changed, I want to
> add more info to it, maybe assign it to a different JIRA component
> - I opened an issue, somebody contributed a fix for it, a committer
> committed the fix, but I'm the only one who can verify that the fix
> effectively solves the issue (because I'm the only one with the
> environment to reproduce the problem for example), so I want to test the
> fix myself and only then allow the issue to be marked resolved.
>
> Do I have to be a committer to do all of this? or should other
> contributors/testers be allowed to participate in the resolution of the
> issues in these cases?
>
> Any thoughts?
>
> --
> Jean-Sebastien
>
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Mike Edwards wrote:
> Folks,
>
> Regarding the issue of who should be given privileges on JIRA, it
> seems to me that all Tuscany committers should be given the privileges
> to assign, modify and close issues.
>
> Regarding the status of developers who are contributing but who are
> not committers, I think that if they cannot actually commit the code
> into the codebase, it is hard to see how they can resolve issues -
> they can build solutions to problems, but ultimately a committer must
> put the code into the codebase - and update issues at the same time.
>
> "jira admins" with full privileges should be a very limited group, but
> should be more than 1 person.
>
>
> Yours, Mike.
>
I agree that only committers can resolve issues as fixed (since only
committers can check-in fixes).
Now what about the following cases:
- I want to cancel an issue that I created by mistake
- I opened an issue yesterday, and just found that it's fixed today (by
a change tracked under another issue, or by a change that doesn't
correspond to a JIRA issue at all)
- I opened an issue, and the nature of the issue has changed, I want to
add more info to it, maybe assign it to a different JIRA component
- I opened an issue, somebody contributed a fix for it, a committer
committed the fix, but I'm the only one who can verify that the fix
effectively solves the issue (because I'm the only one with the
environment to reproduce the problem for example), so I want to test the
fix myself and only then allow the issue to be marked resolved.
Do I have to be a committer to do all of this? or should other
contributors/testers be allowed to participate in the resolution of the
issues in these cases?
Any thoughts?
--
Jean-Sebastien
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Mike Edwards <mi...@gmail.com>.
Folks,
Regarding the issue of who should be given privileges on JIRA, it seems
to me that all Tuscany committers should be given the privileges to
assign, modify and close issues.
Regarding the status of developers who are contributing but who are not
committers, I think that if they cannot actually commit the code into
the codebase, it is hard to see how they can resolve issues - they can
build solutions to problems, but ultimately a committer must put the
code into the codebase - and update issues at the same time.
"jira admins" with full privileges should be a very limited group, but
should be more than 1 person.
Yours, Mike.
Re: JIRA: How to get priviledges to enable updating status of Issues
Posted by Jeremy Boynes <jb...@apache.org>.
Mike Edwards wrote:
> Hi,
>
> I've got a JIRA ID (edwardsmj) but this is just at regular jira-user
> priviledge level. How can I get my ID to have the priviledges to enable
> me to update / assign issues, please?
>
> Yours, Mike.
I added you to tuscany-developers so you should able to do this now.
When we should grant this type of access was part of a previous thread
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200601.mbox/%3c43C34CC5.5030308@apache.org%3e
that we didn't resolve.
--
Jeremy