On Thu, 31 Jan 2013 02:20:40 AM Pedro Rodrigues wrote: > In the old Sourceforge interface, developers were able to claim a bug, to > signal it was being worked on and avoid duplicate work. > > In the new interface, there is an owner field (not sure if its the > corresponding field), but developer have no way to edit bug reports (not > even to change status)
Ugh. That is clearly an unacceptable regression. The `upgrade' issues
continue.
> Is it possible to give developers editing capabilities to the bug reports?
I went to "User Pemissions" under the "Admin" tab and hacked around. There
are five levels: admin, developer, member, authenticated, anonymous, and four
permissions: admin, create, read, update. Documentation of the precise
semantics is hard to find, so I am hoping that giving developer all permissions
except admin will do the right thing. Ironically, I am unable to test the
result, so let us know if it worked.
FTR, the current full breakdown is now:
admin: acru
developer: cru
member: cr
authenticated: cr
anonymous: r
This is a rough cut at replicating what we used to have, the main difference
being that you have to authenticate to create a bug report. What is unclear
is whether this allows authenticated users to add comments to their own bugs
or other people's bugs. If a helpful non-{admin,developer} reads this, please
comment.
Cheers,
Mike Pope
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________ Freecol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freecol-developers
