Feature #4382
[Refactor] Move autocomplete methods to an AutocompleteController
| Status: | New | Start date: | 2009-12-11 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | - | % Done: | 20% |
||
| Category: | Code cleanup/refactoring | ||||
| Target version: | - | ||||
| Resolution: |
Description
If the Autocomplete methods are moved to a common AutocompleteController, it would be easier to share them with different parts of Redmine. This would make adding things like an issue autocomplete for the Issue Relations trivial.
Related issues
Associated revisions
Refactor: move IssuesController#auto_complete to a new controller. #4382
History
Updated by Eric Davis about 2 years ago
- Category set to Code cleanup/refactoring
Updated by Richard Schulte about 2 years ago
+1 as it relates to #4325, and all the other wonderful possibilities that could come of it!
Updated by Eric Davis over 1 year ago
- Target version changed from 1.0.0 (RC) to 1.1.0
Updated by Eric Davis over 1 year ago
- Status changed from New to Assigned
- % Done changed from 0 to 20
Started on this in r3945 with the issues autocomplete.
Updated by Eric Davis about 1 year ago
- Assignee deleted (
Eric Davis)
I am stepping down from working on Redmine. If someone else is interesting in working on this issue, feel free to reassign it to them.
Eric Davis
Updated by Jean-Philippe Lang about 1 year ago
- Target version changed from 1.1.0 to Unplanned
1.1 feature freeze.
Updated by Etienne Massip 11 months ago
I don't think there should be an autocomplete dedicated controller with methods concerning issues, others categories, users, etc.
I think these autocomplete methods shoud stay in issue_controller, etc. and may use an autocomplete helper tightly linked to the application_helper.
Updated by Jean-Philippe Lang 3 days ago
- Status changed from Assigned to New
- Target version deleted (
Unplanned)