Product ideas | Community
Skip to main content

10000 Ideas

AndrewQu2New Participant

Enable Duration and Planned Hours for Personal To-Do Tasks to Improve Capacity Accuracy in Workload BalancerNew

Description:Currently, users can add personal To-Do tasks either via the Home widget or by creating tasks directly within their personal To-Do List project. However, these tasks do not reflect planned hours by default and therefore are not factored into Workload Balancer capacity calculations, even though they may take up meaningful portions of an individual's day. This creates a disconnect between actual user availability and what project/resource managers see when planning workloads. For example, a user may be spending several hours on personal To-Do items (e.g., training, internal documentation, self-assigned initiatives), but still appear 100% available for project work in the Workload Balancer view. Suggested Enhancement:Allow users to optionally assign planned hours and durations when creating personal To-Do tasks—ideally directly from the Home widget interface or through a simplified entry form. This would allow the system to:Accurately reflect that time as allocated in the Workload Balancer.Provide project/resource managers with a more realistic view of team member availability.Reduce the need for manual workarounds such as navigating to the Personal Tasks project or embedding planned hours into task names.Optional Features for Consideration:Enable a toggle when creating a To-Do item to "Include in workload capacity."Allow admins to define whether these tasks can be visible to others (e.g., team leads or managers) or remain private.Improve visibility of these To-Dos in reports and dashboards alongside regular task assignments.Business Value:This improvement would help organizations more accurately manage resources and plan projects by ensuring that all time commitments, including self-managed tasks, are visible during capacity planning. It would also reduce overhead from workarounds, improve forecasting accuracy, and support better workload distribution across teams.

aanchal-sikka
aanchal-sikkaNew Participant

Automated Reporting Based on Metadata MatchInvestigating

Request for Feature Enhancement (RFE) Summary: The proposed feature aims to enable businesses to generate customizable, template-based reports by leveraging metadata criteria for assets stored in Adobe Experience Manager (AEM). These reports can be scheduled for automated generation and distributed to various platforms or teams. Use-case: Businesses often need reports filtered based on specific metadata values (e.g., region, asset type, product category). These reports are essential for: Supporting marketing campaigns by identifying suitable content. Generating insights for compliance or governance reviews. However, manually filtering and compiling this data is time-intensive and prone to errors. Automating this process would save time and improve data accuracy. Current/Experienced Behavior: We need to manually filter the content after generating reports for all assets. Improved/Expected Behavior: Report Templates: Admins can create and save report templates with predefined metadata filters. Automated Scheduling: Reports can be scheduled (e.g., daily, weekly, monthly) to run and generate outputs in standard formats like CSV, Excel, or PDF. Customizable Distribution: Generated reports can be automatically emailed or pushed to other integrated platforms (e.g., Slack, Teams, or SharePoint). Granular Access Control: Access to report creation and data is managed via AEM’s existing permissions model. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 Customer-name/Organization name: Mondelez Screenshot (if applicable):   Code package (if applicable):  

Provide the ability to dehibernate AEM Cloud Service Sandbox Environments through the Cloudmanager APINew

  Request for Feature Enhancement (RFE) Summary: I would like to be able to dehibernate my sandbox environments in a script using the Cloudmanger API (and CLI plugin). Use-case: My sandbox environments go down into hibernation daily, and once I get to development, I need to start the first, eating away 10 minutes every day.I would like to send the de-hibernation signals once i open my laptop in the morning - through a script using the Cloudmanager API or the aio cloudmanager plugin. I have tried to use the Call using from the CM-UI, but I did not get a positive response: Request URL: https://dev-console-ns-team-aem-cm-prd-n108153.ethos14-prod-deu6.dev.adobeaemcloud.com/api/releases/ns-team-aem-cm-prd-n108153/dehibernate/cm-p127553-e1403927 Path: /api/releases/ns-team-aem-cm-prd-n108153/dehibernate/cm-p127553-e1403927 Current/Experienced Behavior: Sanboxes are all hybernated, I have to spin them all up one-by-one manually. (this is very time-consuming ... and annoying!) Improved/Expected Behavior: When I open/start my laptop, the Sandboxes get dehybernated automatically through scripted calls. Environment Details (AEM version/service pack, any other specifics if applicable): AEM CloudSerices Cloudmanager (API) Customer-name/Organization name: CDA11DC661266AB70A495F8B@AdobeOrg Screenshot (if applicable):   Code package (if applicable):