-
Notifications
You must be signed in to change notification settings - Fork 5
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
Magic link workflow improvements #79
Comments
nice. |
I thought about something like this as well. However, I think that adding a button to each row in the timesheet is too much so this would be my proposal:
|
I think this "magic mode" would be rather tricky to understand or be discoverable, unless massive visual aids help pointing the user in the right direction after clicking (highlighting clickable rows). It would also introduce some additional state management complexity. I'd rather stay with my proposal, I but absolutely accept your objection regarding over-cluttering of the timesheet row. In the activities tab, we could entirely replay the "play" button, as my proposal would also allow users to "start tracking". It would add one click if you wanted to resume an activity, but that's acceptable IMO. In the timesheet tab, the magic link button could be hidden unless the row is moused over, to avoid visual clutter. Or maybe we could move some rarely-used parts of the row into an edit mode (similar to the form that pops when clicking on a row in the activities tab) where we would hide the delete button, possibly the remaining-effort input and the "magic" link |
The magic links (#1022) are indeed magic! However, I wish for some changes that would massively improve the feature's usability and effectiveness.
Similar to adfinis/timed-frontend#685, I'd like to have the possibility to have a magic link anywhere (At minimum in activities and timesheet, possibly other places).
I kinda imagine it to work as follows:
Here's how I imagine it to look (roughly):
This would enable the following use cases:
The text was updated successfully, but these errors were encountered: