Product Communities

When we convert an Issue to a Project, we can specify the intended owner of the Project. It would be super helpful if we had the same functionality when adding a Template to a Task, i.e., "Assign template tasks to the Owner of the parent Task" or something similar.

I actually expected the feature to work this way to begin with and was surprised to learn that it didn't. If I have an issue that is resolved by a project I would like that issue to display the planned completion date of the project. Nothing more complex than that.

Please consider changing the radio buttons to checkboxes so we can assign the same template to multiple Tasks at the same time (instead of having to do it one at a time).

This is a feature available in the legacy version of report builder, but not the new one. This feature is a tremendous help in doing reporting for fiscal time periods (WTD, MTD, QTD and YTD) through the previous day without having to manual work in Excel in the form of creating a fiscal calendar reference table, which would then need to get manually updated every year as well. This is an overview of how/why I used this feature:My reports are scheduled to send early in the morning, with reporting through previous day. Our Adobe instance is set up to use our fiscal calendar, and I use fiscal dates for reporting. The issue I have would be when the report is run on day that's the first day of a new fiscal period because I would want this report to actually run the data for the fiscal period that just ended. For example, our weeks start on Sunday. When the report is run on Sunday, I want my WTD reporting to be for the previous Sunday-Saturday. With new report builder, if I just have my week

Description:Introduce a feature in Adobe Real-Time CDP that utilizes machine learning to predict customer churn based on real-time behavioral and transactional data. The system would allow marketers to define churn-risk thresholds and automatically activate personalized retention journeys (e.g., email offers, push notifications, or loyalty incentives). It would also maintain a version history of churn prediction models for transparency, comparison, and improvement over time. Why is this feature important?Increases ROI of marketing campaigns through targeted retention efforts.Enables real-time action, which is crucial for saving at-risk customers.Provides transparency and iterative improvement through model versioning.Supports personalization at scale with minimal manual effort.Reduces revenue loss by proactively identifying customers likely to churn. Current Behavior:Adobe Real-Time CDP allows segmentation and audience activation, but lacks built-in churn prediction and autom

Today it is only possible to include the audience status. Including 'Segment name' and 'Segment ID' is useful directly in the .csv shared, if the receiver platform can't read off of the file naming, but can only evaluate input from the file itself.

Enable the option of configuring a source/destination account after it have been configured, such as changing and/or at least viewing the bucket name, folder path, fily type, include manifest toggle and compression format which is a part of the wizard when setting up the account, instead of having to create a new one.

The folder possibilities for storing Audiences in a folder structure has become a nice function. It save a lot of time to find your right Audiences when you dont know exactly the name. I would like to expand this functionality to also be able to use for Offers and Journeys. It will makes it easier to find what you are looking for. To be able to work even faster it would be nice with  f ex a button in/on every folder that with one click could open the folder tree from where you are standing/clicking. It is nice with the tree but we still need to go inn and out from the folders to fint what we are looking for it we operate with a deep folder tree. 

Description - make WF CC or BCC me when I submit an update, or some kind of warning that I have "draft" updates... Why is this feature important to you - so that I know I actually hit "submit" after entering information that is intended to go out to the requestor or team- and that I don't come back to my desk Monday morning wondering why no one has responded, and then I open WF and dig into the request queue, and open the actual "updates" tab, and discover an unsent "draft" . but of course that's never happened. How would you like the feature to work - as above. either CC or BCC myself upon hitting submit, so I can see in my email that I sent a message... or a warning that I have unsent messages... or both.  Current Behaviour - if I navigate away from an update without hitting "submit" ... it just sits there. and if I go get coffee and start working on something else- perhaps I go to the "request details page to make sure I am not missing important details... and th

Project, Task, and Issue priorities are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.

Project, Task, and Issue conditions are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.

Let me know your thoughts on cross platform / App tracking I have developed a Cross-Domain & Mobile User Tracking Platform 🧠📱💻In today's fragmented digital world, understanding our users across websites, apps, and devices is no longer a luxury—it's a necessity.That’s why I’m excited to share what I’ve built:👉 A privacy-aware, cross-domain + mobile user tracking platform Designed for marketing teams, data analysts, and tech-driven businesses that want a unified view of their users — no matter where they come from.🔍 What it does: ✅ Tracks users across multiple domains and platforms✅ Links mobile app sessions with web visits in real time✅ Offers a beautiful, customizable dashboard with rich filters, analytics, and export options✅ Supports GDPR-compliant tracking and real-time logs📊 Whether you're running multiple brands, client websites, or want to boost your personalization strategy — this platform puts identity resolut

It would be great if Marketo had an API endpoint for managing fields, such as hiding them.For example, we have dozens of fields that we need to hide that are unused, and it is time-consuming and tedious to hide them one at a time.

Description of change you want to see:I would like the ability to expand or collapse the various top and side interface elements on the Adobe Workfront home page—specifically, the Adobe unified experience bar at the very top, the Workfront top navigation bar, and the "Home and Priorities" left-side panel. Currently, these elements take up significant vertical and horizontal screen space and cannot be hidden or minimized.Why is this feature important to you:This feature would greatly improve usability and workspace efficiency. The persistent interface elements reduce the available area for viewing and working on tasks, especially on smaller screens or laptops. Having the option to hide or minimize these sections would allow for a cleaner, more focused working environment and improve the user experience—especially for users who spend most of their time within the task list or dashboard views.How would you like the feature to work:I would like to see collapsible or toggle-able interface s

Description - I have a field that I would like to duplicate and rename without having to create another field manually. Example - I need to manually create fields with drop down options on the open/close time for one of our specific locations (this can get extensive when building it out for each day of the week).  Why is this feature important to you - It would save me a ton of time when building out custom forms. How would you like the feature to work - Have an option within the custom form area to copy existing fields (and rename them) similar to how you are able to do this with templates, projects, tasks, etc. Current Behaviour - Inability to copy custom fields (need to manually create each).  

Description:Introduce the ability for multiple users to collaboratively build and refine audience definitions in Adobe Real-Time CDP with support for version history, change tracking, and inline comments.This feature would help cross-functional teams (marketers, analysts, data scientists) work together more efficiently while ensuring traceability and reducing errors in audience logic. Why is this feature important to you:Audience building often involves multiple team members, and right now, it’s hard to track who made what changes or why.Sometimes, edits overwrite each other or lead to confusion without proper documentation or context. How would you like the feature to work:Each saved audience should include a version history, showing what was changed, when, and by whom.Users should be able to leave inline comments on specific filters or conditions (like commenting in Google Docs).Rollback functionality should allow users to restore a previous version if needed.Notifications

Request for Feature Enhancement (RFE) Summary: .aex & .aep (Adobe After Effects ) files are not supported in DAM today. Requesting to extend the support to these file formats Use-case:   Current/Experienced Behavior: .aex & .aep (Adobe After Effects ) files are not supported in DAM Improved/Expected Behavior: .aex & .aep (Adobe After Effects ) files should be supported in DAM similar to .ai files.  Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 & Cloud Customer-name/Organization name: Mondelez Screenshot (if applicable):   Code package (if applicable):  

Request for Feature Enhancement (RFE) Summary: Request to add functionality to make the default workflow package name unique to prevent collisions when multiple users execute "Publish Now" simultaneously. Use-case: When multiple users manage publication using the "Publish Now" option at the same time, the default workflow package name is duplicated, causing conflicts. This results in publication failures and error messages displayed to users. Current/Experienced Behavior: A conflict error occurs because the same workflow package is used in multiple requests when they are made simultaneously. As a result, the following errors occur:  - "Not enough to manage publication" is displayed to users Improved/Expected Behavior: The expected improvement is to ensure the default workflow package name is unique, preventing conflict errors. For example, the workflow package name could include the user name and current UNIX time to guarantee uniqueness. Environment Details (AEM ver

Request for Feature Enhancement (RFE) Summary: Ability to bookmark things in AEM Author Use-case: All types of Touch UI activities Current/Experienced Behavior: Not often you can find yourself working on mid or long term implementations of features if you are a developer, or often working on a specific set of pages and assets if you are a content author, or continuously doing regression testing on specific points of the solution as a tester, or purely having to do only with a small portion of "everything" and not usually go in the entire content or solution all the time.In these often situations I found that the person working on that specific area tends to have lots of browser tabs opened, trying to go back and forth between them to do their work, to do investigations, trying or find things out, oftenly doing mistakes or forgetting where things were, and spending lots of time to untangle stuff and to make sure he is looking in the right place each time before actually addressin

It Would be nice if I could rename a variable in Analysis Workspace for a specific project.For example, I just created a simple report for a colleague of mine looking at tracking codes and the number of clicks. For number of clicks I used 'Tracking Code Instances'. As a regular AA user, I understand what Tracking Code Instances means but someone who isn't a bug AA user might not know what it means. So, it would be good if I could right click on the metric and have an option to rename it. This renaming would only exist in the specific project.Thanks.

Description - It would be nice to have at profile-level the amount of emails each profile have received and opened in the last 30 days.Why is this feature important to you - It would be possible to address journeys based on communication-engagement withouth having to do it at audience-level. How would you like the feature to work - a computted attribute that returns the count of emails a profile have received/ opened in the last 30 days, something link:xEvent[_experience.customerJourneyManagement.messageInteraction.interactionType in ["open"]].count() Current Behaviour - Computed Attributes currently do not support System generated datasets

Description -Why is this feature important to you -keeping track of individual sub-tasks inside a task or requestHow would you like the feature to work -I'd like to have checklist that either automatically generates from a list of items entered by a requestor, or manually entered by me (or someone) upon receiving the request. this would allow me to verify with the requestor that I have all required sub-tasks on my "to-do list" for each request, and to track my progress before sending back. also allows identifying items that are incomplete or have outstanding questions.  Current Behaviour -requestor checks boxes in pull down menus, or selects radio buttons, and then a fairly hard to organize page is generated. also there are several locations to add "additional comments", which are a useful way to get details communicated- (not everything fits in a menu). but to be useful to me, I need to organize this information in a way that fits into my workflow. punchlists are a common pr

It would be a great feature in journey design, if read audience based journeys can be scheduled at different dates. Basically schedule follows a irregular pattern. Journey could be triggered on 11th of Jan, 17th of Feb, 25th of Mar, 15th of Apr and so on. We understand one can use business events to trigger the journeys at different dates OR use a time condition journey. But it will be a cool feature to configure different dates in the journey.

We would like the capability to configure the visual view of reports in our Dashboards.Currenlty each report has horizontal space for;- Tabs Menu (Details / Summary / Matrix etc.)- Options (export, lookup, Gantt etc.)It would be great if these lines could be configured, as they take up a lot of space and are not always required by the users.See the attached image for an example of the space that these unused rows are taking up in one of our Dashboards.For this particular Dashboard / Team, 'Details' is not required on the majority of reports, as there are no other tabs and 'export / search / Gantt' would also not be required on the majority of the reports for this team. It would be great if there was an option to configure these lines to create a better visual and make better use of the Dashboard space.Thanks

In the Omniture Legacy UI,  there is an option to expire a user after a set amount of days (I have a screenshot I can provide). It would be helpful to be able to utilize the same functionality within the Admin Console, specifically Adobe Analytics, to ensure that external users are expired after a certain number of days (ideally 6 months), but ONLY if they haven't had any activity in the last 6 months.By having to expire every external user after 6 months, we are facing many users being locked out every 6 months, requiring our User Admins to unlock them, as well as not allowing them within the tools in the interim. If we changed the solution to only expire the inactive users, we would prevent time lost and would properly expire only those who required it. ----------------------------------------------------------------------------------------------------------------------------The customer, General Motors, requested a product enhancement for Adobe Analytics to automatica