Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Project Schedule Should Override Individual User's ScheduleNew

Current Behaviour / Description - Both the project and individual user settings have an option to select a schedule. If you select the project setting to have option A (no holidays) and the individual user setting to have option B (company holidays), the project will not use the project setting option A if an individual user is assigned a task. If two or more people are assigned a task however, then the task will default to the project setting of option A. The reason the project setting works is due to the system project preferences: When multiple users are assigned to a task, use the schedule of the....Project. How would you like the feature to work - We should be able to use the project setting to override the individual user's setting.  Why is this feature important to you - Users work on different types of projects. Some are more time sensitive that others so we should be able to select the schedule that works best for the project type. Additional Notes: This really becomes a problem with you have predecessors with long lag times or durations. Tasks can get pushed out pretty far from all the vacation and time off. Another idea would be to have the project exclude holidays and time off when calculating duration / lag time but avoid scheduling the actual due date on a holiday.  For additional information, refer to: Case Number 00406587 - Schedule functionality not working as expected [ ref:!00D3006HBH.!5004X01z7BqB:ref ] 

Tlovie
TlovieLevel 3

Resource Manager Enhancements IdeasNew

The Workload Balancer is really the only part of the Resource Manager that our teams use. The other features have not proven to work for us. The Scenario Planner (which seems unfinished) needs more of a connection between its features and the Workload Balancer. Combining the two would unify the planning of possible initiatives with the reality of a team’s capacity. They are currently disparate and fall short in how much they can be used to roadmap work quickly and efficiently. If you were able to quickly work on new initiatives and broadly assign users to those initiatives on the fly, that would be an extremely useful feature. Another disparate feature is the relationship between the Workload Balancer and the Work Effort columns in a project view. I should be able to update this percentage in the Work Effort column from within a project view and have this be reflected in the Workload Balancer. Right now it is only the “small, medium, large” shortcut, but it should be specific percentages like the allocation feature in the Workload Balancer allows. It takes too much time to click away from a Task view and into the Workload Balancer view from inside the project. The new filters GUI should allow you to switch between to a text edit view.The 3 month view should still split the allocations up by weeks. The current distribution of hours is very confusing when applying a single percentage to an entire 3 month period. It’s hardly ever used because of this. The tool should show Task status colors in Workload Balancer. Currently, you can only choose to color code the items in the Workload Balancer based on the project status, but this is misleading if the project is in-progress (green), but the task is on hold (red) because all tasks would show as green. It would be helpful to visualize the Tasks by their individual statuses.The Utilization feature is not used because it is only month-to-month, the filter system is yet another method of configuring, and it doesn’t describe actual user assignment. This is another example of a feature that should be more integrated with the Workload Balancer and not a separate view. Anytime the tool only shows “FTE” instead of the actual % is confusing. As an example. This can be seen in the Planner view. [4/22/2024] The ability to move/shift task dates would be a HUGE time saver. It’s understandable that doing this is difficult because of the various task constraints and dependencies of the tasks within the project. However, you have options if you auto-set the tasks to fixed dates once you move and the original task constraint doesn’t work with the change you’ve made. Another option would be to treat these if you took the approach of the Scenario Planner and treated the 

Tlovie
TlovieLevel 3

Custom Field - Proposed change to provide enhanced governanceNew

Description - We would like all custom fields to have a check box that denotes "System Admin Only" can update. We want this to appear on existing and future fields created. We want to be able to select this during and after a new custom field is created. We want a System Admin to go into a custom field and select "System Admin Only". Why is this feature important to you - We have approximately 60 key custom fields that we only want System Admins to be able to modify. Yes, we educate and enable System Admins and Group Admins on how custom forms/fields work. We ask that any requests to modify these 60 key fields be brought to Governance Board. We have a custom form with these fields on it that we ask users to refer to. We also have a google sheet with these fields listed. We have learned (the hard way) that people forget. We need to add in a level of checks and balances to these key fields. This monitoring becomes even more important as we integrate into new applications in the future. We are currently integrated into AEM, and have active fusion scenerios. How would you like the feature to work - We want all existing and future custom fields to have a checkbox titled "System Admin Only can update". This should appear at the top of the field. There would be in information text that would advise the user that only a system administrator can update this field, please reach out to them directlyCurrent Behaviour - Group and Sys admins can create and edit key fields that require governance before creation or editing. Realize this would require existing fields to be reviewed by Governance Board, which is fine. Also acknowledge ongoing governance would be needed to identify future key fields that require the "Sys Admin" only updates. 

FelixGomez
FelixGomezLevel 2

Avoid sent SDK App trackState or trackAction with Adobe LaunchNew

 How many times a trackAction is activated with an ID that is not registered or is entered incorrectly within the native app code.Taking into account that the development cycles for the deployment of applications within the different STORES (Android & IOS) can take months, these trackActions are dirtying the data and can sometimes increase the useless consumption of SERVER CALLS in your company.This can cause unwanted SERVER CALLS billing.Currently, the "CONTEXT DATA" data in the event we want can be modified through Adobe Launch, enriching the event from "Adobe Launch", but we cannot prevent a "SERVER CALL" from being executed even if we do not need it in our implementation. How would you like the function to work?Ideally, to avoid unwanted "SERVER CALLS", we would include an option in the "MOBILE CORE" where we could prevent the execution of a "trackAction" or a "trackState", conditioning based on its "action name" and/or contextData (in Adobe Launch UI). Current behaviorThere is no way to prevent a "SERVER CALL" from being consumed and counted, even if it is not controlled, or has been included by mistake within the source code of the mobile application through the "trackAction" / "trackState" events. There are some issues in the community regarding this that are quite old.This feature should be a "MUST" to better control the data that reaches the Report Suites, it would give a lot of flexibility and control over the data.