Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

BernardoCFNew Participant

Report drilldown improvementsNew

I think that Adobe needs to up their game in the report drill-down features of Workspace. Items that are missing and almost prevent a good workflow to me are:   1) ability to keep all rows in a report with a specific drilldown dimension/segment: there should be a feature to allow drill-down of every row item that appears on the report, automatically.   Example: a report is broken down by day of the month and then by hour. The report is created on 15 October and the report date is set to "this month". As the days of the month go on, the report will add more days of the month, but the days of the month that were added after the report has been configured won't be broken-down by hour. This is a terrible limitation to me.   2) ability to set a specific drill-down configuration to all rows in a report.    Example: a report is broken down by page and then by page url. My website has 100 pages and url variation of those pages don't go beyond 5 urls. Thus, I want to add a drill down dimension (page url) to each of the 100 pages listed in the report. I want all of the pages to be drill-down by the page url segment with 5 rows under each page url drill-down. I want this setup on all 100 pages, applied automatically to the 100 rows (including potential future rows as I add more pages to my website). Currently, I need to manually set up the amount of rows in a drilldown for each main roll. That's not practical. I know about table builder, but that's still limited. For example, I want all drill-down rows to be sorted in a certain way. How do I set that up for the 100 drill-downs automatically?   Thank you.

LizMiller-BJCNew Participant

Change the behavior of issue RecallNew

I would like to propose changing the default functionality of recalling an issue or request that has a pending approval status. It would be even better to have the ability to customize the behavior at the system level, but any improvements would be appreciated.   In current state, when a user submits an issue or request that has an approval process, they have the ability to Recall the issue while it is still pending approval. When the Recall button/icon is selected the issue is deleted and sent to the recycle bin. Because these recalled issues are deleted, we are unable to keep a record of the need and users are unable to refer to the information that was included.   We find that users who need to recall an issue need to either cancel it due to some change, or they need to revise it before initiating approvals. In either case, we would like to retain a record of the recalled issue, as well as have the ability to copy or resubmit it. Ideally, we would have the option to customize the behavior of the Recall functionality at the system level. This would be similar to the functionality in approval processes that allow you to select a status for rejected work items, i.e. if rejected change to status XYZ.    However, if the default functionality of Recall was to "revert to draft" rather than delete, we could easily create our own process to change the status manually. 

MarlaDrNew Participant

Request/Issue planned completion date tied to connected project - similar to the project/task statusNew

Description - Would like the request/issue planned completion date tied to the connected project so when the planned completion date of the project is changed it also reflects on the corresponding request. Currently, the status does this. For instance, you cannot mark the request/issue complete. It auto closes once the project does.   Why is this feature important to you - Reduces the amount of manual work for people who receive requests/issues. Also, it makes the overdue reminder notification more relevant.   How would you like the feature to work - When the project's planned completion date is changed, the corresponding request/issue's planned completion date auto updates.   Current Behaviour -  We have the reminder notification turned on to send if a task/issue is overdue more than 5 days. Because the request/issue has a default 2 day planned completion date and can't be closed until the project is closed, those requests/issues are showing on the notification as overdue. Technically they are overdue because the planned completion has passed, but not really because the request/issue has been worked and converted to a project. Right now, the only solution is once the request/issue appears on the overdue notification, then find the project and its planned completion date, then go back and change the request/issue to match. This is time consuming and could be solved if this was automated.