Build better products with our product team
We don't worry about the time of due dates. We've always looked at end of the day as the deadline. Yes, sometimes we have to stay late to get it done on time. Now we have Workfront (in our 4th month) and the planned completion date has a time portion, which has cause some issues for us. Tracking On Time delivery, even 3 minutes past is considered late. We only worry about it going out on the date it was requested due. (We've worked around this with a custom field on a report, using the "cleartime" function, to get accurate reporting for our needs)We have two teams, one in Minnesota and one in Chile. We have a lot of issues with tasks and time off sliding up or down a day on the schedule because of the time zone difference. Makes for a scheduling nightmare! (we can work around this by setting every project and task due date to be ie. 5pm, but that's yet another tiny detail for our PM's to have to not forget) We'd rather not have to work around these issues. Could there be a global setting to "clear time" on all projects, tasks and issues?
Description: It's pretty straightforward: Make it so the status field is editable on the My Requests widget. Why is this feature important to you: We are on a crusade to remove clicks wherever possible. Right now, if I want to change a request's status in the My Requests widget, I have to select the issue in question, open the preview pane, and then change the status there. These are two additional clicks, plus it feels like the widget is broken. (That was my first thought.) Although it's not The End Of The World if one has to use the preview pane, I anticipate getting support tickets from people who think the same way I did. How would you like the feature to work / Current Behaviour: See above.
Request for Feature Enhancement (RFE) Summary: Ability to disable the Publish functionality on Assets View Use-case: When using AEM Assets with Dynamic Media with OpenAPIs, the 'Publish' functionality is not relevant anymore as assets are published by 'approving' the asset. Current/Experienced Behavior: In an architecture based on Assets View and Dynamic Media with OpenAPIs, users see a Publish option, which is not supposed to be used. The Publish prompts occurs upon asset upload, which is confusing for the users. Improved/Expected Behavior: Ideally, there should be a configuration option to enable or disable the Publish feature depending on the the architecture needs. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service - Assets View interface. Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Currently if you need to make even the slightest tweak in a watch events filtering you have to delete the webhook and start again. It would be so much easier and save so much time, if we could instead edit the watch events setting like other Fusion modules
Description - After opening a support ticket, I've learned that only Sys Admins can create and activate new users with the new license structure. Users with Standard licenses can create new users, however any users they add to Workfront now require Admin approval to activate. Legacy Planner licenses did not have this extra step/limitation.Why is this feature important to you - We'd like the Standard license to have the ability to instantly activate a new user without requiring admin approval. This new limitation is adding an extra step to our workflow. It's resulting in delays as Standard users have to wait/remind admins to approve new users now. Additionally, the only work around is to make more people Sys Admins which is not ideal and it adds an additional risk.
Currently, multiple conditions seem to always take an "AND" operator- for anything "OR", I go to custom code. It would be very helpful to be able to use "OR" conditions.For instance, if I needed to have a condition like "if the pagename is 'home' OR the page type is "product details", I would have to resort to a custom code condition, or creating multiple rules.
Description - Do not make assigned tasks that are depended on predecessors visible Why is this feature important to you - Do no want to confuse assigned users if the tasks are not needed or ready to be worked on. But want to be able to assign the tasks in a task template so that it is a part of the task structure/workflow. How would you like the feature to work - We would like to assign a particular designer to tasks in a task template so that when a project is opened and the task template is attached, the tasks are pre-populated. If the tasks are not needed, the owner can delete the tasks, but if revisions are required, we want to make sure those tasks are assigned and made active once the preceding tasks are marked complete. Current Behaviour - All tasks with and without predecessors that are preassigned in the task template and used in a project are visible up in the designer's My Task and My Work lists.
Description - it would be nice if cohort tables displays same day (+0 days) returns. Why is this feature important to you - in our organisation, we like using cohort tables to see first-time email opens in a journey. In other words, email sends goes to inclusion criteria and first instance of email open goes to return criteria. Once the table is built, we can clearly see how long it takes to customers to open a email from a specific journey. This helps us to understand customer behaviour and works as a source to adjust journey steps. How would you like the feature to work - I would like to see +0 days (same day) as a column in the return criteria. Current Behaviour - currently, cohort tables columns starts from +1 Days
Description - Can we please get the right-click functionality for opening objects in new tabs back? Why is this feature important to you - It's nice to be able to open two windows at the same time How would you like the feature to work - Right click like how we used to have it Current Behaviour - It currently doesn't work and we have to use a work around that I have to explain to all new users with a CTRL +
Description - The limitation of 2,000 returns on the external look up field prevents us from being able to use master data for client names in WorkfrontWhy is this feature important to you - Using an external look up field to allow users to choose from a golden record for our client names would provide more robust reports in Workfront.How would you like the feature to work - We would like Adobe to increase this threshold as 2,000 returns is very limiting. A query search allowing more options would support our use of golden records for robust filtering.Current Behaviour - the look up field returns the first 2,000 lines only and ignores anything after that. Our master data platform can return up over 16,000 records in 1.8 seconds but they cannot be accessed beyond the first 2,000.
Request for Feature Enhancement (RFE) Summary: Currently we are not able to configure external github repositories to a Configuration deployment pipelines. When we add non-adobe github repo, it throws error `An external repository is not yet supported for this type of pipeline.` Use-case: We were migrating from internal TFS repo to enterprise github repository. We to point other pipelines: Code Quality, FullStack, Front End pipelines to external Git. Just the configuration deployment pipeline alone is blocked. Sounds like temporary limitation, it is intentionally blocked. Current/Experienced Behavior: When changing repository to external non-adobe, it is throwing error Improved/Expected Behavior: Configuration pipeline should allow external non-adobe github repositories Environment Details (AEM version/service pack, any other specifics if applicable): 2025.3.20133.20250325T063357Z Customer-name/Organization name: SouthernGlazers Screenshot (if applicable): Code package (if applicable):
It's can be so tedious to do a full clean up in Marketo when assets and fields are "used by." Marketo should introduce a more intelligent, guided deletion workflow for assets (like emails, forms, smart lists) and custom fields, even when they’re currently in use. The goal is to streamline the process and reduce the manual effort and risk associated with cleanup. Why This Matters:Fields and assets are often entangled across multiple campaigns, forms, and smart lists, making deletion tedious and risky.The current "Used By" view is limited and doesn’t always show full dependency chains, especially with nested assets or tokens.Custom fields are hard to deprecate fully. Even after clearing them from forms or flows, they remain blocked due to invisible references.Proposed Features:A “Smart Delete” tool that:Maps all dependencies (even nested ones) across the entire workspace.Offers options to replace or deactivate references in bulk.Includes a “safe delete preview” to assess the impact before confirming.Supports versioning or rollback in case something breaks.For fields: warns if the field is used in forms, filters, flows, or reports, and helps remove those references intelligently.
Hi all,Yesterday I found myself working on a report and I needed to get the bounce rate for a specific country. I already setup the calculated metric to get bounce rate, but then I realized that no option to use calculated metrics on reports from the data warehouse.I think there´s no way to do this, so that´s my proposal to be included on the platform.
Description - At present my understanding is that we are only able to see collisions information in Target by opening each activity, this is very time consumingWhy is this feature important to you - We have many experiments running at the same time often using the same website pages.How would you like the feature to work - A collisions dashboard that would show all of the activities running on a specific page.Current Behaviour - Currently I can only see this information by seperately opening each activity.
Request for Feature Enhancement (RFE) Summary: Introduce a built-in visual debugging tool in AEM Author to detect and highlight failed ClientLibs loading (eg. 404s, category mismatches). Use-case: AEM pages often break in layout or functionality due to missing or incorrectly loaded ClientLibs, especially during template development or after dispatcher/CDN deployments. Authors and content editors face difficulties identifying these issues quickly without browser dev tools expertise. Current/Experienced Behavior: Missing ClientLibs result in broken layouts, JS errors, or missing styles/scripts - but no warnings are visible to non-technical users on the page itself. Only browser dev tools or logs reveal these issues, making root cause analysis slow. Improved/Expected Behavior: AEM should highlight missing ClientLibs visually on the page, or provide a debugging overlay or console warning for authors. This should include category mismatch detection, permission issues, and HTTP error codes for assets. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service; observed in multiple environments with Dispatcher/CDN caching layers. Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK