Idea Delivered
over 1 year ago

Modifying a due date of a project awaiting approval

Hello,

Our client AGCO would like to have a possibility to change project due date in ManTra after a project has been created but before the approval. It is because they often create a project, set a due date for example in 7 days' time but approve it after a month or so, and in such cases the deadline is no longer valid. 

Thank you for taking it into consideration,

Daria

Parents
  • Hi Daria,

    Many thanks for your suggestion and my apologies for not responding to you sooner.

    I can think of a couple of alternative solutions here: -

    1) We allow users to edit the project due date field directly in ManTra prior to a project being authorized. With this approach, we would lose visibility of the original due date(s) set for a project. Do you consider this an issue? Do we also need to consider the implications from a Project Manager's point of view? For example, what if the client user modified the due date of a project while it was pending authorisation but the new date requested was not feasible from a delivery perspective?

    2) TMS provides Project Managers with the ability to enter an estimated duration for a project. Where provided, this duration is used to populate an Estimated Delivery Date field in TMS at the point the client approves the project. i.e. the Estimated Delivery Date is set to the date the project is approved + the Estimated Duration. In this scenario, the originally requested due date remains untouched. We don't currently expose the Estimated Duration or Estimated Delivery Date fields through the ManTra UI. I would be prepared to consider this as a possible enhancement, however, if you think this would meet the requirement for your customer?

    Cheers,

    Ian

Comment
  • Hi Daria,

    Many thanks for your suggestion and my apologies for not responding to you sooner.

    I can think of a couple of alternative solutions here: -

    1) We allow users to edit the project due date field directly in ManTra prior to a project being authorized. With this approach, we would lose visibility of the original due date(s) set for a project. Do you consider this an issue? Do we also need to consider the implications from a Project Manager's point of view? For example, what if the client user modified the due date of a project while it was pending authorisation but the new date requested was not feasible from a delivery perspective?

    2) TMS provides Project Managers with the ability to enter an estimated duration for a project. Where provided, this duration is used to populate an Estimated Delivery Date field in TMS at the point the client approves the project. i.e. the Estimated Delivery Date is set to the date the project is approved + the Estimated Duration. In this scenario, the originally requested due date remains untouched. We don't currently expose the Estimated Duration or Estimated Delivery Date fields through the ManTra UI. I would be prepared to consider this as a possible enhancement, however, if you think this would meet the requirement for your customer?

    Cheers,

    Ian

Children
No Data