-
Notifications
You must be signed in to change notification settings - Fork 55
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
Design reports flow for "all organisations"-view #2346
Comments
This design is waiting for a conclusion on the new flow with query building. #2713 |
This ticket is not blocked anymore as of June 5 '24. It will be possible to work in this in sprint 37 (June 7-20), or sprint 38 (June 21-July 4) depending on who is going to work on it. |
There are still some questions to be answered, let's review in a meeting. |
Small changes since last design review. Now awaiting approval for implementation. Review link: https://www.figma.com/design/OIl7U9gY4T5tLSZ2wUby5n/%E2%9C%8D%F0%9F%8F%BC-KAT-%7C-For-Review-%7C-Reports-Flow?node-id=1669-51480&t=GeK5z2suheCfFdhj-1 |
The design of the flow itself has been reviewed and slightly revised. The only question now (as described in comments) is how to enter the flow now that there's organisations that need to enter both the flow for object-reports and report-reports. |
As mentioned in my previous comment, the design of the flow itself has been reviewed and doesn't need big changes. While discussing ticket #3335 we noted however that a report based on reports is not always mean across organisations like a sector report because it can also be a large organisation (e.g. hospital) with some assets hosted by an external party, or even combining multiple aggregate reports within the same organisation. Some copy needs to be changed and these will need a final review (design and technical expert) soon. |
Reports page design from the view "all organisations"
Current workfile(s)
https://www.figma.com/file/6vS6Ehh64hyPJB3FKdHf7K/KAT-%7C-Design-%7C-Reports?type=design&node-id=1811%3A31199&mode=design&t=c6ETcSKf02ILCf42-1
The text was updated successfully, but these errors were encountered: