Actions
Defect #17954
closed/time_entries/new can't derive project from issue
Start date:
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
Description
If you use the /time_entries/new link to log a new time entry from outside the context of a project the form displays with both a Project field and an Issue field.
The Project field defaults to the first Project in the database, regardless of whether the current user is a member of that Project.
If the use enters an Issue Number belonging to a different Project and press Create they get an "Issue is invalid" error message. The user needs to change the Project to the correct value for the Issue in order for the time entry to be saved successfully.
It would be better if:
- the Project select list didn't have a default value
- if a valid Issue is chosed (and if the previous item has been implemented then the Project is blank) the Project is derived from the Issue automatically
- ideally, the Project select list shouldn't show Projects the user isn't a member of
Updated by Jean-Philippe Lang about 10 years ago
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 2.6.0
- Resolution set to Fixed
Roger Hunwicks wrote:
- the Project select list didn't have a default value
- if a valid Issue is chosed (and if the previous item has been implemented then the Project is blank) the Project is derived from the Issue automatically
Fixed in r13422.
- ideally, the Project select list shouldn't show Projects the user isn't a member of
The list shows projects for which the user is allowed to log time. Please open a new ticket if there's a problem about that.
Actions