Skip to main content

Filter by idea status

10000+ Ideas

Workspace, allow us to set visualization labels at the column level of the freeform table as well as in the visualizationNew

Being able to set labels in our visualizations is great, we can immediately see where the label is going and how it will look... but the problem comes when the freeform table has the slightest change (like the dimension breakdown, which doesn't impact the columns), forces the labels to re-populate with the default value. Let's take a simple example. I create a freeform table with Referrer Instances at the top, and that broken down into columns by Referrer Type. Then I use Day as my dimension.    When I visualize this, what do I get:Referrer Instances [Referrer Type: Search Engines]Referrer Instances [Referrer Type: Typed/Bookmarked]Referrer Instances [Referrer Type: Social Networks]Referrer Instances [Referrer Type: Other Websites]Since I am going to label my visualization and add a description of what this data is, I don't need it repeated in this fashion all through the legend labels. I want them to be clean, not this ugly version:  So here is where renaming comes in, great! Love that I can rename them. (Search, Direct, Social, Other - done) But here's where the issue of the default comes in... let's say I want users to be able to select a set of rows from the table to focus on one part of the overall data.... the labels on the visualization reset to the default values...  Or if I want to duplicate a table to do a different dimension... I want my columns to have the same visualization labels, but I have to rename every iteration. So in some cases I am wasting time on every report re-labeling the same sets of columns to make the report look presentable... or having to leave the defaults in there because once users start selecting rows it makes no difference cause I can't control what shows... There is obviously a need for these default generated values (something that we can always revert to), but I would love to be able to also set "actual values" or even "defined how the auto-label should populate" at the column (or even report level - even if it's take the "top" or "bottom" value (metric or segments, etc) on stacked value, or concatenate in this order, etc (I'm sure there are a lot of options that could factor into this). The modify at visualization level would then take priority over that.So it would be (in order of prioritization):1. Visualization Level Set Value2. Column Level Set Value (new)3. Report Level Custom Generated Values (new)4. Standard Default Generated Values  Providing more control on how our labels are generated could save so much time on creating and styling our reports, and make the interactivity of the reports work better and more consistently with what our users would want to see (ease of reading) 

BRING BACK the ability to Edit a single Item/Task/Project from a report and add a Comment (SPOILER ALERT: Support reported this will disappear from bulk edit as well)!New

When I am working in a report in Classic WF, I am able to select a single item from the report (via the check box), select Edit , then jump to the bottom of the pop-up form and add a comment. Currently, I CAN NO LONGER do this in WF New Experience.In the New Experience, if I am working in a report and I select a single Item to edit, the outcome is NOT the same as before. I DO NOT have the option to add a comment any more.Please note that if I select more than 1 Item on the report (ie Bulk Edit), the pop-up box that displays is the Classic WF look / feel and the Comment box is available for use (at least for right now).Workfront Support provided the following response when I inquired why I no longer have the ability to do something that I used to.I was able to confirm that with the New Workfront Experience, the functionality of the Comment Section has been removed as overall there was very low usage and as the Comment section is to essentially post an update to the update stream, this can be done in other areas such as the Updates tab of the object. The reason you are able to still see the Comment section is due to the interface of bulk editing work objects still being the Classic interface which is still being worked on and may eventually go away within that process as well.­Why in earth would this have been removed? Surely our organization can't be the only one that found this useful when working in a report. It was really handy in both single and bulk edit mode. Needless to say, I'm not happy that I'm having to ask to have something like this back. :(