Build better products with our product team
If they don't already exist, It would be nice to have folders to store workspaces. My list is getting very large. I like the tagging feature, but would also be nice to file some away.
There can be many reasons users and the system enter updates on an object (project, issue, task, etc). This can make finding the most relevant update for a report challenging. Today's design also assumes that every update the object owner makes is a "condition update".We propose adding functionality to #tag, categorize, or group updates. This would support the ability to filter the updates for a more precise item - such as the last "project status summary" or the "project gate review" or "staffing" topic.The tagging/categorization should support a single update having multiple tags - such as "customer facing update" and "internal project status summary".
From the Resource Management > Planner tool, it would be great if we could create flexibility in the way that the information is displayed. For example, we were hoping to re-organize the order in the planner view to show the available hours from a team first, then the hours for the people within that team, and then the hours per project.The current filters are helpful, but there are a few limitations. When filtering by role, it shows the available hours for everyone in that role, but then it goes directly into the entire list of projects. Adding flexibility in the hierarchy of the way the data is displayed is what I'm hoping to achieve.
We would like to be able to highlight when creating updates and the ability to add highlights to existing updates to call out crucial information and allow for clearer understanding of needs.
Include an "Apply" button with Layout Template setup. While creating an implementing Layout templates for users this will allow minor changes to be made and tested without having to leave the template setup area.
Anytime someone is assigned to a task in a project, is the project owner or has had a project shared with them, they become in the People section of the project. All good. However, anytime a task is removed, a project owner changes, or any people change on a project, the old users are still in the People section of the project. Based on email notifications many people opt into, this means they are getting so many irrelevant emails for projects they are no longer on. They don't want to turn those off, bc need those notifications for projects they are actually on. When someone is removed, the People section should be dynamic to be removed from there too. Also, when we use a template for a project (which is almost always), and in Planning/refinement before changing to Current, sometimes we remove unnecessary tasks, but it is still adding those people to the People section even when we remove them in Planning status. Very frustrating.Lastly, when someone is deactivated, they should also be dynamically removed from templates and the project people section.
Many times for some teams, the whole team is assigned to a task (not individual users, but the WorkFront Team is assigned, like Web Team, or Studio Team for example). In the Team's balancer, it shows tasks assigned to people on the team, but doesn't show any tasks assigned to the Team itself. This is very frustrating and not showing us the full picture of what is assigned to a team and want to be able to see these and then easily reassign from there, like we can reassign tasks to an individual from the workload balancer.
The use case:Project Owners assign a team from a different department to tasks on their project. The team then looks at the tasks in the Workload Balancer of their team view (Unassigned Tasks) and allocates users and hours to the task.Currently doing this we are facing two problems, where the task will not show up in the balancer, and the team does not take notice of the assignment.1.) When the team is assigned to a parent task, but not to a child task. The task will show up in the backlog, but not in the balancer, because we can not plan hours on a parent task. However, it is important to see the assignment in the balancer as well, so the task is noticed.2.) When the team is assigned to a task, but there are also users assigned who are not part of the team. - It is pretty common that a team and not team but project related users are assigned to the same task. However, these tasks are not visible in the Workload Balancer, because they are not unassigned, but also not assigned to a user of the team. It would be great to find a solution where all tasks assigned to the team will show up in the balancer, so teams can use the balancer for reliable planning and do not miss any work items in their planning.
I'm talking about a standard feature in MS Project which allows to collapse tasks at multiple Indent levels. It's called Outlining Tasks.It works something like this:When you select Outlining Level 1 - All the Tasks at Level 1 Indent will collapseWhen you select Outlining Level 2 - All the Tasks at Level 2 Indent will collapse and so on..If this is not clear please watch this video: https://www.youtube.com/watch?v=jzHNHW5Xrzs to learn more.
Problem:We are unable to identify employees by Job Role in a project plan or on the project Workload Balancer.The new functionality only shows 'Recent Assignees'. We are a very large organisation and we now have to create a report or user filter to find the 10 Project Managers in Denmark, go back to our project plan or project Workload Balancer and manually input the employee's name.Change Needed:The recent assignments logic is very useful, and an excellent idea for smaller organisations, however, for larger organisations, we also need the 10 project managers appearing in the search results.Please implement a hybrid list of Search Hits of Recent Assignments and Employees with the same Job Role.
Request for Feature Enhancement (RFE) Summary: Better UI experience for Settings and Rules section in the metadata schema Use-case: To be able to create metadata schemas easier and faster Current/Experienced Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has numerous fields), the "Settings" and "Rules" section are no longer visible. 2. When selecting fields already in the metadata schema, "Build Form" option is also visible. This can lead confusion to the users as users might think that "Build Form" is a setting of the selected field. Improved/Expected Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has a lot of fields), the "Settings" and "Rules" sections should follow with the scrolling or "stick" to the page. The "Settings" and "Rules" sections should always be visible so that it would be easy to change the settings when selecting the fields. 2. When selecting fields already in the metadata schema, "Build Form" option should not be visible so that "Settings" and "Rules" section are the only ones displayed. Another option is that the "Build Form" can also be placed in the left side of the page so that it would be separate from the field settings. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK