Edgewall Software
Modify

Opened 10 years ago

Last modified 8 years ago

#7290 new enhancement

restrict_owner_force Option to populate user list

Reported by: bill.meyer@… Owned by:
Priority: normal Milestone: unscheduled
Component: ticket system Version:
Severity: normal Keywords: restrict_owner consider
Cc:
Release Notes:
API 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)

comment:1 Changed 10 years ago by Noah Kantrowitz

-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.

comment:2 in reply to:  1 ; Changed 10 years ago by ebray <hyugaricdeau@…>

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 in reply to:  2 Changed 10 years ago by anonymous

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:4 Changed 10 years ago by Noah Kantrowitz

There are some patches on #2456, not sure how recent they are.

comment:5 Changed 10 years ago by Christian Boos

Keywords: consider added
Milestone: 0.11.10.12
Owner: Christian Boos deleted

comment:6 Changed 8 years ago by Remy Blank

Milestone: next-major-0.1Xunscheduled

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set.
The owner will be changed from (none) to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.