List view
In Q4, the focus will be on fine-tuning the integration between the legacy Elektra dashboard and the new Aurora dashboard. This includes reducing technical debt, fixing bugs, introducing new UI components, and making the Gardener UI ready for production use by real customers. The goal is to deliver a seamless, stable, and user-friendly experience across both dashboards. ## Goals and Deliverables 1. **Seamless Integration between Elektra and Aurora** - Ensure smooth session transfer and data synchronization - Harmonize authentication and authorization mechanisms - Align UI and navigation patterns for a consistent user experience 2. **Technical Debt Reduction** - Identify and refactor code and architecture that hinder integration and maintenance 3. **Bug Fixing and Stability Improvements** - Prioritize defects affecting user workflows, authentication, and API interactions - Address edge cases such as token expiration handling in Aurora - Improve overall system stability and performance 4. **Gardener UI Production Readiness** - Polish UX/UI based on user feedback and testing - Optimize performance and responsiveness - Finalize features necessary for real customer usage 5. **Extend New Dashboard with UI Components** - Develop and integrate new UI components such as: - **Flavors:** Component(s) to select and manage instance or service flavors - **Object Storage:** Component(s) for configuring and managing object storage services - Ensure these new components align with the design and technical standards of the Aurora dashboard
Due by December 31, 2025•39/41 issues closedThis milestone encompasses key objectives for achieving a production-ready deployment along with critical feature integrations and UI enhancements. The focus is on ensuring secure, scalable deployment and delivering a Minimum Viable Product (MVP) for the Gardener UI and integrating in Elektra. ### Goals and Deliverables 1. **Production Deployment** - Enable Pull Request (PR) previews for deployment validation - Configure deployment details including: - Region-specific settings - Catalog entry setup for API access - Ensure no secrets are exposed in the deployment process 2. **Gardener UI in MVP State** (Definition of Done) - Integrate Gardener within OpenStack authentication scope - Define and document requirements and user stories for MVP - Deliver UX designs that meet the documented requirements - Implement refined UI designs reflecting the approved UX - Utilize TanstackQuery for all API requests to enhance data fetching and caching 3. **Legacy System Integration** - Implement session transfer capabilities - UX integration components including: - Layout adjustments - Navigation flow improvements - UI/UX enhancements - Handle edge cases such as token expiration in Aurora
Overdue by 2 month(s)•Due by September 30, 2025•44/46 issues closed