Product ideas | Community
Skip to main content

Filter by idea status

10000+ Ideas

MarlaDrNew Participant

Timesheet Profile Updates - Add option to select 'None'New

Description -We have users who do not need to log time based on their job level. For those users, we didn't apply a timesheet profile. Now we have some users were who logging time but due to recent job role changes are now not required to log time. I went to change their timesheet profile to remove it and with the new UI updates, it does not allow me to do so. It only always you to choose another timesheet profile. How would you like the feature to work - I would like the ability to completely remove or clear a timesheet profile from a user’s profile in the UI. Ideally, there should be an option to select “none” or leave the field blank, so that no timesheet is generated for those users who do not need to log time. Current Behaviour -Currently, the new UI does not allow clearing or removing a timesheet profile from a user’s profile. Instead, it requires assigning a different profile, with no option to set it to “none.” Support has confirmed this is a known limitation affecting multiple customers. They provided a workaround below, but it is more time-consuming and less efficient. Allowing administrators to remove timesheet profiles directly in the UI would simplify the process and improve usability. From Support: Best workaround here would be to create a “No Timesheet Required” profile to act as a replacement for these users. You could do this by creating a dummy timesheet profile (e.g., “No Timesheet Required”) with settings that do not generate timesheets or have no approvers/hours types. Then assign this profile to users who should not log time. You will then want to update your “no logged time” reports to exclude users assigned to this profile.

LyleSt1New Participant

Enable support for modern package managers (Yarn or PNPM) in the Frontend Deployment Pipeline of Cloud ManagerInvestigating

Request for Feature Enhancement (RFE) Summary: lease enable support for modern package managers in the Frontend Deployment Pipeline. Currently the pipeline only supports NPM, which although widely adopted is also generally known as the slowest solution for package management within the nodejs ecosystem. Consider support for yarn or pnpm, both of which outperform NPM from a CI/CD perspective. Use-case: We currently use Yarn on Managed Services to deploy full stack code. However, when migrating to Cloud Services and wanting to take advantage of the Front End (FED) pipeline, NPM is assumed and only the version can be altered via pipeline variables. We use Yarn as it has additional features and builds/deploys faster than NPM. Similarly, pnmp and Yarn PnP deploy about twice as fast as npm in our benchmark tests. Current/Experienced Behavior: Customers must use NPM and package-lock.json as the deployment package manager Improved/Expected Behavior: Customers can customize the FED deployment pipline to usee the package manager of their choice. This could be either an explicit selection, a pipeline variable, or the pipeline could lockfile detection (npm uses package-lock.json, yarn uses yarn.lock, pnpm uses pnpm-lock.yaml) Environment Details (AEM version/service pack, any other specifics if applicable): This request is for AEM Cloud Service, current version. Customer-name/Organization name: Toyota Motors North America (TMNA) Screenshot (if applicable)     Code package (if applicable):  

BrentHat
BrentHatNew Participant

Better planned hours management in new Priorities viewNew

The new Priorities view has really caught on with our team. The GUI is attractive and the recent release brings a lot of functionality that helps the team have a singular place to go in order to manage work assigned to them. But it could be perfect! Please add the same "edit allocations" functionality as is available in the Workload Balancer (within the Resource Management section) that allows a user to specify planned hours for a task on a day-to-day, week-to-week, or month-to-month basis. Currently, the Priorities view only allows a user to change the total planned hours of a task over the entire duration of the task.The ability for a working team member to specify the exact amount of hours they will spend on the remainder of a task gives managers a more specific view from week to week. We do not have access restrictions of the Workload Balancer on our team and have found it very useful to use during our meetings when discussing what will be worked on during a given week and each member has the autonomy to update the planned hours for all tasks that are either in progress or about to start. This granularity that the Workload Balancer provides would make the Priorities view the ONLY view that a team would need in order to make quick, simple changes without having to jump to a different part of Workfront. Perhaps the Log Time pop-up (image attached) could be used to enter in allocations? Thanks!