-
-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Populate project and customer by activity selection #1634
Comments
I am not happy with that, as we are only duplicating features that are already available ... but not that easy to understand (you are not the first person to miss that dropdown at all.) - so maybe its better to improve the UX for it? Adjusting the part you are asking for is a massive pain, as the code is already quite complicated (even though it might not look like it, as it is "only" a dropdown). Adding other options to pre-select project and activity could be added as, eg. "bookmarks" were requested multiple times. |
No feedback, closing |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai. |
Is your feature request related to a problem? Please describe.
When adding a timesheet entry, it's unnecessary to fill out the project and customer when those are always connectedto the activity. If you enter an activity, project and customer should be populated automatically.
Describe the solution you'd like
When going to the activity selection, a list of recent activities should be displayed. If none of those is the desired activity, the user can search by name. After a selection, customer and project are populated automatically.
Describe alternatives you've considered
Populating manually (although only project seems to be really neccessary as customer can be left empty even though it is marked as obligatory).
The text was updated successfully, but these errors were encountered: