Skip to main content

Filter by idea status

10000+ Ideas

Tlovie
TlovieLevel 3

Requesting that Adobe create new user access level for fusion only users - Do they truly need Sys Admin Access Level?New

Description - We have fusion users who create fusion scenarios, but are not acting as system admins within Workfront. To create fusion scenarios, users must be given the access level of System Admin.  For example we have users within our Corporate IT team who are experts in Jira. They create fusion scenarios that link Workfront into Jira, but their expertise in within Jira. They take training on how to work in Fusion, but their focus is not on being a  Workfront system admin. They own, document, update their fusion scenarios.Why is this feature important to you - We have users in Fusion who show as System Admins, when in reality they are not system admins. They only author and maintain fusion scenarios. We would like them to be assigned a newly created access level to denote that they are Fusion only users. We don't want or need them to be viewed as system admins, because in reality they are notHow would you like the feature to work - We would Adobe to develop an access level that allows users to interact between Workfront and Fusion, but not give them System Admin access level. Would it be possible for a fusion person to only be required to have group admin access level?Current Behavior - Our Workfront instance gives the appearance of having System Admins, who don't act as system admins, and we don't expect them to act as System Admins. We need visibility on who is  a "fusion only user". Yes, I know we could create a job role or team, but the reality is we don't want these users to have the same access levels and permission as a System Admin. All feedback is welcomed. 

natteaLevel 3

Enhanced formatting options for Project & Task Descriptions - HTML formattingNew

When creating a Project and Task there should be a more robust feature for creating the description. Wrike has this ability and it's amazing. A lot of times, a project's description reaches far beyond plain text and custom form fields. How most people at our company communicate is through email, and although email is a complete mess, what email is good at is allowing the person to format a message and description is multiple ways: through documents, screenshots, HTML text formatting (BOLD, underline, strikebreaking, bullet points, numbering, indenting, tables, charts, font colors, etc). Most project and tasks have supporting information in the form of images and charts, and there isn't a way currently in WF to communicate this within the system. We now have to go outside the system and go back to emailing or using other project management tools. Workfront has a lot of amazing features, but I feel as though you have to think back to the basis of a project management tool - and this tool should focus on the easy communication of project and task creation. This could also be applied to requests and documents as well, but not as important as projects and tasks.The creation of a task should be a bit simpler and less cluttered. Workfront has so many options and features, which is fantastic, but it can be completely overwhelming for users who are not necessarily tech savvy and just want to use the system for creating a task, description, dependencies, assignee, and due date. This information should be at the forefront of the design and the rest of the functionality can be shown differently. And custom form fields should really be considered part of the projects description and be within that same area. Right now it's not very intuitive where to get necessary details about the project in order to do someone's job. The user needs to go to project details, look at the main overall timeline details then click custom form to get the actual full description of the project.