1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

Ticket #24505 (assigned)

Opened 2 years ago

Last modified 2 years ago

new beta projects - why admin no rights to moderate?

Reported by: jmichae3 Owned by: ctsai
Keywords: PEND Cc:
Private: no

Description

in the tools, I have noticed consistently that
- when initial rights are given, usually only 1 user is granted access.

- after touching something like permissions on the tools, the tools reorder themselves - ack! please make them stay in the same order unless someone changes the layout of the browser. this is a suggestion for a change. with so many tools to tweak, I have a hard time figuring out which one I changed when they keep shifting on me every other click.

- moderator should have both developer and admin I should think, by default. what do you think? this is a suggestion for a change.

thanks - Jim Michaels

Change History

  Changed 2 years ago by jmichae3

when I say moderator should have both developer and admin, I mean for NEW projects. I wouldn't dare change existing projects.

in reply to: ↑ description   Changed 2 years ago by ctsai

  • keywords PEND added
  • owner set to ctsai
  • status changed from new to assigned

Replying to jmichae3:

in the tools, I have noticed consistently that
- when initial rights are given, usually only 1 user is granted access.

I'm not sure what you mean, the permissions are granted by usergroups (eg., Admin, *anonymous), not individual users.

- after touching something like permissions on the tools, the tools reorder themselves - ack! please make them stay in the same order unless someone changes the layout of the browser. this is a suggestion for a change. with so many tools to tweak, I have a hard time figuring out which one I changed when they keep shifting on me every other click.

I just tried changing permissions on a few tools on my test project, and the tool order never changed. Could you provide some specific steps to reproduce this?

- moderator should have both developer and admin I should think, by default. what do you think? this is a suggestion for a change.

The default moderate permissions are for developer, and the admin usergroup is a subset of the developer group (ie., all admins are also developers), so just having developers have moderate permissions implies that admins also have the permissions. Or am I missing something?

Regards,
Chris Tsai, SourceForge.net Support

  Changed 2 years ago by jmichae3

"The default moderate permissions are for developer, and the admin usergroup is a subset of the developer group (ie., all admins are also developers), so just having developers have moderate permissions implies that admins also have the permissions. Or am I missing something?"

there's no manual for a lowly admin like me. I have mentioned this a few times.
the users and user groups have a structure *I* am not familiar with, and if I am not familiar with them, same goes for probably the rest of the sf.net folk.

"I just tried changing permissions on a few tools on my test project, and the tool order never changed. Could you provide some specific steps to reproduce this?"

click admin.
click tools.
on bugs, support tickets, feature requests, and whatever else you can find that has permissions, (work them all),
click options first and make changes,
such as the notification email, and setting the notifications to all changes and click save, then click tools (if you have to)
click on permissions on the same item,
make changes,
click save,
click tools.
try another item and note the order of the items.

this needs to be a beta project, not classic.

this happens to me ALL THE TIME on ALL my projects that were migrated.

Note: See TracTickets for help on using tickets.