-
Notifications
You must be signed in to change notification settings - Fork 58
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
GUI Notifications: user actions #3221
Labels
kind/enhancement
New feature or request
Comments
In order to implement this feature the following changes are required form server side:
|
tcibinan
added a commit
that referenced
this issue
May 17, 2023
tcibinan
added a commit
that referenced
this issue
May 17, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
May 18, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
May 18, 2023
rodichenko
pushed a commit
that referenced
this issue
May 23, 2023
GUI Issue #3221: Postpone lifecycle rule action
rodichenko
added a commit
that referenced
this issue
May 24, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
May 30, 2023
…ING_QUOTA_EXCEEDING actions
AleksandrGorodetskii
added a commit
that referenced
this issue
May 30, 2023
rodichenko
pushed a commit
that referenced
this issue
May 30, 2023
NShaforostov
changed the title
[DRAFT] GUI Notifications: user actions
GUI Notifications: user actions
May 30, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
May 31, 2023
rodichenko
pushed a commit
that referenced
this issue
May 31, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 1, 2023
rodichenko
pushed a commit
that referenced
this issue
Jun 1, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 2, 2023
… according to quota info
mzueva
pushed a commit
that referenced
this issue
Jun 6, 2023
mzueva
pushed a commit
that referenced
this issue
Jun 6, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 6, 2023
GUI Issue #3221: Postpone lifecycle rule action
AleksandrGorodetskii
pushed a commit
that referenced
this issue
Jun 6, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 6, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 6, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 6, 2023
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 6, 2023
… according to quota info (#3263)
AleksandrGorodetskii
added a commit
that referenced
this issue
Jun 6, 2023
GUI 0.16 UAT - notification actions (issue #3221)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
Since #3015 is implemented, users have the handy form where all users' related notifications are displayed.
Users can view them and manually perform neccessary actions in the Platform based on the information from that notifications - for examlple, to avoid extra spendings on forgotten run and stop it.
As further steps - it would be convenient for users to perform some actions explicitly from the notification - to not perform extra actions.
For example, user received a notification LONG_RUNNING. Currently, the Platform suggests user to open the run logs page, then manually check the run state and solve what to do with it. In this case, it would be useful to have the list of possible user's actions for this run inside the notification - it may be "STOP"/"PAUSE" actions.
Let's add possible actions to notifications where it is possible.
Approach
POSTPONE
- Postpone transition on the predefined number of days.
PAUSE
STOP
- Pause run.
- Stop run.
RESUME
TERMINATE
- Resume run.
- Terminate run.
TERMINATE
- Terminate run.
RESUME
TERMINATE
- Resume run.
- Terminate run.
PAUSE
STOP
- Pause run.
- Stop run.
Show the following actions under conditions (otherwise, hide them):
Actions shall be shown only at the Notifications page as set of buttons for each notification, e.g.:
Other options
A clear and concise description of any alternative solutions or features you've considered.
The text was updated successfully, but these errors were encountered: