Skip to content
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

Notification mechanism for Guardian #2426

Closed
anvabr opened this issue Jul 17, 2023 · 0 comments
Closed

Notification mechanism for Guardian #2426

anvabr opened this issue Jul 17, 2023 · 0 comments
Assignees

Comments

@anvabr
Copy link
Collaborator

anvabr commented Jul 17, 2023

Problem description

Currently the status of most long-running Guardian actions, such as minting tokens, publishing (potentially large) documents, is not visible thus users may get the wrong impression or get confused. Furthermore, these long-running operations usually involve 3rd party (external) systems, and thus error prone. When errors occur the users do not get notified about them, and may notice failures later in the process thus causing them to attribute the errors to the wrong step- usually their or the system last action.

Requirements

Introduce notification capability to Guardian such that users can see:

  • the progress of long-running tasks (i.e. "policy creation is 70% complete")
  • the status of completed tasks
  • review all the tasks (perhaps navigating to the special page by clicking 'view all tasks')
  • navigate into tasks to see the details about the tasks or other relevant info about the results of the task execution (e.g. created artifacts)

There should be a way to mark notifications as 'read' one by one or 'all'.

Add the capability into the policy to create notifications (i.e. a new 'notification block') which would enable policy creators to alert particular users about the actions they need to take and/or inform them about an event.

Definition of done

  • Notification system is implemented where tasks list is accessible from the UI via a drop-down menu with the functionality as described above.
  • Documentation updated accordingly.
  • An example usage of the notification block is implemented in one of the demo policies.

Acceptance criteria

Users get access to the status information of at least the following long-running tasks:

  • token creation
  • token minting
  • policy/shema create, import, export, publish, clone
  • user and key operations
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants