Build better products with our product team
Description - Similar to allowing the addition of Tags or changing the Assignee, Board columns should allow the affition of or the auto addition of named Custom FormsWhy is this feature important to you - Data is often only required at stages as the item travels through the stages of a project and is often NOT required to be entered at the initiation of the item, additional information may be required to be added by a specific person. By facilitating the addition of a board combined with the assignment of the card to a person or team, the data will be entered at just the right point in timeHow would you like the feature to work - Add an additional option on the Column Edit under the Update Field Values Automatically, add an option for the user to select a custom form or in the board definition set the form(s) to be added. Could also do this in the same way as defining Members for a Board so that only a limited number of forms can be displayed on a particular Board. Bonus, it would be awesome if values in the form could be set based on being moved into this column. When setting up the custom form on the column you would need to have a switch next to each field to allow the value to either be maintained or to be set (similar to the switches for Project Preferences). If "Enabled" for a field, then the board would allow a value to be set. Bonus Bonus to this, is that the "Overview" or "Financial" fields should be able to be included as if they were custom forms with the same enablement. Bonus, Bonus, Bonus... Allow Project Level Forms to be included based on security, with the same "Enabled" switch on fields.Current Behaviour - Cannot add Forms
Would it be possible to move the Start Task bar next to the Log Time tab?Having this next to the Log Time tab would make it easier to remember to click the Start Task info and keep jobs on track.
Hi Team, If we have multiple programs in the instance and we want to move them to a single folder then we need to move each and every program to that folder. The drag-and-drop feature is helpful here, however, if we have a huge number of programs then this will consume more effort, so would it be possible to have a program multi-select option? This will help us in multi-selecting our assets and moving them all at once. Thanks
Allow "backwards integration" back into a Workfront project. I created a standalone board, but it lacked the full set of features available in project-based boards (more on those features below). I had to manually connect each card into the project. Also, each new card that is created cannot be connected, so I will need to manually connect new cards created by the team (if you use the "Create connected card" feature it only lets you pick from tasks in the project, but doesn't let you create an entirely new task)Allow document upload in standalone BoardsDon't let team members delete standalone BoardsEnable the Tags feature in project-based BoardsMake it easier to change the column names in project-based BoardsAdd an option that defaults each new card in standalone Boards to be connected to a projectAdd a "general information" section to standalone boards so that you can leave general information for the team (i.e. project description, general rules for using the board, links to folder locations, etc.)Allow filters for custom card fields (i.e. Priority)Enable reporting or at least export of data for standalone BoardsWhen you Group cards, it creates a redundant scroll bar that takes up spaceAllow the owner of standalone Boards to change the Status options (the seem to default to System Defaults)The standalone Boards load faster and have a better GUI than the project-based Boards, which seem to be buggy and load slowlyEnable notifications to be customized for standalone Boards
Request for Feature Enhancement (RFE) Summary: Image component loads rendition based on screen size, not target image size. Use-case: Google Lighthouse score complains that images are too large. Images should be sized depending on their target size. Our portrait thumbnails are loaded mostly at 1600 px width (based on screen size), although thumbnails only need to be around 500 px width across most screen sizes. Introducing the HTML "sizes" attribute did not solve the issue. The only thing that helped so far is to upload small-scale images for thumbnails. But we don't like that approach. Editors should not be required to think about images resoluition. They should just upload their high-res images and AEM Assets does the magic. Current/Experienced Behavior: Thumbnail-sized images are loaded at 1600 px and scaled down by the browser to fit into the target space leading to unsharp images or image artifacts. See attachments. Improved/Expected Behavior: The Image component loads a rendition that fits best for the target height and width. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: VERLAG DES OSTERREICHISCHEN GEWERKSCHAFTSBUNDES GMBH Screenshot (if applicable): See attachment. Code package (if applicable):
Description - Please add an option to sequential segments for After Current VisitWhy is this feature important to you - Using After 1 visit leaves a data gap of the next visit.How would you like the feature to work - Same as current sequential segments, but allow After Current Visit to optionCurrent Behavior - Limited to after 1 visit, which excludes the next visit. Here's an example from demo data
Request for Feature Enhancement (RFE) Summary: Allow AEM Folders and Assets Move in AEM Desktop Version 2.3.0 Use-case: Move Feature in AEM Desktop Application v2.3.0 Current/Experienced Behavior: Currently we are unable to move assets and folders in AEM Desktop application. Improved/Expected Behavior: Move feature should be allowed for moving assets and folders (individually at-least if not in bulk) Environment Details (AEM version/service pack, any other specifics if applicable): AEM Desktop Application v2.3.0 Customer-name/Organization name: TA Digital Screenshot (if applicable): Code package (if applicable):
I was surprised to not find this already in the idea exchange. Maybe its because I am on my 13th hour today.. so if this is duplicate please accept my apologies. One thing I have been very frustrated with custom forms is how the data fields are displayed once the form is rendered. In the custom form setup you basically have two options, do I want this field to be next to the one before it or do I want it to be underneath it. If you get too many side by side fields then it rolls over to the next line anyway. Even Microsoft Access lets you design custom forms on a grid. At least with dashboards you have the option of choosing some basic layouts (see image).Would it be so difficult to give us the same layout options for custom forms? So I humbly submit this idea - "Custom Form layouts". If you feel as frustrated with the look and feel of your custom forms I would appreciate your votes! Michael
Hi all,Thank you for submitting the idea and upvoting for it.After careful consideration and investigation of the impact the change will have on the overall system performance, we decided that it's not feasible to introduce the change at this point. We will re-visit this from time to time to understand if we are able to introduce the change. I apologise for the inconvenience this is causing on your side.Kind regards,Anna Asatryan,Product Manager, WorkfrontOriginal requestA task has a [recently completed] cross project predecessor (a predecessor task in another project), and is not "ready to start" in the My Work area until the overnight calculation has taken place or until the project timeline is manually recalculated. My users are a little agitated because those who use the My Work area would like to see their work update immediately rather than the next day. (Workers who use dashboards or rely on emails are of course unaffected, because those two types of notifications are instantaneous)Workfront support indicates that apparently it's normal to have to manually recalculate a timeline but since we complete over 2000 projects a year, and PMs cannot always track when someone has finished a task in order to recalculate a project timeline, it seems a little ridiculous to expect any sort of manual update/recalc.
Teams often want to brainstorm and begin to organize a list of tasks in something like Word and/or Excel. To avoid the cumbersome process of "uploading" the list into a project via a clunky kick-starter template, teams would like to easily copy the list of tasks from Word/Excel and paste them into a Project. Other programs they have used in the past have made this a common-practice approach. So, having a fast way to just copy and then paste a raw list of tasks into a project at any time would save time and decrease frustration/complaints.
When we create projects, we would like it to be easily identifiable by a docket number, something sequential eg 17-xxxx and should increment only by the specific object type eg Project. Unfortunately, the only available autonumbering available on Workfront is through all objects, meaning if I have 2 projects created, this could be 17-ABX1 and 17-1257 because of all objects created in between. We need this number to be sequential to the object only.
FEATURE REQUEST - Suggesting a new feature for the Analytics Data Connector. Please build the ability for the Analytics Data Connector to send Activity Map Data to CJA? Thanks you for the consideration. I5
Add a timer to Timesheets that helps to manually track time spent on a task.
Integrating the capability to bulk move Workfront Programs to a Workfront Portfolio is crucial for streamlining project management processes and enhancing user efficiency. The current limitation of manual, one-at-a-time processing for this task creates a bottleneck in workflow management. To address this, developers should prioritize the inclusion of bulk editing functionality for Workfront Programs, aligning it with the existing capability for Workfront Projects. This enhancement not only ensures consistency in user experience but also maximizes the utility of the platform. Potential implementation strategies include:Unified Interface: Design a user-friendly interface that allows users to select multiple Workfront Programs and initiate bulk moves with a few clicks.Customizable Filters: Integrate customizable filters to facilitate the selection of specific programs based on criteria such as status, deadlines, or assigned teams.Batch Processing: Implement a batch processing mechanism to handle the simultaneous movement of multiple programs, optimizing efficiency for users dealing with large project portfolios.Error Handling: Include robust error handling mechanisms to notify users of any potential issues during the bulk move process, ensuring transparency and mitigating the risk of data inconsistencies.Audit Trail: Incorporate an audit trail feature that logs all bulk move activities, providing users with a comprehensive record for tracking changes and troubleshooting if necessary.Assistance provided by an AI
Ultimately, it would be nice to have the ability to add fields. For example, adding the project number next to the project on the timesheet would be great.
Description - I'd like the ability to be able to create cross-project predecessors in project templates. Currently you're only able to create internal predecessors in templates. Cross-project predecessors are very powerful but can be time consuming to set up each time a new project is created and can cause user error if a person either forgets to set up the predecessor or does it incorrectly. Why is this feature important to you - Our users work cross-functionally very often and we'd like to be able to link tasks between the different teams without having to manually create the predecessors for every project. How would you like the feature to work - Ideally, we'd be able to set a cross-project predecessor on a task on Project A Template to a task on Project B Template. When a project is created from that template, I'd like to be able to either create a new project for all linked templates OR select an existing project to link. Example 1: Marketing creates a project using Template A that has cross-project predecessors for Template B (which belongs to the Sales team). On the 'Create Project' page, they have the ability to create both projects. Example 2: Quality has already created a project from Template B but didn't sets up any cross-project predecessors since Marketing hadn't yet created a project from Template A. When Marketing goes in to create a project from Template A, they have the ability to select an existing project to link their predecessors to (Quality's Project B).
Description - I would like the option to extend the Visitor Profile Lifetime up to 365 days Why is this feature important to you - This feature is important because on average our customers visit our site once every 6 months. Being able to have their visitor info from the last time we saw them would allow us maximize our ability to serve up a personalized experience even if we have not seen them for awhile. How would you like the feature to work - Current Behavior - We currently have our Visitor Profile set to the max allowed of 90 days.
Currently only one resolving items is allowed per issue. Most of the time we have more then one action to address an issue, so limit of "1" forces us to create weird workarounds such us creating a resolving task, with many subtasks, or a task with many issues, but then reporting on progress becomes cumbersome. If issue could have many resolving items, it would become easier to report by filtering items that have "this resolves" relationship defined and group by it.
When choosing field types to building custom forms, it would be very helpful to have the field character length for the text and descriptive fields designated as small, medium or large. The documentation provided on this is very general and just provides maximum character length. More specifics would help- https://experienceleague.adobe.com/docs/workfront/using/basics/update-work-items-view-updates/character-limits-in-fields.html?lang=en
The ability to grant permissions to add a new field, delete an existing field, delete existing field not used, add list of values, remove/disable list of values. Logic -- we typically have our "Super Users" the ability to create new custom forms and edit the fields. BUT I'd like the ability to limit what they can remove as it can impact other divisions.
We would like to see the ability for Group Admins to be User Admins WITHOUT being required to also give them access to DELETE users. Since Workfront allows users with logged hours to be deleted, we have already run into an issue where a user with time billed was deleted. And now we have no way to tell who those hours belong to, which has caused some probably with our revenue reporting. In order to avoid this in the future -- we removed the ability for our group admins to delete users. Unfortunately, when we took away the ability to delete users -- it then removed the User Admin access rights, as Create and Delete are both required to give that functionality. Now our group admins are unable to even add users, as they get an error stating they do not have access to the job role. They are also unable to edit the federation ID -- which we require as we have SSO enabled (as I assume most other enterprise level users do as well). We don't think you should be able to have access to DELETE users in order to successfully be able to add users and update federation id's. I suspect other large enterprise companies, especially those whose revenue recognition is tied to hours and users, will run into this issue where a user is accidentally deleted and then they have big headaches. If you have, please vote! If you have not already, please take this as a WARNING and a PLEA for help. :) ------------------------------------------------------------------------------------------------------ Below is the feedback we received from WF support about both of these: Job Role: The product manager over this area has let me know that to be able to assign a user a job role which you do not have yourself, you must either be a system administrator or a plan license user with the "User Admin (All Users)" access in your access level. Federation ID: The ability to delete users is not directly tied to the ability to edit the Federation ID. The ability to edit the Federation ID comes from the "User Admin (All Users)" checkbox in the Users section of the Access Level. Even if you have "User Admin (Group Users)", "Create", and "Delete" all checked, you cannot edit the Federation ID. The problem for you guys is that "Create" and "Delete" are mandatory with "User Admin (All Users)".
Currently you can only 'share' tasks and update their access when they're projects. I'd like to be able to do this on templates.
We really need logging on all objects and also on exactly what a user is doing once they log in. We need the ability to keep our systems up to date. Right now, I can't tell how often a report or dashboard is used - so I am not able to clean up items. (Even with Filters, Views, Groups -- I can't tell how often they are used, or not used.) We would like to know who & when someone accesses items - a report, a project, a portfolio. To push adoption, I need to know what a user is doing when they access. When a user logs in, what are they doing & when. I want more than just last log-in date. ex; I need to know if a user is only logging in once a week to log time on a timesheet, or are they using the application all week.
When you check the box for auto provisioning users as part of the sso process, there should be a selection called “Default access level when auto provisioning” with a drop down where you can pick from a list of the access levels you’ve created.
Create the functionality that allows you to manage and use tasks and sets of tasks consistently across the system without excessive manual effort (similar to to how you can edit a single field or a single form that can then be reused across multiple project template) 1.) Create a task library similar to the field library that allows you to manage tasks and choose to reuse them 2.) Allow admins to create custom "Parent/Child task sets" that could be added to a Project template just like you can add in multiple forms in the Project's custom forms section (ex: if you had a Parent Task for "Design Layout" with the 4 child tasks already made, you could just add the Design Layout task section to a new project or template without having to rebuild it) Building and maintaining consistent tasks across project templates is very cumbersome. For example, currently if we need to change the description or duration of the "Design layout" task we have to make the change on every template the task appears on (basically all of them). This is a huge lift.
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.
