Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed milestones #125

Open
GoogleCodeExporter opened this issue Jun 28, 2015 · 10 comments
Open

Fixed milestones #125

GoogleCodeExporter opened this issue Jun 28, 2015 · 10 comments

Comments

@GoogleCodeExporter
Copy link

I would like to be able to fix the date of a milestone.

Currently, milestones can be moved around by the scheduler. But if I have a 
milestone which needs to be met at a fixed point (due to project restrictions) 
it would be convenient that the scheduler is not able to move it around due to 
dependencies on other tasks!

Even better: possibility to schedule tasks which are predecessors of fixed 
milestones correctly as well!

Original issue reported on code.google.com by maarten....@gmail.com on 17 Jun 2010 at 3:00

@GoogleCodeExporter
Copy link
Author

The second is in fact the whole new feature, "backward scheduling", so it makes 
sense to create a separate issue for that. Fixing milestones seems to be doable 
in the short term

Original comment by dbarashev on 18 Jun 2010 at 4:32

  • Added labels: Tasks

@GoogleCodeExporter
Copy link
Author

Original comment by dbarashev on 23 Jun 2010 at 10:50

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

If it also would be possible make a fixed time period for a task, the software 
would be enhanced a lot.

I work in public management, and we mostly have 8 weeks of public hearings, so 
this time period needs to be fixed.

Original comment by madsb...@gmail.com on 17 Feb 2011 at 11:46

@GoogleCodeExporter
Copy link
Author

Already implemented by the issue_125 branch :)

When the code changes are correct, we will merge it into the default branch and 
it will be available in a next release.

Original comment by maarten....@gmail.com on 17 Feb 2011 at 12:08

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

This looks intense. What's the cost for you building your house now? Do you 
like using the milestone app to update what you are doing? It seems helpful. 

Original comment by neltje...@gmail.com on 7 Jun 2011 at 8:33

@GoogleCodeExporter
Copy link
Author

What is the state of this issue? How can I fix the date of a milestone in 
2.5beta?

Original comment by BruhnDom...@gmail.com on 13 Jan 2012 at 12:01

@GoogleCodeExporter
Copy link
Author

   Any progress on fixing milestones or creating tasks of fixed lengths?  I'm trying to work backward from a fixed commitment date to see how to organize all the activities that need to be accomplished prior to that date. Fixing task lengths as stated in comment #3 would also be useful.
   I can anticipating one issue you might encounter in programming this feature is that you create the possibility of setting an unsolvable schedule.  For example, if I set a start-finish condition on a task with a fixed time period of 10 days that has a fixed end date milestone five days away from the predecessor, there would not be enough days available to complete the fixed length task before reaching the fixed milestone.  
   In this situation I'd suggest that you put in an error handler that would bring this condition to the user's attention in the form of a message detailing the condition and then perhaps undo the last change which generated the error.  This could prove to be a very powerful feature which would alert the user to a scheduling conflict that might have otherwise gone unnoticed.  

Thanks for all the great work!  

Original comment by philipfr...@gmail.com on 26 Mar 2012 at 3:32

@GoogleCodeExporter
Copy link
Author

What do you guys mean when you say "fixed length"? GanttProject tasks have 
fixed length, unless you explicitly change it.

Backward scheduling is not yet supported. I created a separate issue #468

Original comment by dbarashev on 26 Mar 2012 at 6:43

@GoogleCodeExporter
Copy link
Author

I'm a big supporter of fixed milestones/tasks. My suggestion to implement it: 
in the task-properties dialogue/predecessor-setting called dependency (last 
column; option "hard" and "soft". For backward scheduling it would be 
convenient imho to be able to choose "hard backward" --> the predecessor is not 
able to move that task forward. Could that work out?

another idea to implement this would be to have a checkbox next to the date 
entries, by checking the box you nail the start/enddate and make it immovable. 

imho it would be great to be able to fix not only milestones but also tasks. 
Some tasks just have to be done in certain months, e.g. depending on seasonal 
waterlevels etc.


(hope my idea is understandable - have to translate the wording from the german 
interface to english)

Original comment by kaeptn.haddock on 4 Dec 2012 at 7:52

@GoogleCodeExporter
Copy link
Author

I too am very interested in fixed date tasks. I find that milestones can be 
moved fwd and back by dependencies, even though I type in a date.

I use the software to plan my time and there are certain things that have to be 
done on certain days so when those tasks move with dependencies rather than 
stay fixed it affects my whole schedule.

Does the /task properties/general/additional constraint allow this to be fixed?

Original comment by ywain.ap...@gmail.com on 30 Jan 2014 at 2:45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant