Product Communities

If a project is cancelled, all of the issues that are associated with the project become moot. However, the issue statuses do not change. It would be great to have the issues automatically get cancelled if the project gets cancelled. Then the owner of the issue wouldn't have to re-open the project, cancel the issue, and then re-cancel the project just to get the issue to be closed out.

Right now when you want to search for all teams with % in the Teams section, all teams show even if they aren't agile teams. We don't want anything mistakenly put in backlogs that aren't used, so it would be ideal if only agile teams would show in this section.

Currently, you have to go in and check on the status of the approval. It would be ideal to receive a notification for a rejected approval.

When entering a user story, there is a description box at the top that is not able to be removed. It is confusing for team members because we have another description field in the custom form that is for the "As a ___, I want, [goal]." traditional user story form, but having a subject, description and that section is confusing for team members. It would be helpful to be able to be able to get rid of this field.

Prior to pulling a story into an iteration, during the backlog grooming session, we go through stories and check the ready checkmark to ensure they are ready to be worked in the iteration. We don't need the checkmark checked when the story is entered because the team has not yet vetted the story to ensure completeness; however, it defaults to checked now so it's an extra step for our team members to uncheck it every time.

Hi Adobe Product Team & @jenla5,We would like to vote for an extension of an already existing feature of conditional formatting in AA Workspace. This is with respect to the custom conditional formating in AA Workspace where we have reports broken down to single or multiple levels. At this point, the 'Auto' formatting works in this case but if we try to do custom conditional formatting for a column, it does not show color formatting for all the cells as per the custom range we have provided in the 'Column Setting' option. With 'Auto' formatting, we have seen that at times this seems to be a bit confusing & the max./min. distribution does not always seem to look appropriate.Therefore, we would like to vote for this feature extension for custom cell formatting as well to be applied to all the items in a Column.Below are a few screenshots of the existing limitation of custom conditional formatting feature:Thanks & Regards,Abhinav

Good Morning, Adobe Product Team/@jen_lasser! Currently, in Adobe Analytics Workspace, if I want to "hide" any section within living report, the best I can do is simply minimize said panel and move it to the bottom of the page, but that does not necessarily accomplish what I would like to do.Oftentimes, I am working ahead on sections that I may want to include in the report as a future section, OR I have a section that I swap in and out, depending on specific elements being reported for that date range.  Creating a different version of the report actually creates more work, particularly when I have 50+ people on a daily distribution, and no fast and easy way to simply copy and paste my list of recipients (but that's a different issue).What I would much prefer is a feature that allows me to select a checkbox that indicates which sections should be LIVE (i.e., Production-worthy) WITHIN a report that I am already delivering on a regular basis.  Having this feature woul

Give the user the ability to filter the notifications they are seeing on the Notifications page. UserRead or UnreadStatus/Comment vs. System Update (i.e. Joe Smith has assigned you to a task)Date range

Workspace has been by go to reporting canvas since its release and I find myself relying on Data Extract, Data Warehouse & Ad Hoc reporting for larger data sets and analysis.It would be helpful to allow for a larger data set threshold within Analytics Workspace.

It is current not possible to use risks outside of the Business Case builder and the Risk tab. This inhibits the ability to create custom reports and dashboards that utilize this data to drive focus or decision making. The fields in Risks should be accessible and flexible in the same way Issues are used.

In organisations with Workfront + Proof, a document will typically be added to an issue/task within a project and a proof generated from within Workfront. We should be able to display information (especially information in custom forms) from Workfront relating to the project, task and/or issue with Proof. Otherwise, every proof reviewer needs a Workfront licence even if their only function is to review and approve artwork. They also need a navigation path, as the notification e-mail from Proof and the proof viewer does not provide any reference back to Workfront. One approach would be to allow calculated fields in the Proof custom form builder that references the Workfront data model.

We're currently having a row between our Project Management team and the Production/Proofreading team:One the one hand, the PM team wants to go all-digital with proof routings, including the handling of corrections by the Production and Proofing teams.However, the Production/Proofing teams for years have relied on a composite PDF of the changes from our previous system that takes advantage of Acrobat's "Comments checklist" functionality to make sure they methodically hit every change. This also serves as their digital record of the work.(Personally, when I have complex annotated PDFs to go through, I like the checklist ability too...I think not having it and trying to work on corrections straight out of WF is asking to make mistakes...)However, using the PDF button under Print Summary to get that checklist is cumbersome and takes at least six steps to generate, download, then re-attach to a new Task to get the work done. A huge time suck over our previous way of doing

It would be great if we could upload imagery or screenshots into our custom forms to better illustrate examples. This need came about when setting up a request queue for our Marketo team. Because Marketo programs/emails have many different elements it would be nice to provide a supporting visual to illustrate what we are asking our submitters to identify.

Ability to Save versus Submit a request - many requests are large and require the ability to be built out and saved before final submission. This is becoming more and more important as we push towards having ALL required information in a Workfront request.

Thank you for your feedback. I am glad to let you know that we have removed the limitation of 1 draft per request queue.You can now have as many drafts for a queue topic as needed and the updated interface will still remind you that you can use one of those drafts. You can access your drafts as you're entering a new request, or from the Drafts area. Feel free to review and provide feedback.

Hi Adobe,To download a single freeform table from Adobe Analytics Workspace, we are currently having to download all freeform tables and remove the rest from the excel or collapse all other freeforms tables and panels. It will be great if Adobe can add a feature where we can select and download only the freeform that we are interested in downloading.Thanks,Srujana M

I LOVE the analytics workspace, especially in comparison to Ad Hoc Analytics (which is what I had been using).The only problem I have with it is that it does not allow you to show more than 200 rows of data. Ad Hoc allows up to 50,000, which is most necessary for pulling some reports.Is there any plan to allow for more rows of data? Or at least download a CSV with more than 200 rows of data?Thank you!

In using WF for our Agile teams and applying the Scrum format, we create Epics by entering a Task on the "project" side of the Agile Team which reflects the parent/child relationship of User Stories and Epics in the Backlog. However, the end date of the Epic is controlled solely by the latest Target Date of all the User Stories under that Epic. We would like be able to control the end date of Epics (or just have no end date at all) but by default, they will show an end date of the User Stories under them. Creating a "shell" User Story works to control this end date however those User Stories will show as aging in our reporting. Is there anything on the WF roadmap to have Epics behave/appear similar to other tools?

It would be helpful to allow for batch campaigns to run more than once daily. We have several campaigns that use custom Salesforce objects that can't use the trigger functionality. I need to be able to run these batches more than once a day for timely communications but this option doesn't currently exist. 

Product team, It would be a big time saver if we had the ability to designate one report suite that would always show up by default in the drop down for A4T reporting in Target.Screen-shot showing the drop down we wish to be able to affect with a settings change:Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | 1 (800) 497-0335

Right now, when you create a new user with a proof license, the option "Automatically generate proofs when uploading documents" is selected. This is irksome. It's an easy fix (remove the proofed document, go into the user's settings, and deselect this option. But I cannot imagine that most people's workflows involve automatically generating a proof for every document stored within a project.

Hello,I would love for there to be an ability for the user to be able to control their own email reminder notifications. For example : If a user wanted to, they can create a notification for "deadline for tasks" that could remind them 2 days ahead of time. If it's easier, there can be pre-set amounts of time or the user could customize. Currently this is global feature but this can be disruptive if I had to set this for everyone as only some would want a notification and others would not. This would be a more utilized feature if this was moved to user control.Thanks,Al

Ability to lock a proof at a specific time not matter what is outstanding on the proofs.

Change the time zones for guest users from military time

Our organization's Adobe Analytics instance includes some "template segments," which we have heard from Customer Care cannot be deleted, and can only be hidden via Virtual Report Suite segmentation and Workspace project curation. These segments were not created consistently, and lead to end-user confusion when our Adobe Analytics power users explore raw data/non-curated reports. I'd like to propose that Adobe Analytics admins have the ability to delete these segments. This would bring the following benefits to organizations:- Increased usability and alignment around organizational goals for existing Adobe Analytics segments - Support an organization's control over their governance plan overall.- Simplification of available/managed Adobe Analytics segments for tool admins and users - Remove admin requirements for curating reporting views due to segments that are not needed or desired, and that cause confusion when present.- Further democratize data for Adobe Analytics power users -