Feedback and Ideas

Currently, REST API access supports only API Key authentication (a long-lived JWT passed via the Authorization: ApiKey <token> header). This presents two concerns:Security — The API key is a static, long-lived token with no built-in expiry rotation mechanism. OAuth 2.0 client credentials flow provides short-lived access tokens that are automatically refreshed, reducing the risk of token compromise.Integration compatibility — Several modern tools require OAuth 2.0 client credentials flow for service-to-service authentication and do not support static API key connections.Would like to have OAuth 2.0 authentication (client credentials grant type) for AdaptiveWork. Specifically: A Token URL endpoint where we can exchange a client_id and client_secret for a short-lived access token and the ability to use that access token in the Authorization: Bearer <token> header for subsequent API calls.

Users need the ability to interact with summarized (grouped) report data directly within dashboards during meetings and discussions, without being redirected to other pages. This is important for maintaining context, improving usability, and enabling smoother navigation when presenting or analyzing data live.Current Limitation:When a grouped report is added to a dashboard, it is displayed in a summarized view. Clicking on a summary row redirects the user to the underlying project or record instead of expanding the grouped data within the dashboard itself. Unlike reports, dashboards do not support in-place expansion of grouped rows.Requested Enhancement:Enable drill-down or expand/collapse functionality within dashboard reports, allowing users to click on a grouped summary row and view the underlying items directly within the same dashboard (similar to how it works in the report view), without redirecting to another page.Expected Outcome:Users can seamlessly expand grouped data within d

Currently, certain UI elements - such as custom action buttons - do not appear or update until the user manually refreshes the page after performing an action (e.g. uploading a file). While the existing behavior is intentional to avoid disrupting multi-tasking workflows and prevent loss of unsaved data, it can create confusion for users who expect the interface to reflect changes immediately.Use Case:A user uploads a file on a project page and then navigates to the Actions menu expecting to see the 'UAT Plan - Send for Approval' button. The button does not appear until the page is manually refreshed, which feels unintuitive.Proposed Enhancement:Introduce selective/partial page refresh functionality, where only the relevant section of the page (e.g. the Actions menu) updates dynamically in response to a user action, without triggering a full page reload. This would preserve the user's current workflow and unsaved data while ensuring the UI stays in sync.

The Project module currently allows users to configure lookup filters within specific views (for example, "My Projects"). However, these filters, such as those applied to the Business Unit field, are user specific and are not enforced globally across all users.Business Requirement:The customer requires centralized control over the Business Unit filter values to:Ensure consistency in project data selection across all usersLimit available Business Unit options to only approved valuesMaintain standardized reporting and data governance across the organizationCurrent Limitation:Lookup filters are applied only at the individual user or view levelThere is no option to enforce filter values globally across all usersThis can lead to inconsistent filter behavior and potential data discrepancies in reportingRequested Enhancement:Provide the ability to configure lookup filters for fields such as Business Unit at a global level within the Project module, ensuring that defined filter values are:Enfo

The out-of-the-box Resource Summary report provides a comprehensive view of timesheet data, including work items, hours, cost, billing, and profitability. However, it currently does not include the Timesheet “Reported Date” (time entry date) as part of the report output.While the report allows filtering using <Timesheet>.Reported Date, the absence of this field in the exported results (Excel) limits its usability for detailed analysis.Business Requirement:Users require visibility of the date associated with each time entry within the report output to: Analyze time data across specific days within a selected period Perform monthly or multi-week reporting with clear date-level breakdown Support financial reconciliation and audit use cases Enable accurate downstream processing in Excel Current Limitation: Date field is available only as a filter, not as a report column Report output is aggregated without temporal granularity Requested Enhancement:Add the ability to include T

Hello, I had reached out about an issue where Validation Rules and Workflow Rules don’t fire on the mobile app. I was informed that it is because the mobile app uses API and several of our Workflow Rules check for NOT(IsTriggeredBy(‘API’)) to allow for our integrations to make API calls on the web page. We need to have the ability to separate out the IsTriggeredBy(‘API’) function to differentiate between the mobile app and the web app to prevent users from taking unwanted actions in the mobile app.

Currently, the GetWidgetHyperLink() function used in workflow rules only supports generating widget links for Gantt and Roadmap views.Customers using workflow rules to send automated emails would like the ability to dynamically generate a widget link for the Project Overview (card view). This is especially useful when emails are sent to stakeholders who do not have AdaptiveWork licenses but still need visibility into project details.At present, the card view widget can only be created manually from the UI, which is not practical when workflows need to generate links dynamically for multiple projects.Requested Enhancement:Extend GetWidgetHyperLink() to support generating a Project Overview / Card View widget link that can be used in workflow-generated emails.Benefit:Allows automated workflow emails to share high-level project information with external or unlicensed stakeholders without requiring manual widget creation.

Hello, We would like to be able to disable the + icon at the bottom of the menu at the organization level for the AdaptiveWork Mobile App or at least be able to hide the Start Stopwatch and New Task options. We don’t want users to be able to use a stopwatch as it causes issues with our billing and we only want specific users to be able to create Tasks.We have the + option hidden with CSS on the web for most profiles, but it seems that CSS is not supported on the Mobile App.

Hello, We would like to be able to disable the Call Work, Call Mobile, and SMS options on the mobile app as we do not use this functionality and it causes unnecessary clutter and confusion. The options show at the top of the user profile on the mobile app.

Currently in the resource planning screen assignments are only visible if the resource has allocation at a task level - we plan our resourcing at the project level and so the majority of our project assignments are missing on this screen.

On the assign resource screen from capacity planning, it is not easily possible to over allocate a resource. If you want to assign the full demand to a resource even if that takes them over 1FTE, you have to manually override the assignment figure in the lower box for every week where that situation occurs. This means a lot of typing for a long project.  

I’d like to request that this functionality that appears on the project assignments tab is added also to the staffing requests tab:  

Product Enhancement Request – Shift Project Assignments (Shift Dates Action)Current BehaviorWhen using Shift Project Assignments, the system shifts assignments based on a dynamic window calculated as:Today – Shift Value (X days)Only assignment entries that fall within this window are shifted. Any assignments dated earlier than this calculated range are excluded from the operation.Key characteristics of the current behavior:The entire assignment range is not shifted, only the portion within the calculated window. The window is not visible or configurable in the UI. Users cannot select a custom start date for the shift. The shift operates on daily hours, which can result in partial and uneven distribution across months. For customers planning primarily in Units (%), this leads to varying unit values month to month, even though hours are not actively used in their planning model.This behavior is working as designed, but it is not intuitive and often differs from customer expectations.What

Customers require a true round-trip integration between Planview AdaptiveWork and Microsoft Project where a Work Plan can be exported, edited externally, and imported back while preserving internal AdaptiveWork identifiers and structure.Currently, while export to MS Project (XML) and re-import is supported, AdaptiveWork does not retain system-specific identifiers such as Task IDs, Milestone IDs, Task Types, or template inheritance when the project is modified in MS Project and imported back. This limits customers who use fixed hybrid/waterfall templates and rely on consistent IDs and task structures for governance and reporting.Requested Capability: Preserve AdaptiveWork Task IDs and Milestone IDs across MS Project export and re-import Maintain Task Types and template structure during round-trip updates Support reliable mapping of modified tasks back to the original AdaptiveWork Work Plan Business Impact: Enables hybrid and waterfall project teams to use MS Project without losing A

Customers across manufacturing, R&D, and IT project environments are requesting deeper skill-based resource management capabilities within AdaptiveWork. While the product provides strong role-, job-title-, and user-based planning, customers need skills and competencies to become first-class planning dimensions.The proposed enhancement includes the following capabilities:    1.    Skill Proficiency Levels    •    Support proficiency attributes for skills (e.g., Beginner/Intermediate/Expert, Level 1–5, or custom frameworks).    •    Enable proficiency-based matching and capacity analysis.    2.    Skill Requirements on Projects, Tasks, and Staffing Requests    •    Allow projects, tasks, and staffing requests to define required skills and proficiency levels.    •    Automatically match available resources based on skill fit.    •    Highlight skill gaps or insufficient capacity.    3.    Skill-Level Capacity, Utilization, and Workload Visibility    •    View workload, utilization, an

When using the Data Loader to perform bulk project uploads, the system currently allows duplicate project records to be created if existing projects are unintentionally included in a new upload file. There is no built-in validation or safeguard to prevent duplicates based on common identifiers such as Project Name or External ID unless the user explicitly uses PK-based updates.This behavior increases the risk of data integrity issues, especially for customers who perform recurring bulk uploads and manage large project portfolios.Current Behavior: Data Loader accepts rows for project creation even if a project with the same Name or identifier already exists. Preventing duplicates relies entirely on manual validation or file preprocessing by the customer. There is no configurable option to block or warn users when duplicate projects are detected during upload. Desired Behavior:Introduce an option to detect and prevent duplicate project creation during bulk uploads by: Validating agai

Customers require the ability to enforce the “Highlight Changes” setting globally so that it is enabled by default for all projects and users without requiring manual activation by each Project Manager.Currently, the toggle is available only at the project instance level under Work Plan → Settings → Highlight Changes. There is no organizational, profile-level, or systemic default that allows administrators to configure this behavior across the entire environment.Business Need / Justification: Ensures consistent behavior across all projects. Reduces missed changes in schedules and improves governance. Eliminates repetitive manual steps for PMs. Supports large organizations where enforcing standard configuration per project is operationally inefficient. Requested Enhancement: Add a global Admin-level setting that allows enabling “Highlight Changes” as the default for all new and existing projects. Optionally, allow applying the setting by: Organization Profile/User Role

our custome would like AdaptiveWork to be able to provide a native system field on the Customer object that automatically counts all Projects related to that Customer.Currently, this capability exists only at the Portfolio level, and organizations must use a custom Relations Summary field if they want this count at the Customer level.The customer has a custom field called “# of Projects”, configured as a Relations Summary counting all associated Projects.This field is intended to support reporting across 150+ Customer records. However: The field has repeatedly displayed ?ERROR, requiring Support to manually recalculate the field.The customer assumed this was a system-provided field and expressed concerns about reliability.They believe counting linked Projects is core platform functionality and should not rely on a custom implementation. Requested Enhancement Create a standard AdaptiveWork system field on the Customer module that:Automatically counts the number of Projects linked to eac

As of right now, the only way that I think I’d be able to track skill proficiency levels is by creating a new skill for each level of proficiency. It would be great if Adaptivework had a way to track proficiencies within each skill.Also, being able to sort the capacity planning module by skill would help identify future demand/internal capacity for hiring decision making.

Currently, AdaptiveWork does not provide the ability to include page numbers in PDF extracts. Users exporting reports or documents in PDF format cannot reference specific pages, which affects readability and usability, especially for larger files shared with multiple stakeholders.Proposed Enhancement:Introduce an option to automatically include page numbers when generating PDF extracts. The feature could allow users to configure the page number placement (e.g., header or footer) and formatting style (e.g., “Page X of Y” or simple numbering).Business Justification:    •    Improves document readability and navigation.    •    Enhances professional presentation for exported reports.    •    Facilitates easier reference and discussion of specific pages in printed or shared documents.    •    Aligns with standard document export expectations in enterprise applications. 

When evaluating and prioritizing new product projects, it is typical to analyze profitability.  Such a common metric is calculating Net Present Value (NPV), while extension may be Break-even, IRR, etc.This functionality seems to be missing in the financial planning aspect of AdaptiveWork.  Is it possible to add in such functionality of calculating an NPV for various time periods (e.g., 10-year and 5-year NPVs_?Has anyone built their own profitability report inclusive of the time value of money based on the standard profitability fields that they can share? Thank,Ginger

In Planview AdaptiveWork, the Resource Load view currently displays data over a rolling 12-month period.Our customer, EDF Solutions Solaires, requires the ability to:View and plan workloads by full calendar year (e.g., all of 2025, 2026, etc.).Extend visibility beyond the current 12-month limit, ideally without restriction or at least across a multi-year horizon.This enhancement would significantly improve long-term capacity planning and portfolio forecasting, especially for organizations that plan staffing and project demand several years in advance.Suggested improvement:Allow configuration of the Resource Load view’s time range byenabling users to define a custom date range (up to 36 months or 48 months etc),Business impact:This capability is important for EDF’s long-term capacity planning and portfolio forecasting.

Currently, the AdaptiveWork Data Warehouse (DWH) process automatically performs incremental data loads after the initial full extract. Customers have no option to manually initiate a full extract when needed.Several use cases such as new integrations, go-live transitions, or troubleshooting data inconsistencies require the ability to perform a full extract on demand.Business Justification:• Enables customers to self-manage data refresh needs, especially during go-live or post-configuration changes.• Reduces dependency on Support for DWH resets.• Improves turnaround time and flexibility for teams integrating AdaptiveWork data into downstream analytics and AI platforms.• Minimizes project delays due to partial or outdated data during key milestones.Proposed Enhancement:• Add a configuration option (via UI or API) to select between:• Full Extract: Pulls all data for all configured objects.• Incremental Extract: Pulls only changes since the last successful run.• Optionally include scheduli

Many of my colleagues speak Italian as prior primary language and struggle with English. Would it be possible to add Italian language to AdaptiveWork?

We would like to raise an enhancement request based on customer feedback regarding the way forecast revenue is currently calculated in AdaptiveWork.At present, the system’s financial model calculates forecast revenue at the project level, using the formula:Planned Billed Expenses + MAX(Expected Revenue, Revenue EAC) × Cost Allocation (%)This calculation is applied regardless of the state of individual tasks. As a result, tasks in “Draft” or “On Hold” which still have planned effort and billing rates continue to contribute to financial forecasts.From a business standpoint, this can be misleading, since Draft or On Hold tasks do not represent confirmed or active work and therefore should not inflate projected revenue.Customer Request:Introduce a system option (or enhancement to the Update Forecast logic) that allows organizations to exclude Draft and On Hold tasks from forecast calculations. This would provide more accurate and realistic financial projections, particularly for customers