Product ideas | Community
Skip to main content

10000 Ideas

arwithGrandeNew Participant

Visitor level segment with rolling date rangeNew

Description - Currently, we are trying to run a report that will pull back all visitors that have placed an order in the last 30 days, what have they done in the last 365 days.  We can set the calendar for the last 365 days, but we are unable to have a segment that will automatically look back to the last 30 days.  Using day, or month will be a manual solution, but is an extra step.  And using granularities will over-ride the current calendar, meaning we cannot look at behaviour previous to the order.   Why is this feature important to you -  Currently, most in the business is using granularities to do this, without realising the impact is has on the reporting.  This means false information / analysis is being used to make business decisions.   How would you like the feature to work - For the short term, can there be a pop-up when granularties is used in the segment to warn that this will override the calendar date range?  Long term: can we have an update to have the Day metric work more like granularities, or have granularities to turn on / off the feature to over-ride the calendar? Current Behaviour -  Currently, granularities is over-riding the functionality of the segment partially by overriding the calendar date range.  The only solution to do what we want is either manually updating the segment each time this report wants to be ran, which is inefficient and beats the purpose of creating segments, or alter the business use-case to not focus on the last 30 days.  

MatthewLi1
MatthewLi1New Participant

Improve ease of use for hyperlinks within formatted text fieldsNew

Description -Right now when you want to add a hyperlink in the workfront you need to highlight the text and then click the link button instead of being able to use command K to hyperlink or links automatically are created like every other site including this forum for example.Why is this feature important to you -For multiple fields across hundreds to thousands of projects when links are needed this results in a lot of additional time needed to enter links within a workfront project.For teams migrating to Workfront from other platforms, this is often a major pain-point and feels like something that would be easy to enable.How would you like the feature to work -When in a formatted text field, you should be able to highlight a section of text and then use the command + k shortcut to hyperlinkYou could even use the same functionality that exists right here in the forum!!!When in a formatted text field, you should be able to enter a link and have it automatically create a hyperlink when you hit enter or space after the linkYou could even use the same functionality that exists right here in the forum!!! (try copy and pasting the URL of this ticket into a reply if you would like to see the the functionality I'm referencing)Current Behaviour -You need to highlight the text, find the link button, enter the link again, and hit enter. This is a lot of clicks, especially when a link could even possibly just automatically create a link when pasted in a formatted text field

MandyGeorge
MandyGeorgeNew Participant

Create a new advanced function for metrics to do a grand total (deduplicated column sum)New

Description - Currently there is the ability to use an advanced function "column sum" in calculated metrics. This adds up the value of all the rows in the dimension and gives a sum. The issue with this is that the number is often different from the 'grand total' at the top of the column of the original metric. This is because the grand total is deduplicating items by default, but the column sum doesn't do the deduplication. For example, if your dimension is products and your metric is orders, the grand total will give you the total number of orders and each row will give you the number of orders for that row. The column sum will add up each of those rows, ignoring the fact that a single order can have more than one product, and give you a sum that overcounts the actual total. To fix this, create a new function that is a grand total, it will take the grand total value associated with the dimension it is put against.    Why is this feature important to you - This is important because it provides increased functionality when creating advanced metrics that need to use a total for the entire column. The column sum is great, but it is limited, and this would remove that limitation.   How would you like the feature to work - The grand total function would be able to be added to metrics like all of the other functions. What it would do is take the grand total (a deduplicated total) associated with a metric.   Current Behaviour - Currently there is no option for a grand total function, only a column sum.

RAshley
RAshleyNew Participant

View access should not grant Edit access on lower objectsNew

We recently discovered an "intended behavior" that smells an awful lot like a bug to me.Our intent is for users to be able to add issues to tasks assigned to them, but not add issues to projects themselves. We set up permissions in such a way as to provide this, but our users are still able to add issues to the projects.We entered a ticket, and after three weeks of research Adobe provided this response:"Our engineers were able to find that when a user has View access to a higher object (such as a program or portfolio), the system is designed to allow those users to enter in issues for projects and tasks. This design has been implemented for quite some time, but our documentation didn't reflect the described behavior. I have included the updated documentation below.User <redacted> has View access to the portfolio of the project where he can add issues. The system will take those assigned rights (on the portfolio level) and it will not be overridden by the selection on the project level (marking for the user to not be able to add issues). In order to prohibit users from adding issues to projects or tasks, you will need to remove view access on the portfolio level."So giving users VIEW access to a high-level object also grants them certain EDIT permissions on lower objects. This is a) not intuitive in any way and b) poor design. There is currently no way to achieve our goal without removing view access to portfolios (which we want them to have). This "link" needs to be broken. If we want a group of users to have edit on an object type then we'll use the existing permissions structure to grant them that access.