Enable global time logging at /time_entries/new
|Assignee:||Jean-Philippe Lang||% Done:|
To log time you currently need to first select a project, then select the time entries report after which you can log your time against a project. We need to be able to log time against lots of different projects without always having an issue.
To make this easier it would be nice to have a global time entry form where one can choose the project and enter the hours at the same time. Almost identical to the currently time logging screen only that you can select a project instead of an issue.
#2 Updated by Olivier Jacquet over 10 years ago
- File redmine-timelog.patch added
I don't have Rails experience but here's what I got so far.
- Added project dropdown to the timelog form;
- Modified order of getting project_id in find_project so that the POSTed project_id has priority on the project_id in the URL
What I'd like to achieve:
- When on a time entry form from a project the dropdown shouldn't be there. Then everything can remain as-is;
- When there isn't a project chosen (e.g. on /time_entries/new) there should be a project dropdown and no issue textfield;
- Ideally the project hierarchy is also repeated there so that I can use the Chosen plugin to easily search a project
- We currently use tickspot for time tracking but it isn't that user friendly if you have a lot of different projects and we would like to log all time in redmine because logging in 2 applications was also cumbersome.
#4 Updated by Jean-Philippe Lang over 10 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 1.4.0
- Resolution set to Fixed
Feature added in r8691. It covers what you're expecting, except that the issue field was left visible, as there's no reason IMO to prevent the user from logging time on a specific issue of a project.
#5 Updated by Ivan Cenov over 10 years ago
It is possible to select a project and to enter a number of an issue that is from another project. The result is that the selected project is silently changed to the one that the issue belongs to. May be some validation on the issue edit control should be added. On the other side this would be heavy operation in a system where many projects and many issues exist.