Skip to content
This repository has been archived by the owner on Apr 30, 2021. It is now read-only.

[Reporting] Technical design #227

Open
v1r7u opened this issue May 5, 2020 · 0 comments
Open

[Reporting] Technical design #227

v1r7u opened this issue May 5, 2020 · 0 comments
Labels
area/documentation Improvements or additions to documentation kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/M

Comments

@v1r7u
Copy link
Contributor

v1r7u commented May 5, 2020

Design Joseki Reporting feature.

Reporting should support:

  • scheduled/on-demand reports
  • sending reports (email/Slack/Teams/webhook)
  • view previously generated reports
  • RBAC integration
@v1r7u v1r7u added area/documentation Improvements or additions to documentation kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work size/M priority/low Low priority issues labels May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/documentation Improvements or additions to documentation kind/enhancement New feature or request lifecycle/backlog General backlog pile. Any idea, which could be taken into work priority/low Low priority issues size/M
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@v1r7u