Build better products with our product team
DescriptionWe need a way to reassign all open and completed tasks from a deactivated user to an active user in bulk. Why This Feature Is ImportantWhen an employee leaves the company, there is currently no method to transfer their tasks directly from their profile. This creates administrative overhead and risks losing visibility on critical tasks that may still require action or tracking. Proposed FunctionalityUpon deactivating a user, the system should prompt the administrator to select an active user to whom all open and completed tasks will be reassigned. This should occur automatically as part of the deactivation process, minimizing manual intervention and ensuring continuity of work. Current BehaviorThere is no built-in functionality to support bulk reassignment of tasks from a deactivated user.
Description - My managers cannot log time via the Hours subtab unless granted admin access. I need my managers to be able to log time for their direct reports to ensure we are tracking time to the best of our ability. Why is this feature important to you - I need my managers to be able to log time for their direct reports, especially when sometimes workers are away on shoots. The responsibility is always on the worker but if they are having status meetings and reveal the information why not help them out and allow managers to log on their behalf? How would you like the feature to work - The feature would work identically to those with admin rights to timesheets. When the user goes to the hours subtask on a work object they will see a log time button. From there they can select themselves or anyone that reports to them and log hours for a specific date. Current Behaviour - I set managers to their own access level and grant them admin rights to timesheets. As you can imagine, this is not ideal since this gives all managers the ability to edit any time logged in even if it is not by someone on their staff. Although the odds are low that someone would abuse this power, I prefer not to open ourselves up to the chance.
Description - I would want to receive customized alerts dashboards. Imagine clicking "Analyze Further" and it shows supplementary information for each alerts so users dont have to manually dig deeper.Why is this feature important to you - This would alleviate a lot of the work and troubleshooting required once an alert is triggered.How would you like the feature to work - we configure a specific dashboard to be sent along with each alert. Current Behavior - We only receive the default alert analysis which shows the last 30 days or longer of the underlying metric trend
Description:Add a built‑in Data Quality Dashboard in RT-CDP that continuously monitors incoming streaming data for schema deviations, missing key attributes, duplicate records, and outlier values. When anomalies exceed configurable thresholds, trigger:Automated alerts (email or slack)Visual drill‑downs showing the offending eventsGuided remediation steps (e.g., map this unexpected field, fill missing email, merge duplicate IDs)Why is this feature important?Proactive Hygiene: Catch ingestion errors the moment they occur, before they corrupt unified profiles.Faster Troubleshooting: Teams spend less time hunting for what broke in the data pipeline and more time fixing it.Higher Confidence: Marketing and analytics users trust that every profile and audience segment is built on accurate, complete data.
When someone is granted access to a report, project, issue, etc. Workfront generates an automatics notification outlining what the object is that the user is being granted access to and who is granting it. It would be nice to be able to add a custom message to explain what the object is and why the person is getting access to go with the notification.
We would like an option to clear selected Mentions once an update has a response. Currently the Mentions Widget retains mentions and it is hard to sort through them to determine what needs follow-up. It would be nice to have the option to clear or hide selections Mentions once an update/reply has been made.
Description - Right now, the People tab of a project is not dynamically updated to people actually in that project. Anytime someone is added to a task or issue in the project, they are added to the People tab (or are the PO or other reasons). But then they remain in the People tab even if they are removed from the project tasks. Why is this feature important to you - If users are opting into emails for 'updates about projects I'm on' then they are getting these unnecessarily. This is a big issue when it comes to projects that act as the projects receiving issues/requests - those projects will never go away as long as we have the request queue feeding it, but more people are randomly added to the project and after a while they aren't needed to be there but are still getting the notifications.How would you like the feature to work - The People tab should be a reflection of the current state of the project, and should not include users who have been removed as assignees. Current Behaviour - Users are added to the People tab when assigned to a task or issue, but if a user is removed as an assignee, they remain on the People tab.
Description - Would love to have the option to pin and unpin a certain update to the top of the updates thread. This would allow for easy visibility on the most up to date items, etc. Would also love the option to filter updates by date, time, etc. to quickly search through and locate a certain update. Why is this feature important to you - This would increase productivity within the Workfront platform tremendously and would avoid confusion and clearer communication with cross-functional partners looking for information via updates. How would you like the feature to work - A button that says "Pin" next to "Reply" and " Like" - Once pinned there would be an option to "Unpin" For the filter, some sort of filtering option at the top right of updates then you can click and customize certain date, time, latest comments, etc) Current Behaviour - Updates are ordered in the time in they are posted, and all replies and updates are not able to be customized at this time making it difficult to find important updates.
Description - It would be much nicer the Edit Text Mode button enabled editing in the main windows instead of having to put it in the tiny popup window that appears. Why is this feature important to you - The edit popup is so small you can't really use it. You have to do your editing in an external editor and past it into the popup How would you like the feature to work - upon clicking "Edit Text Mode" the main window where you can see the code should be enabled for editing.
Description - If your text mode code includes a long line(s), the window widens to the point that the Edit Text Mode button isn't visible on the screen, making it easy to think that the button doesn't exist, especially since the code wraps in the edit popup window. Why is this feature important to you - multiple times we've had users think there was a bug because they couldn't find the button How would you like the feature to work - The button should always be visible on screen
Description / Current behaviour:If a Task has Revenue Type = Role Hourly [With Cap / Plus Fixed] setting, the Planned & Actual Task revenue is calculated with the Billing Rate associated with the Assignment Role(s) of the Task.The Billing Rate applied may be the default one set on the Job Role, or one that is set on the Company / Project for that particular Job Role.If a Task has multiple Assignments, revenue is calculated for each of them separately (using Assignment Role) and then summed.For User Assignments (as opposed to Role Assignments), the Assignment Role (labelled as "Assignee's Role" on the UI) can be (only) one of the Job Roles associated with the assigned user.The following business problem exists with this scenario:A task is planned with Job Role X and sold to a client at a price calculated with Job Role X.Given task is assigned to a user with Job Role Y (since a user with Job Role X is not available)The Assignment Role will be Job Role Y, i.e. the Job Role of the User.Workfront calculates the planned / actual revenue of the Assignment using the Job Role of the user (Job Role Y).Consequently, the planned/actual revenue of the assignment (and of the Task and Project) is incorrect, since the correct figure would be calculated using Job Role X.How would you like the feature to work?When editing Assignments of a Task, any active Job Role can be specified as "Assignee's Role" not only the Job Roles associated with the assigned user.The planned / actual revenue for the assignment is calculated with the Assignment Role (as it is now).Role Hourly revenue can be calculated with any role, not only with one of the assigned user's own roles.For convenience, project level default assignment roles can be defined for each project team member.If a project level default assignment role has been defined for a user, when that particular user is assigned to any task on that particular Job , the "Assignee's Role" (Assignment Role) on the new Assignment will automatically be set to the user's project level assignment role.It should be possible to manually change the Assignment Role to any Job Role.When setting a project level assignment role for a user, the Assignment Role of this user on this project on existing Assignments is not changed.Configuring project level default assignment roles can commence either on the "People" tab of the project or in a new Column labelled as "Default Job Roles".Project level default assignment roles can't be date effective. They apply to the project regardless of the date.The proposed way of working will be really critical to our new core design!
Description - Currently deleting archived cards is a method to improve board performance. Rather than manually deleting one-by-one there could be a setting that controls what & when archived cards are auto-deleted by the systemWhy is this feature important to you - It takes time to manually delete a card one-by-one, and one has to remember to do so.How would you like the feature to work - This feature would mimic the existing archive setting where you could control when a card gets deleted (# days, # weeks etc) (see screenshot)Current Behaviour - There is no automation.
We'd like to have the option to apply contouring (i.e. edit the distribution of the allocated hours per day/week/month) to tasks & issues in the "Unassigned Work" section of WLB. The UI would be the same as that in the Assigned Work section. A task's resource needs fluctuate during the span of the task and it is often known before a user is assigned but can't be captured via the Workload Balancer UI at the moment. This would make resource planning easier and more real-life.
Description - I want to create additional rules for marketing channels but it says rule 4. Even if i create one more it says Rule4 only. It might be a bug. How can I reference these if names are same.Why is this feature important to you -Even if i create one more it says Rule4 only. It might be a bug. How can I reference these if names are same.How would you like the feature to work - add edit option to rename the ruleCurrent Behaviour - no edit option
Description: The Search UI has recently changed in Workfront removing both the ability to simply close window when finished searching to return to the page you were on and the ability to have your search filters per object type persist.This change impacts our user base negatively enough that we assumed it was a bug and I put in a support ticket. I've received the following response: What Changed in the Workfront Search UI?Full-Screen Search: The Advanced Search is now a full-screen experience. When you open the search, it overlays the entire page.No Close Button: The new design does not include a close (X) button to exit search and return to your previous page. Instead, you must use the browser’s back button.Navigation Impact: If you perform multiple searches or add filters, each action adds to your browser history. Returning to your starting page (e.g., a project) requires multiple clicks on the back button, which can be cumbersome.Consistency: This behavior is the same across Chrome and Firefox, on both Windows and Mac. Why Was This Changed? According to Adobe Workfront’s official documentation: The Advanced Search is now full screen. You must navigate away from the page rather than closing the dialog.This update is part of a broader interface modernization effort to make Workfront more consistent with other Adobe applications. However, it has unintentionally reduced usability in this area. Known Limitations and User ImpactThere is no way to simply “close” the search and return to your previous context. The filter is not prepopulated and does not persist after a refresh. The only way to return to your previous page is to use the browser’s back button, which can be tedious after multiple searches or filter changes. This affects all users and is not browser- or OS-specific. Workarounds & RecommendationsUse the Back Button: For now, using the browser’s back button is the only way to return to your previous context. Open Search in a New Tab: As a workaround, right-click the search menu and choose “Open link in new tab” (if available), so your original page remains open. Why is this feature important to you: Being able to simply close the search window when done searching is the simplest most efficient user journey especially if you are trying to eliminate user clicks as much as possible. Right now, with the update in place, if you perform a search and then add multiple filters in order to narrow down your search you will have to have either remembered to open a new window/tab for searching alone or will be forced to click the back button in your browser multiple times to return to your original page. Filters you set no longer persist to the next search which necessitates this multiple iterations in the search window every time you use it unless you want to use a simple, very generic search and not drill down past the first page of results If this is aligned to how search works in other adobe products, search should be updated across their whole product offering because this experience is terrible.How would you like the feature to work:1) Primary concern: Bring back the close button so you can simply close the search window at any time to return to the page from which the search window was opened2) Secondary concern: Allow filters to persist in the search window
Description:Adobe Campaign Classic (ACC) does not currently support the <amp-img> tag used in AMP mailers when uploading HTML content via the Browser folder option in the Email Delivery template. As a result, image paths are not updated to hosted URLs correctly, causing issues with rendering AMP emails.Why is this feature important to you:We are increasingly using AMP mailers to deliver richer and more interactive experiences to our customers. Manual conversion of <amp-img> tags to <img> tags is time-consuming, error-prone, and not scalable for larger teams or frequent campaigns. Supporting AMP-compliant tags like <amp-img> natively in ACC will streamline our workflow, reduce turnaround time, and improve accuracy.How would you like the feature to work:We would like Adobe Campaign Classic to automatically recognize and process <amp-img> tags when AMP HTML is uploaded via the Browser folder option in Email Delivery. The platform should update the src attribute in <amp-img> tags in the same way it currently handles <img> tags, enabling proper hosting and rendering of images in AMP emails.Current Behaviour:Currently, ACC only processes standard <img> tags for image URL rewriting. When uploading AMP HTML containing <amp-img>, the image paths remain unchanged, which breaks proper rendering in the final email. As a workaround, we manually replace <amp-img> with <img> before uploading, which enables URL rewriting but compromises AMP standards and is not ideal for production use.
Description - After Adobe Admin Console migration, external users created in Workfront need to be approved by system administrators, otherwise their accounts won't be active, and they won't be able to use Workfront. This is very time-consuming especially for larger organizations with 6k+ users. So, we would benefit from having an "action" available in Workfront Fusion that would automate the approval process for us.Why is this feature important to you - This will eliminate the manual effort of approving every user created in the system on daily basis. It will save time for the system administrators to look for the approvals daily and approve. It will also save the waiting time of the user, so they don't have to wait for approval to be able to use Workfront.How would you like the feature to work - an Action should be available in Workfront Fusion in the Update record -> "User" record type, so it can approve the users automatically.Current Behavior - at the moment when external users are created in Workfront, they stay deactivated until an admin goes and manually approves them, only then they become active and can start using Workfront.
Request for Feature Enhancement (RFE) Summary: Introduce the Apache mvnd (Maven Daemon) wrapper in Adobe Cloud Manager so that the build step can reuse a long-lived JVM, parallelise module compilation, and dramatically cut cold-start overhead. This change targets only the build phase; the deploy phase likely remains untouched. Use-case: Large, multi-module AEM as a Cloud Service projects (often 10 + modules) can spend several minutes just starting Maven and resolving plugins for every pipeline run. In busy CI/CD setups (feature branch builds, frequent merges, scheduled quality gates) these wasted minutes quickly accumulate, slowing feedback loops and consuming CI minutes. Current/Experienced Behavior: Cloud Manager invokes the stock mvn CLI in a fresh container for each build. Each invocation spins up a new JVM, scans plugins, and builds modules sequentially. Typical build duration for a representative 10-module project: 9–11 minutes, of which ~1-3 minutes are Maven start-up and plugin scanning. Developers compensate by using mvnd locally, but must still wait for slower pipeline feedback. Improved/Expected Behavior: Cloud Manager containers start an mvnd daemon once, then execute build goals through the daemon for the lifetime of the build step. Parallel module compilation (default --threads=auto) and reused class-loaders remove the repeated start-up cost (potentially the resources of the build-pod(s) need to be increased to provide more CPUs to work with in parallel). Anticipated build-step time-savings: 25-40 % on typical AEM multi-module projects (confirmed in local benchmarks and community posts). No impact on deployment logic; output artefacts (all-, ui.apps, ui.content) remain identical. Environment Details (AEM version/service pack, any other specifics if applicable): ---- Customer-name/Organization name: ---- Screenshot (if applicable): ---- Code package (if applicable): ---- Maven-Deamon (mvnd): https://github.com/apache/maven-mvnd Article: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/speed-up-local-development-in-multi-module-aem-projects/ba-p/738507
Occasionally, we have a situation where a lead is accidentally deleted or merged with the wrong record. When this occurs, we can restore most of the data including acquisiton program and date, program memberships with successes and dates, etc. However, we cannot restore the cookie association because the cookie ID is not exposed on the lead record (or its exported data). Please expose the cookie ID, so we can use the technique described by Jep in the Discussion item (Is there a way to reassociate a cookie with a lead record without the lead taking another action?) to reassociate their cookie with the restored lead record.
I've had a couple of clients now go to delete a My Token on a program only to be told the token is in use. Unfortunately there's no easy way to determine how the token is being used.This is increasingly important since tokens can now be added to Guided Landing Page templates and as long as the template is in place and approved it will prevent the deletion of the token.It would be nice to have a "Used By" column for My Tokens, just like any other asset in the design studio.
It turns out program tokens can be in use in very strange ways, which makes it a necessity to have the "used by" functionality for program tokens. A use case I came across today: Original token is set up in a campaign folder. Someone erroneously made changes to the inherited token in a program that was stored inside that campaign folder. The program with the incorrectly overridden token was then cloned to an entirely different campaign folder. The cloned program retained its reference to the erroneously overridden token in the source program. Therefore, when we tried to remove the token this was not possible as it was still in use. We needed Marketo Support to trace where that was, because in the UI it was impossible to figure out. Although it can be argued that the link to the original overridden token should be broken in the cloning, providing visibility on where a program token is used prevents this confusion already quite well.
It would be great to see a list of places throughout a program where your program tokens are being used.Even if there was some way to run an audit to do the same thing that would work as well.This would help to know if tokens are no longer being used or to see if there are any other places it is being used that are not initially apparent.
WorkFront has no ability to 'undo last action' - in some cases this can be very troublesome - as it is quite easy to make a change to basic project behaviour, critical path and end dates. An 'Undo' last change function would be very useful if the Project owner has in-advertantly made a change that has caused multiple activities to be impacted. Even a - revert to last saved version function might be useful - at least allowing the project owner to go back to a version that they have already reviewed and approved with their team.
Usually name of variables / metrics / segments, but also their value, are something really technical. That kind of values absolutely do not suit the needs of top management who cannot read technical description.Also, when we do complex workspace the name of column is hidden because no space available in layout. So, why dont allow to overwrite and change color of any string we have into column/row head or cell?
Description - Add field to capture the entry date of a report similar to the entry date of a issue, project, task, or user. Why is this feature important to you - This is important because I need to know how long a report has been available to be used. This helps tell the story of high quality reports that can be duplicated/copied for other users across my instance and peer customers of Adobe Workfront. If a report has been around for years and was recently modified that highlights importance and emphasizes need to secure it and have it monitored for quality control. The reports in Adobe Workfront are often used to drive key business decisions and knowing every aspect about a report is critical to data governance and management. How would you like the feature to work - Users should be able to add the field as a column (view), filter or grouping in similar manner as an entry date for a project, issue, or task. Current Behaviour - The field is not available in Workfront UI or API Explorer. @skyehansen
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
