You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Might be "be design", then it is a feature request)
When an item is in the "recent items" area of a list / grid, after long-press (or three-dots) on the details view, the "Description" field isn't available. It is only available when the item details are called up from the "get me!" / "active items" list (how do you call that?). Field should always be available, regardless of how user "enters" into the details screen.
Use case:
spot something on the recent items, notice description entry is wrong (or want to add one now). Have to tap it once (if I remember that long-tap right here won't work for the field is missing then) => item jumps to "ge me!" list (which is sorted by categories or even algorithm, so where did it jump...!? Ah, there it is...) => long tap => edit => save/back => tap again to get it back down to "recent items" (as I don't want it on the "get me!" section for now).
Versus: directly being able to edit would be way more easy and "straight forward".
Share your logs
No response
Share your configuration
No response
The text was updated successfully, but these errors were encountered:
Is this urgent?
No
What parts are affected
Frontend
What is the server version
92
What is the client version
v0.4.20 (91)
What platform are you using
Android, Web, Linux
What's the problem 🤔
(Might be "be design", then it is a feature request)
When an item is in the "recent items" area of a list / grid, after long-press (or three-dots) on the details view, the "Description" field isn't available. It is only available when the item details are called up from the "get me!" / "active items" list (how do you call that?). Field should always be available, regardless of how user "enters" into the details screen.
Use case:
Share your logs
No response
Share your configuration
No response
The text was updated successfully, but these errors were encountered: