phpGroupWare - Bugs: bug #2103, Time Track Admin Setup is Bad
You are not allowed to post comments on this tracker with your current authentication level.
bug #2103: Time Track Admin Setup is Bad
Submitter: | Dave Hall <skwashd> | ||
Submitted: | Tue 31 Dec 2002 10:28:33 PM UTC | ||
Item Group: | 0.9.14.001 release | Category: | timetrack |
Severity: | 3 - Normal | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Component Version: | None | Operating System: | None |
Reproducibility: | None | Planned Release: | None |
Fixed Release: |
Mon 05 May 2003 04:57:33 PM UTC, comment #1: |
Johnson <jecinc> |
Tue 31 Dec 2002 10:28:33 PM UTC, original submission:
The admin setup script for timetrack is bad imho.
It should not automatically create 2 new groups without warning, and then use user based acls for granting access to the app.
For the current release it should at least warn the admin what it is about to do (with a no option) and use the TT_Users Group to grant access to the app.
In future releases i think it should allow the admin to use an existing group to be used as the "users" group.
I like many admins like to play with an app to decide if it is suitable. The current admin setup script does not allow this.
Cheers |
Dave Hall <skwashd>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
I changed my copy to use interface similar to projects to pick users or groups to be project managers or payroll managers with initial default to default ttrack groups if they exist
Values stoed in acl table instead of app table (which is what projects does)