Product Communities

I wanted to suggest an improvement regarding how we handle delegated issues in Workfront. As it stands, unless a delegate user takes ownership of a project, the delegated issue will only appear in their "my work" widget. This setup isn't quite streamlined enough for our needs. Could we request to have Workfront include delegated tasks in the "my task" widget as well? This adjustment would provide a more cohesive and efficient view, allowing us to better track and manage our responsibilities. Thank you for considering this suggestion. Looking forward to your thoughts on this matter.

What do we need:Create or update a user notification option that lets assignee(s) know when a task can start work!  (Can Start = True = Notification)                                        My Ask → Please Upvote this idea! There is currently not an option for users or admins to enable a notification to be sent to a user or team that is assigned to a task that lets them know that they can start working on a task; a trigger once the Can Start indicator on a task moves to True.   Users do not receive notifications that let them simply know they can start working on their task.   What’s available today in user notifications?   There is an option for “All predecessors of my tasks are completed” located in the Information about Work Assigned to Me section, but this does not always work and is not always accurate.  This runs simply off directly associated predecessors on a task.  If you manage predecessors at a parent task level, notification will not be sent to your users and affect your tea

Field Content Request for Feature Enhancement (RFE) Summary: Allow defining custom 404 pages per specific page or directory (path) so that only the designated scopes show a tailored 404, different from the site-wide default. Use-case: When users access 404s under landing pages (LPs) or other special sections, the site owner needs to show a section-specific 404 that provides targeted guidance (e.g., relevant links, promotions, or contact paths) appropriate to that section. Current/Experienced Behavior: It is not possible to create a dedicated 404 page for a specific page or directory. All 404 responses fall back to the global default, which cannot convey section-appropriate guidance. Improved/Expected Behavior: Enable configuration to display a unique 404 page only for the specified page/directory scope, while keeping the default 404 for other areas of the site. Environment Details (AEM version/service pack, any other specifics if applicable): Experience Manager as a Cl

Field Content Request for Feature Enhancement (RFE) Summary: Provide a Page List block that allows filtering by a specific path × specific directory, and supports listing non-HTML items such as PDF files and external links. Use-case: Content authors need to easily create lists such as news, column, and article indexes based on specific directories, and include non-HTML items (PDF files, external URLs) within the list. Current/Experienced Behavior: 1. It is currently not possible to generate a page list filtered by a specific path × specific directory. 2. Authors cannot easily include PDF files or external links in lists such as news indexes without creating dummy pages and setting manual redirects. As a result, page lists cannot naturally contain mixed content such as pages, PDFs, and external URLs. Improved/Expected Behavior: 1. Enable authors to generate a page list by specifying a directory × tag (or equivalent filtering criteria). 2. Allow authors to add PDF files

Request for Feature Enhancement (RFE) Summary: Improve the Columns block so that (1) opening Column properties immediately after adding a Columns block does not cause errors, and (2) components inside Columns can be moved freely between Columns blocks or between Columns and Section containers. Use-case: During authoring, editors frequently add Columns blocks and adjust Column properties before placing content. They also often reorganize page layouts by moving components such as Text or Button between Columns, or between Columns and Section containers. Current/Experienced Behavior: 1. Immediately after adding a Columns block, opening the Column properties before adding any inner content results in an error. 2. Components placed inside a Columns block cannot be moved to another Columns block or to Section containers, limiting layout flexibility and forcing authors to recreate content manually. Improved/Expected Behavior: 1. Column properties should be accessible without error

I am an Adobe and (now also) ai consultant in the fashion industry for over twenty years. I am absolutely stoked about Firefly boards and teach all designers i meet to work on it. There are two potential features that would make Firefly boards unbeatable. 1: The possibility to add style-guide information on a specific board or maybe a ‘project folder would be even better’. This will make Firefly boards instantly the number one ai tool for brands (not only fashion). 2: Integrated LLM of choice. I now teach designers to use their favorite llm to create detailed prompts for generating images and video on a firefly board. How nice would it be if there would be a sidebar with an integrated LLM. Even better if the user can choose their own favorite llm (please include Mistral for the European market).  

Feature Request | Allow exporting DAM usage reports from Assets View and Admin interface so that users (end user or admin) can export DAM usage reports and are able to share, analyze, or archive reporting data offlineReports can be exported from: Assets View page Admin interface Export reflects: Selected time period Applied filters Upload and download metrics Supported export formats include: CSV (mandatory) XLSX (optional / nice-to-have) Export includes metadata such as: Report generation date Generated by user Exported data matches exactly what is displayed on screen.

Currently Asset reporting statistics available only in Asset View interface. Enable admin users to access DAM usage reports from the Admin interface without needing to switch views so that  they can analyze assets usage across teams, brands, and regions.Admin users can access reporting from the Admin interface. Admin can view the same metrics as end users: Uploads Downloads Admin can apply all supported filters: Time period Brand, Sub-brand, Geo/OU, Agency, Adaptations, Master, Experience Admin visibility supports broader organizational scope (subject to role configuration). Reports load within acceptable performance thresholds for large data sets.

One challenge many users face across Adobe products is navigating documentation, tutorials, and community resources efficiently. Even though Adobe provides extensive documentation, finding the exact answer quickly can still require multiple searches across help pages, forums, and external tutorials.Proposed Idea:Introduce an AI Documentation Agent embedded directly within Adobe Help, product panels, and community pages.This agent could allow users to: Ask natural language questions about features or workflows Instantly search and summarize official Adobe documentation Surface relevant tutorials, guides, and community threads Walk users step-by-step through tasks directly inside the product Suggest related features users might not know exist Example Use Cases “How do I remove background noise in Premiere Pro?” “Show me how to create a gradient mesh in Illustrator.” “What’s the difference between Smart Objects and Linked Objects in Photoshop?” The AI agent could return: Direc

When a user copies a URL from within Workfront (e.g., via 'Copy URL' in the Documents folder menu), it pastes as a raw URL with no display name — exposing a long string of alphanumeric IDs that is hard to read and unprofessional when shared in tools like Slack, Outlook, or Teams.Current Behavior:Pasting a copied Workfront URL displays the full raw URL. Example:https://companynamehere.my.workfront.adobe.com/issue/11aa11a0001123456df123dfcc1e1234/documents?initialFolderID=11b01cbf00010123bb12345ac12d123dAdditionally, there is no 'Copy URL' option on project or task pages, so users have no native way to share a direct link to those objects, other than copying the raw links from the browser address bar.Desired Behavior:1. Copied Workfront URLs should carry a friendly display name on paste — such as the document name, object name + ID, or folder path + document name — similar to how Microsoft Teams handles copied links.Pasted Teams link comes with Display text2. A 'Copy URL' option should b