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
This is step 4 of creating scheduled reports. It needs to be possible for the users to cancel their scheduled reports.
Feature benefit/User story
As a user, I want to cancel my scheduled report, so that I can stop the scheduling from happening in the future.
Specifications
The implementation should include…
Button when row is expanded
When enabled: show disable button
When disabled: show enable button
Show in table that the schedule is enabled/disabled
Design
Screenshots
Figma link
...
Implementation
Possible solution
The scheduler already has the possibility to enable/disable a schedule. The cron and deadline_at variables will remain the same.
By clicking on the disable button (or cancel button), the page should refresh and it should be visible in the table that the schedule has been disabled. Also, the disabled button then must be replaced with an enable button.
Alternatives considered
...
The text was updated successfully, but these errors were encountered:
This ticket is part of epic #2626
About this feature
Detailed description
This is step 4 of creating scheduled reports. It needs to be possible for the users to cancel their scheduled reports.
Feature benefit/User story
As a user, I want to cancel my scheduled report, so that I can stop the scheduling from happening in the future.
Specifications
The implementation should include…
Design
Screenshots
Figma link
...
Implementation
Possible solution
The scheduler already has the possibility to enable/disable a schedule. The cron and deadline_at variables will remain the same.
By clicking on the disable button (or cancel button), the page should refresh and it should be visible in the table that the schedule has been disabled. Also, the disabled button then must be replaced with an enable button.
Alternatives considered
...
The text was updated successfully, but these errors were encountered: