nl-kat-coordination
nl-kat-coordination copied to clipboard
minvws
Design improvements: Task overview
User feedback lead to some discussion (2484) of which these improvements are discussed for design solutions:
- Add bulk action possibility
- Add visual clue like a checkmark on succeeded tasks
- Find solution for the wrong use of expandable rows expanding with only two buttons (takes unnecessary clicking).
- Add design for the option to cancel scheduled tasks (ticket #2632)
Plus possibly after discussing with Heleen: -❔ Find a way that users don't lose the tasks they reschedule out of sight because it shoots to the top of another page (because they are sorted by scheduled date by default) -❔ Prevent page refresh if possible --> After discussion: Design confirmation message on top of page to let users know task has been rescheduled. With the possibility of bulk actions & + confirmation message the page refresh should no longer be an obstacle. For the use case of rescheduling 1 task there is a confirmation message on top of the page that needs to be visible, and in case users want to reschedule multiple tasks the bulk action provides the possibility without losing scroll position in between every rescheduled task.
Screenshots of the current task list page will be provided to see the current functionalities.
FOR REVIEW: https://www.figma.com/file/tYzng7qq8nPnfxaKJgWm71/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Task-list?type=design&node-id=2301%3A32986&mode=design&t=VtjDJ3bsdmpL28KF-1
Slight changes based on previous feedback in updated design: FOR REVIEW: https://www.figma.com/file/tYzng7qq8nPnfxaKJgWm71/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Task-list?type=design&node-id=2301%3A32986&mode=design&t=Sn8VRcgSRtQuQv9d-1
If approved, this ticket can be closed.
I have replied to some comments @underdarknl to confirm whether or not I understand it correctly, in order to make the next iteration on this design. Maybe we can meet about this after June 19th. I've put this ticket in sprint 37 (June 7-20) because if I can clear my questions up I can make a new iteration quite quickly.
After discussing this with @underdarknl , a design update has been made adding:
- New metrics of a job/task process.
- Mime-types of results grouped by raw file & possibility to download separate raw files (+job meta)
- Additional info for related tasks; which mime-type initiated the related task
Two focus points to consider while reviewing:
- Separate raw files don't have names right now, making it hard for users to identify/distinguish them. Numbering them could be a solution for users to identify them, shown in the design. Is this a sufficient solution for the problem?
- Related to this, if the job/task results in two separate raw files that both create a similar mime-type, it looks like the related jobs initiated by these mime-types will not be distinguishable for the users in the current design. Is this conclusion correct? If so, we might want to include raw file ID/name/number to related tasks.
FOR REVIEW: https://www.figma.com/design/tYzng7qq8nPnfxaKJgWm71/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Task-list?node-id=2389-31981&t=cO0YyRQxx1KQLy25-1
After feedback on the previous design, a design update has been made with changes:
- ‘Overview’ tab to offer users a way to see what jobs are currently active. The combined tab of boefje jobs and normalizer jobs in one table (previous design) was confusing because of their different nature and different column variables.
- A collapsed row specificly for Normalizer jobs, with different initiators/output than the Boefje jobs.
https://www.figma.com/design/tYzng7qq8nPnfxaKJgWm71/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Task-list?node-id=2301-32986&t=4VHsJtJ8Fd4wC1Ti-1
I added the small confirmation modal flow to the file. It's still for review.
Design is approved for implementation. Implementation Figma link: https://www.figma.com/design/zoorlsXQ0ankrB4tsxusvo/%E2%9C%85-KAT-%7C-Approved-%7C-Task-List?node-id=2332-6707&t=V0VMYPf9gaRktq2d-1