Permissions are confounding....

[tcchau]

Hi all,

I find the permissions policy in Agilo a little strange, but perhaps
it's because I don't understand it well enough. Here's my situation:

I have a QA group. They should be able to access the Edit tab of a
ticket, so that they can change the ticket states and make other
necessary edits to a ticket.

However, they cannot do so unless I grant them AGILO_CREATE_XXXX
permission as well. For example, if I want them to be able to edit bug
type tickets, I need to grant them AGILO_CREATE_BUG. If I want them to
be able to edit story type tickets, I also need to grant them
AGILO_CREATE_STORY. While the former makes sense, the latter does not.

Any ideas how I can workaround this problem? I

Thanks,
Clinton

[Martin Häcker]

Hi Clinton,

> > I find the permissions policy in Agilo a little strange, but perhaps
> > it's because I don't understand it well enough. Here's my situation:
> >
> > I have a QA group. They should be able to access the Edit tab of a
> > ticket, so that they can change the ticket states and make other
> > necessary edits to a ticket.

Well, this is clearly not ideal, but the idea was that anyone who cannot
create the type should also not be able to edit it. (I.e. stories are
owned by the Product Owner and it is his duty to keep them groomed.)

> > However, they cannot do so unless I grant them AGILO_CREATE_XXXX
> > permission as well. For example, if I want them to be able to edit bug
> > type tickets, I need to grant them AGILO_CREATE_BUG. If I want them to
> > be able to edit story type tickets, I also need to grant them
> > AGILO_CREATE_STORY. While the former makes sense, the latter does not.
> >
> > Any ideas how I can workaround this problem? I

Well, you could always give them TICKET_ADMIN though I guess that is not
really the intention.

To ask further: what is your intention? Stories for example should be
closed by the PO when he has reviewed them in the sprint ending
presentation.

Sorry I couldn't be of much help.

Regards,
Martin