Color coordinate Parent tasks so it is easier to track deliverables in a large project. There can sometimes be different tasks that have different times to be reviewed/proofed so color coordinating them would help us to find the "grouped" parent tasks in a project that has 300+ deliverables.
I would love to connect user names and the custom forms. That way when submitting a project, the requester can choose the users within a custom form and those users would be alerted that the request is submitted or project created.
Ability to assign every member of a team to a task without having to enter each of the members names manually - The use-case here is tasks that represent meetings. In these cases, we need to assign every member of a team and have the hours allocate across all of them. We want to assign the team and have everyone on the team assigned, not just the first to pick up the request/task.
Imagine a scenario where lead IDs 4 and 5 are merged together in a Marketo instance. 5 is the "winning" ID, so querying the lead via the REST API returns data. However, if you query for data on lead ID 4, a successful API query is returned with no data in it. This means reconciling that 4 was merged into 5 difficult, and leaves a stray ID. Would it be possible to update results on merged records so that they pass something like "mergedInto" : 4 when this occurs? Bonus points if the winning record also got a note like "mergedWith": 3,4,7 -- something that concatenates all records which have been merged into this winning record; this would be nice to help verify on both ends that a merge was successful.
Display traffic volume in Occurrences rather than in Page Views on the Traffic Management Overview page to help administrators to estimate the server calls volume.
The workload balancer allows a user to group tasks by project which is great. But it needs to go a step further to group those projects by program/campaign.
When converting an issue to a project, it would be helpful to retain the priority level of the issue after conversion rather than having to manually set it each time
Allow users to choose which time zone they want to see on task due dates when they're viewing tasks in Workfront via web browser.I have a team split between Eastern Standard Time and India Standard Time. The folks in India Standard Time want to be able to view EST time stamps. Because the browser is using the time stamp of the machine, there isn't anything that I can change in Workfront to help them see EST time stamps.
Description - Cross-Device Analytics allows analysts to understand user behaviour across devices, by stitching device data together.I would like to see this extended to become more of a general "Cross-User-Agent Analytics", where (field-based) stitching works across devices and browsers (and even standalone browsers and in-app browsers in mobile devices).I would also like to see this extended to all AA SKUs, not just AA Ultimate.Why is this feature important to you - Given modern browsers' tracking restrictions, it might be more feasible and accurate for clients to provide their own "user ID" that analytics systems can consume. Also, with the proliferation of apps and browsers (standalone and in-app), there are many areas where a common user ID is beneficial to identify actual unique visitors, or "people".How would you like the feature to work - The client provides its own "user ID" (with Adobe providing a fallback user ID, e.g. with the current Experience Cloud ID Service). AA consumes this user ID and uses it as its own visitor ID. This has the added benefit of AA being able to count Unique Visitors using this client-supplied user ID, instead of a cookie-based visitor ID that is subject to modern browsers' tracking restrictions.Current Behaviour - Cross-Device Analytics is limited to stitching device data together, but there is no (apparent) impact on counting unique visitors, or even overcoming modern browsers' tracking restrictions.
We need to be able to utilize Programs for our Campaign assignments, but due to the volume of our work-- more than 10,000 project per year-- the Programs need to be deactivated, just like Portfolios, Projects, or Issues can be. This is essential. Other work-arounds are clumsy and unreliable.
As of January 2021 continuous audience sync is available, but it's only available for static lists. Would love to see this introduced to smart lists as well.
As of today, using /rest/v1/program/members/describe.json will return default Program Member fields in addition to whatever custom fields have been defined. Although items like Acquired By and Success are present, the field for Success Date is not. Could this be added to the list of extractable fields, both when describing and exporting?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.