RomijnHumanoids
commented
1 week ago The design review file consists of a first draft, and another version with a different approach.
Change log:
- (ticket #3123) Exploration different approach: split between ‘schedules’ tab and ‘scheduled reports’ tab.
- (ticket #3857) Editing recipes via route leading back to the filled report flow with the data of the recipe (Assuming this is less implementation work but it hasn’t been discussed).
About this feature
Detailed description
Now that we can schedule reports, users also need to be able to edit, disable and delete the schedules. As backend implementation allows for editing recipe as a whole, and this is now linked to buttons in the 'scheduled reports' tab on the reports page, we propose an update with a focus on UX. There were no designs for editing schedules yet. Using human readable terms, recognisable elements from the report flow for example would already improve the current version in the main branch.
Because 'edit recipe' and 'disable schedule' is in this sprint (48), I suggest prioritising this design ticket so that it can be instantly implemented (as far as components of the design exists in implementation).
Feature benefit/User story
As a user, I want to edit my scheduled reports recipe so that I can make small alterations without having to delete the recipe and start the report flow over again.
Specifications
Please add some specifications for the implementation. What needs to be implemented to match the design?
The implementation should include…
Additional information
Any additional information, considerations, or context that might be helpful for understanding or evaluating the feature request.
Design
This part should only be filled in by the OpenKAT design team.
Screenshots
Include screenshots of the proposed design changes here.
Figma link
Link to the Figma design for further visualization (if applicable)
Implementation
This part should only be filled in by the developers.
Possible solution
Outline your proposed solution for implementing the feature. You can include any specific ideas, designs, or functionalities here.
Alternatives considered
Describe any alternative approaches or solutions you've considered, and why you believe the proposed solution is superior.