List view
1. Restructure the greenhouse in a way that we are enable to implement org plugins newly 2. We are able to migrate to Carbon in easy way at any point in time 3. Review the user stories and finalize the UX wireframes 4. Create a new fundation based on tanstack router to build all admin apps upon it 5. Migrate the existing apps to work with new foundation in a way that we cover the decided user stories
Due by December 31, 2025•0/2 issues closed* Convert image-version queries into image-based queries so that the support group journey can present image-based information instead of relying on different “image versions.” * Define the schema in collaboration with the backend * Implement mutation queries and their request logic * Design necessary views with designers and implement them * Add tests covering all new functionalities
Due by December 31, 2025•0/1 issues closed. Develop Feature Requests from Users after Go-Live . Implement Deep Link Functionality . Refactoring based on using tanstack router . Setup Schema Change Management . Apply Code Changes with UI-Friendly Queries from Schema . Write and run tests for all required components . Provid a list of Non-duplicated issues for managers journey
Overdue by 4 day(s)•Due by October 31, 2025•16/23 issues closedThis milestone focuses on upgrading all existing UI components to be fully compatible with React 19, ensuring optimal performance, stability, and access to the latest React features.
Overdue by 6 month(s)•Due by April 25, 2025•7/7 issues closed- Overdue by 8 month(s)•Due by March 1, 2025•6/6 issues closed
Create a detailed, user-friendly documentation for the Juno design system and component library, ensuring that users can easily understand, navigate, and implement UI/UX best practices using the components provided. This documentation will cover UX best practices, key terminology, layout standards, guidelines for component usage, and recommendations for UX patterns based on specific use cases. Objectives: - Describe base patterns and best practices that helps with the most common use cases - Descriptive examples - Decision help (e.g. in the form of decision trees, flow charts) - People should be able to create a recognizable "Juno" app with common patterns and paradigms using this documentation Key Deliverables: - Documentation publicly available (e.g. as part of the storybook docs) - All base patterns that are necessary for building admin UIs are described
Overdue by 10 month(s)•Due by December 20, 2024•8/11 issues closed- Overdue by 9 month(s)•Due by January 31, 2025•7/7 issues closed
Acceptance Criteria: * Initial Aurora app deployed * One initial module (e.g. Servers) exists and shows something
Overdue by 10 month(s)•Due by December 20, 2024•1/1 issues closed* Architecture diagram * where should business logic live (in our proxy layer or somewhere else) * How can others contribute to the "proxy" layer
Overdue by 11 month(s)•Due by November 29, 2024•5/6 issues closed