Skip to main content

Filter by idea status

10000+ Ideas

MaryTr1New Participant

Move long Proof Comments conversations to the proof updates sectionNew

Description - Move long Proof Comments conversations to the proof updates sectionWhy is this feature important to you - Our teams love WF proof mainly for their ability to communicate with each other real-time via the proof comments. Some of those conversations can get pretty long. They are aware of the ability to take the conversation to the proof updates section - but they fare wary of leaving the actual proof (for some reason). How would you like the feature to work - In the case of those long conversations, it would be so cool if they could "send" the proof comments to the proof updates section once they have had their say. Leaving only the resolved comment. Current Behaviour - Proof users are reluctant to "leave" the proof to take long conversations into the proof updates section. Currently they have the conversations in the proof and then go through and delete all of the conversations, leaving only the resolved comment, or by starting a new comment all together with the resolved comment. This is time consuming and the supporting data is lost that way. We work with long technical documents, so there can be several 100s of comments per proof.They know of the "go to the last comment" feature, but working with outside composition vendors can be confusing to them, especially when documents/images have been added to the comments at random intervals throughout the conversations.Any thoughts on how to keep the comments' data intact, while making it cleaner and easier for wary users. 

projects in kanban boardNew

Hello,here's an idea that was already shared in the past. I would like to re-enter it for the development team, together with a workaround that might interest some of you, Workfront users and experts. The idea first: for all "traffic managers", it would be nice to have a kanban board with existing projects and some of their properties. The new boards have been developed for issues and tasks only, and we hope that the concept will be extended to projects soon. For the meantime, I've just implemented for one of our team a workaround, without interactivity (yet?), to display their projects in such a board, using Fusion. The scenarios are quite easy to create. The principle is to create issues corresponding to the projects (tasks can also be used in theory) in a dedicated project . A board is then linked to that project.A first Fusion scenario is watching for new projects and create corresponding issues = cards in the board (2 modules)A second Fusion scenario is wachting for changes in existing projects and updates the issues = cards (4 modules) With Fusion this set of information is visible in the issue card (directly in the Kanban view):- the issue name is the name of the projects. It is also possible to concatenate the name with other information from the project,- due date is the planned completion date. But it is also possible to use this field with any date,- estimation is the progress percentage (can get a value between 0 and 100),- status is the equivalent status for issue (not necessary the same) and determine the column of the Kanban,and most important (but not directly in the Kanban view but inside the card), description is the URL to the corresponding project.I also store the projectID in the URL field of the issue to keep the reference between project and issue. This is necessary for the second Fusion scenario above.  So it's currently only a passive view of the project. Making changes here will not interactively change the project properties (maybe with new scenarios?). But at least one can spot a project that needs a follow-up and go to that project with 2 clicks. And it's also possible to enter tags, like in a common issue/task board.

Year Filter on the search engineNew

The addition of a "Sort Results by Year" filter in Adobe Workfront would significantly enhance user experience and streamline workflow efficiency. As a user who regularly interacts with the platform, I find it increasingly challenging to navigate through a growing volume of data spanning multiple years. The existing date filters provide a useful range-based selection, but a dedicated year filter would offer a more intuitive and precise way to isolate and review information. This feature is essential for users like me who frequently need to track and analyze project progress, client interactions, and other critical data points year by year.The envisioned functionality is straightforward—integrating a simple dropdown menu or clickable interface where users can select the desired year would instantly organize and display results exclusively for that specific timeframe. This targeted approach would eliminate the need for manual date range adjustments and expedite the search process. Currently, users face the challenge of sifting through results from various years, leading to potential data overload and decreased efficiency.In essence, the "Sort Results by Year" feature represents a practical and user-centric solution that aligns with the evolving needs of Adobe Workfront users. It promotes a more refined and time-effective search experience, allowing users to focus precisely on the data relevant to a particular year, thereby enhancing overall productivity and user satisfaction within the platform.

elliemayberry
elliemayberryNew Participant

Quick Segment UpdateNew

Description - I have run into issues with quick segments. When copying a panel or a project, the quick segment copies over and changes on all versions of the copy when I change it. When I submitted an Adobe support ticket, it was explained that "Engineering teams have reviewed our case to find that the reasoning behind the changing segments is that quick segments operate similarly to standard segments in that once they are created they are assigned a specific segment ID. When copied, the copy of the report containing segments also ties to this same segment ID (so it's not a new segment calculated on the fly). As a result, each dashboard references the same overarching segment, so when the definition is changed in one, the change show in the other because ultimately each report is referencing a single segment ID."I believe the most ideal way for this to function should be that when copied, a new copy of the segment is created and referenced in the new report. This would allow the user to build similar reports and panels more quickly and easily without having to rebuild from scratch in order to avoid having linked quick segments. Why is this feature important to you - This would help me more quickly and easily build out similar reports for different segmentsHow would you like the feature to work - Ideally, I could copy something with quick segments and would be able to make changes to the quick segment in the copy without affecting the original.Current Behaviour - Changes in the copy change the original too, so I have to build from scratch. I am attaching a link to the closed support case for further clarification https://adminconsole.adobe.com/9DB302BE53306A270A490D4C@AdobeOrg/support/support-cases/E-001053848

Prevent Stale Meta Data Values from Mapping to AEM from Workfront via Native ConnectorNew

Description: When Workfront forms are filled out based on dependency rules and subsequently changed, the entries are retained unless manually cleared by the user before making any modifications. Otherwise, the data is retained and will carry over to AEM via metadata mapping when transferred. How would you like the feature to work: Workfront should not retain and send stale values to the DAM. Only currently selected/saved project information should map over to AEM. Current Behavior Example & Why It Matters: In our instance, we use custom fields to denote business group and business category. Our logic shows the user the applicable category field based on their choice of business group. Sometimes users click through the different business group and category options to review which options are available before they make a selection and save it on the project. If the user doesn't fully clear a category option that they clicked on, before switching to a different business group, the category option is stored and sent to AEM. As a result, Workfront sends all of the actual saved project selections for assets sent to the DAM, along with whatever stale values might have been selected and not cleared at project setup. This leads to incorrect categorizations (junk) showing up in the DAM. This will impact the accuracy of reporting and searchability in our brand new AEM DAM. We are clarifying our field options for users, but cannot reasonably enforce that they 'clear values' whenever they select something and then switch to something else.