To be allowed to assign bugs you must be member of a group
with the EditAssignment bit. The developers group does not
have this bit by default. (I don't think they had so in rc5
either)
Use the Groups page in the Administration Tools to edit your
Developer group and add the EditAssignment bit. Please
report back whether you are able to assign bugs after this
configuration change.
(If developers could assign bugs without having the
EditAssignment bit in rc5 that might have been bug that is
now fixed. I can't find any relevant changes in CVS
though... Maybe you had configured rc5 they same way as
suggested above?)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The only way I can see is to add a person to a certain
group, and then make this group e.g "Locked | Assignable",
but still the person can not assign others to a bug.
(He can be assign to a bug by a administrator, but he
himself can not assign others...)
I think it work in 0.9.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oops! You are right. One cannot set the 'EditAssignment' bit
from the admin pages in v1.0.x. Sorry. My fault. I should
have tested.
To give your developer group EditAssignment permissions by
hand try this (assuming phpbt_ as table prefix):
1) Find the 'group_id' of your Developer group by searcing
the phpbt_auth_group table.
2) Find the 'perm_id' of EditAssignment in the
phpbt_auth_perm table.
3) Add a row to the phpbt_group_perm table that connects the
two id:s.
With a default setup this would be the SQL query to use:
INSERT INTO `phpbt_group_perm` ( `group_id` , `perm_id` )
VALUES ('3', '3');
Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I assign this bug to Benjamin who may decide whether the
developer group should have EditAssignment permission by
default or not.
Currently only Admins (and perhaps project admins?) are
allowed to assign bugs. There seems to be no bug in the code
just a configuration disagreement. Without an easy way to
change what permissions a group has this can confuse and
frustrate users.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=592447
To be allowed to assign bugs you must be member of a group
with the EditAssignment bit. The developers group does not
have this bit by default. (I don't think they had so in rc5
either)
Use the Groups page in the Administration Tools to edit your
Developer group and add the EditAssignment bit. Please
report back whether you are able to assign bugs after this
configuration change.
(If developers could assign bugs without having the
EditAssignment bit in rc5 that might have been bug that is
now fixed. I can't find any relevant changes in CVS
though... Maybe you had configured rc5 they same way as
suggested above?)
Logged In: YES
user_id=1337983
The only way I can see is to add a person to a certain
group, and then make this group e.g "Locked | Assignable",
but still the person can not assign others to a bug.
(He can be assign to a bug by a administrator, but he
himself can not assign others...)
I think it work in 0.9.
Logged In: YES
user_id=592447
Oops! You are right. One cannot set the 'EditAssignment' bit
from the admin pages in v1.0.x. Sorry. My fault. I should
have tested.
To give your developer group EditAssignment permissions by
hand try this (assuming phpbt_ as table prefix):
1) Find the 'group_id' of your Developer group by searcing
the phpbt_auth_group table.
2) Find the 'perm_id' of EditAssignment in the
phpbt_auth_perm table.
3) Add a row to the phpbt_group_perm table that connects the
two id:s.
With a default setup this would be the SQL query to use:
INSERT INTO `phpbt_group_perm` ( `group_id` , `perm_id` )
VALUES ('3', '3');
Hope this helps.
Logged In: YES
user_id=1337983
No problem - following your description, it works again. Thanks.
Logged In: YES
user_id=592447
I assign this bug to Benjamin who may decide whether the
developer group should have EditAssignment permission by
default or not.
Currently only Admins (and perhaps project admins?) are
allowed to assign bugs. There seems to be no bug in the code
just a configuration disagreement. Without an easy way to
change what permissions a group has this can confuse and
frustrate users.