Skip to main content
Answer

Past Staffing Requests have lock

  • November 18, 2025
  • 1 reply
  • 39 views
A
Silver Innovator
Forum|alt.badge.img+2

Hello,

Can someone please advise where’s the configuration/ setting for locking any past data, specifically staffing requests?

We have staffing requests that span past months, current and future months. The past months have lock and rightly so. Project Manager cannot make the past months staffing requests 0. Resource Manager (RM) cannot approve a request if it contains past months along with current and future months. So, what’s the options left?

The PM needs to delete the entire staffing request and create a new one with current and future months and then the RM can approve such a request. This eats into the PM’s time.

So how to tackle this problem (other than requesting RMs to approve/ reject on time?) I was hoping that the past months’ data for admin can be unlocked so that they can make it 0 and then the RM can approve.

With just the staffing requests lying there, I am pretty sure that no one can submit timesheet unless approved and the requests translate into project assignment.

Any help/ guidance will be highly appreciated.

Thanks

 

Best answer by Aayush

Hi Amit, 

The issue of locking past staffing requests and the inability to modify them is intentional within the system design. For staffing requests that include past months, the system does not allow approvals, and the recommended approach is to reject the request and create a new one for current and future months. This aligns with the best practices outlined for handling past data in staffing requests. 

If stricter enforcement or changes to this behavior are required, it may need to be logged as an enhancement request for future consideration to AW Product team.

    1 reply

    Aayush
    Planview Falcons
    Forum|alt.badge.img+4
    • Aayush
    • Community Manager
    • Answer
    • November 19, 2025

    Hi Amit, 

    The issue of locking past staffing requests and the inability to modify them is intentional within the system design. For staffing requests that include past months, the system does not allow approvals, and the recommended approach is to reject the request and create a new one for current and future months. This aligns with the best practices outlined for handling past data in staffing requests. 

    If stricter enforcement or changes to this behavior are required, it may need to be logged as an enhancement request for future consideration to AW Product team.

    A
    Terms of UseCookie settingsAccessibility statement
    All Data Subject Access Requests (DSARs), and requests of “Do Not Sell My Personal Information” according to the CCPA, must be submitted through the Planview DSAR portal located here

    Planview has appointed a Data Privacy Officer (DPO) to be responsible for overseeing our Privacy Management Program and related privacy compliance measures. DPO can be contacted at privacy@planview.com