Opened 17 years ago
Last modified 14 years ago
#7290 new enhancement
restrict_owner_force Option to populate user list
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | restrict_owner consider |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
The restrict_owner setting changes the field to a dropdown list that has (1) TICKET_MODIFY rights and (2) logged in at least once.
In an environment where you add users - and want them to be assigned tickets - even if they have not logged in before can be useful. Maybe the following option can be added:
Something like Add restrict_owner_force = TRUE in ini file to populate the list with the TICKET_MODIFY rights, without having logged in. This way either the filtered and unfiltered lists can be made available depending on the environment requirements. I have need for both situations.
Attachments (0)
Change History (6)
follow-up: 2 comment:1 by , 17 years ago
follow-up: 3 comment:2 by , 17 years ago
Replying to nkantrowitz:
-1, better to provide a snippet to populate the session table based on permissions and existing tickets (for migrations). Real support will arrive with IUserDirectory stuffs.
Is this IUserDirectory
idea documented anywhere, or is this just a pie in the sky idea for better user management-related extension points? I'm guessing the latter, since a search turned up nothing. But I'm curious, because we've done a lot of work related to user management in Trac (in particular, keeping track of "project members" versus "project participants").
comment:3 by , 17 years ago
Replying to ebray <hyugaricdeau@gmail.com>:
Is this
IUserDirectory
idea documented anywhere, or is this just a pie in the sky idea for better user management-related extension points? I'm guessing the latter, since a search turned up nothing.
Mostly the latter, AFAICT: this topic has been discussed since late 0.9. I hope it will be defined at some point, as I hope to connect a LDAP directory as a possible back end. Now that 0.11 is finally ready (I hope so), maybe it's time to (re)think this API.
comment:5 by , 17 years ago
Keywords: | consider added |
---|---|
Milestone: | 0.11.1 → 0.12 |
Owner: | removed |
comment:6 by , 14 years ago
Milestone: | next-major-0.1X → unscheduled |
---|
-1, better to provide a snippet to populate the session table based on permissions and existing tickets (for migrations). Real support will arrive with IUserDirectory stuffs.