Re: [phpBT-dev] User Permission Levels

[Benjamin C. <php...@be...>]

Ulf Erikson wrote:
> * Benjamin Curtis [2005-02-15 15:06]:
> 
>> basically, users could change roles per bug, but they could have a
>> different set of permissions by virtue of their group memberships on a
>> more general basis (users in the QA group would always have CloseBug
>> permission, regardless of reporter/owner/witness role).
> 
> 
> Hmm.. I must have missed this earlier. Do you mean that you would like
> to difference EditStatus in permission to close a bug or not?
> 
> How about other enforcements on what Statuses and Resolutions one can
> chose depending on the current status? That would finally lead to
> something similar to the WorkFlow:
> http://sourceforge.net/tracker/index.php?func=detail&aid=648867&group_id=14939&atid=364939
> 
> 

You know, I'm not sure that I realized the full meaning of what I was
typing until your reply, but yeah, we certainly could do a permission
per status.  That would go quite a bit of the way towards workflow
customization.

> There are also requests on keeping comments and/or whole bugs restricted
> to people with the right permissions:
> http://sourceforge.net/tracker/index.php?func=detail&aid=626884&group_id=14939&atid=364939
> 
> 
>>> New user can set another reporter for bug
>>> http://sourceforge.net/tracker/index.php?func=detail&aid=1034495&group_id=14939&atid=114939
>>
>>
>>
>> This set another reporter bug is one that I'd really like to fix
>> before 1.0, but I haven't put enough thought yet into what is the best
>> approach.
> 
> 
> Do you mind if I suggest more blockers? ;-) The earlier security issue
> should probably be revisited once more, and considering the speed of
> development it would probably be a very good idea to make sure that both
> php5 and MySQL 4.1 are possible platforms for phpBugTracker 1.0.
> 

Heh, sure, more blockers are always fun.  Yes, the security issues need
to be reviewed again, and I can vote for PHP5 support.  I'm not sure
about MySQL 4.1, though, as I had some problems with it combined with
transaction support while trying to use adodb.  Of course, I probably
just didn't spend enough time on it to nail down the exact problem. :)