Opened 15 years ago
Last modified 9 years ago
#6969 new defect
Add option to limit target project
Reported by: | Fine Banana | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | TicketMoverPlugin |
Severity: | normal | Keywords: | ticket move target |
Cc: | jhammel | Trac Release: | 0.11 |
Description
My Trac setup consists of many projects and since I enable this plugin, opening a ticket just for viewing takes a long time. I suspect this is due to the extra process in the plugin to check thru all existing Trac projects before populating them in the drop down list. It will be good is you can add on option to limit the target project to the ones listed explicitly in an additional parameter, for example:
there are 10 projects in the Trac server: project1 .. project10
and this plugin is enabled for project1, but for some reasons, I'd like to limit moving of ticket from project1 only to project2 and project3. So in project1's config, i'd like to specify:
ticketmoverplugin.target = project2, project3
With this option, I hope the plugin will only go thru the listed ones and shorten the time taken to open up existing tickets in project1. If the parameter is not specified or missing, then the current behaviour can be use as default.
Attachments (0)
Change History (3)
comment:2 follow-up: 4 Changed 15 years ago by
comment:3 Changed 10 years ago by
Owner: | Jeff Hammel deleted |
---|
i agree. i have more than 20 projects and each i browse a ticket, it loads a ticket at an average of 30 seconds.