Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. General discussion

Due date cannot be set to future date

Added by Sameer I over 10 years ago

Hi,

I am facing a peculier issue. When I created a milestone it was not allowing me to select the due date anything other than start date. If I try to do so, OP throws following error:

Due date is not on start date, although this is required for milestones

Is this a bug in OperProject version 3.0.3?

-Sam


Replies (5)

RE: Due date cannot be set to future date - Added by Deleted user over 10 years ago

Hi Sam,
this is not a bug but a feature.
Like in every project planning system I know a milestone ist a one-day event.
Maybe you use a project phase?
Greetings Tom

RE: Due date cannot be set to future date - Added by Sameer I over 10 years ago

Thank you for reply Tom.

No, even if I select a new work package and select type as “Phase”, I get same error:

Due date is not on start date, although this is required for milestones

Regards,

-Sam

RE: Due date cannot be set to future date - Added by Sameer I over 10 years ago

Thomas Klahr wrote:
8<—-snip

btw, I understand a Milestone differently. Its an indicator of my project completion.

For example, Phase 1 of my project may define 5 milestones, each requiring different effort (in terms of PDs).
Each milestone may have multiple work items. Total time estimated to complete all work items in a milestone is the total time taken to reach a particular milestone. For reporting purpose, say, how much of the work is done for a particular milestone, it is important to have this kind of setup.

It can be different from the way you look at it. In any case even selecting the work package type as Task throws same error.

-Sam.

RE: Due date cannot be set to future date - Added by Niels Lindenthal over 10 years ago

Sameer I wrote:

Thomas Klahr wrote:
8<—-snip

btw, I understand a Milestone differently. Its an indicator of my project completion.

For example, Phase 1 of my project may define 5 milestones, each requiring different effort (in terms of PDs).
Each milestone may have multiple work items. Total time estimated to complete all work items in a milestone is the total time taken to reach a particular milestone. For reporting purpose, say, how much of the work is done for a particular milestone, it is important to have this kind of setup.

It can be different from the way you look at it. In any case even selecting the work package type as Task throws same error.

-Sam.

Hi Sam,
Each type (Phase, Milestone, Bug, Task etc.) has several settings. One of these settings is “mark type as milestone”. If this setting is enabled both dates need to be the same.

You can check the settings in Modules -> Administration -> Types -> “Type”.

Regards
Niels

RE: Due date cannot be set to future date - Added by Sameer I over 10 years ago

Hi Niels,

Thank you. You nailed it.

That solved my problem.

-Sam

  • (1 - 5/5)
Loading...