Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Amanda3
Amanda3Level 1

Workload Balancer Setting - Add Color Theme functionality for Project PriorityNew

Description - Why is this feature important to you -My PMO manages projects for a Creative Studio Resource. At any given time there are more than 100 projects open. When we are looking at that teams Workload Balancer we can't tell easily which projects are running ahead or behind as there is no way to see the Priority. The Priority is a field in the Overview section on a Project under Basic Information that is an out of the box field. Today we utilize Flexible and Firm Deadline to know if the Creative Studio has more time or not for their task. They appear in green (Flexible) and red (Firm Deadline). How would you like the feature to work - If Priority was added as one of the Color Theme, then it would color code the projects on the Workload Balancer - green (Flexible) and red (Firm Deadline). Benefits - Team members can see which projects are most critical (green and red), fostering alignment and urgency. Color-coded priorities help visualize workload distribution and plan for capacity more effectively.Reduced PM time going back and forth between opening up every single project to see what the Priority is.Current Behaviour - Under Select Color theme, there are 3 options today:Default: The bars for all projects and their work items display in blue.Project: The bars associated with each project and its tasks change according to the name of the project. All tasks that belong to the project display in bars that match the color of the project. The project bars display in a lighter shade to distinguish them from the tasks. The project bars also include a project icon when choosing not to display allocations.Project Status: The bars associated with each project and its work items change to the color of the status of the project.The project status is that associated with the Group of the project. If the Group does not have group-specific statuses, the color of the work item bars is that of the system-level project status. Both system as well as custom statuses display. For information about group statuses, see Create or edit a group status.However, my team is asking for the Priority field to be added to this Color Theme options. 

Instance-Level Display Settings Management in AEM: Replacing Browser CookiesInvestigating

Request for Feature Enhancement (RFE) Summary: This idea proposes enhancing Adobe Experience Manager (AEM) by shifting the storage of display settings within Sites and DAM sections from browser cookies to an instance-level configuration. By managing display preferences (such as UI layouts or viewing modes) directly within the AEM instance, users can enjoy a consistent experience across devices and browsers without relying on client-side storage. This approach improves usability, eliminates cookie dependency, enhances security, and ensures compliance with stricter data privacy regulations. Use-case: Use Case: Unified Display Settings for Multi-Device Content Editors Scenario:A content author frequently switches between a desktop computer at work and a laptop at home to edit content in AEM. Currently, their preferred display settings—such as column view—are stored in browser cookies. This leads to an inconsistent user experience, as their preferences need to be manually reconfigured on each browser and device. Solution with Instance-Level Settings:By saving display preferences at the AEM instance level, the author’s settings are automatically applied regardless of the browser or device they use. The system retrieves their settings directly from the instance during login, ensuring a seamless and personalized experience. Benefits: Consistency: The same display settings persist across all devices and browsers. Efficiency: Eliminates the need for users to reset or reconfigure preferences. Privacy & Compliance: Reduces reliance on cookies, aligning with stricter privacy laws like GDPR. Usability: Provides a more polished and user-friendly experience for content authors and administrators. Current/Experienced Behavior: In AEM, display settings for users are typically managed on a per-browser basis using cookies or local storage. This cookie-based approach is functional but lacks flexibility and scalability for modern multi-device workflows and collaborative environments, making a server-side, instance-level storage mechanism a desirable enhancement. Improved/Expected Behavior: The expected behavior involves transitioning from a browser-dependent model to an instance-level storage model for display settings. This approach ensures a consistent, user-friendly experience across devices, browsers, and shared environments. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud service (All environments), Release: 2024.11.18598.20241113T125352Z Customer-name/Organization name: BORUSSIA DORTMUND GMBH AND CO Screenshot (if applicable):   Code package (if applicable):