Submitted by davet on 2011/04/10 18:06
 
  1. Entering and End date that is earlier than a Start date draws a Gantt bar (illegal operation)
  2. You can manually enter a Task ID (Would be better if it were write protected and auto generated) See comments below.
  3. Task IDs do not show until a dependency is made. (Task ID should show when task is created)
 
 
 
Dave

Comments


[quote]
Entering and End date that is earlier than a Start date draws a Gantt bar (illegal operation)
[/quote]
 
This is an old issue I've got on my list and postponed putting in Mantis for ages... I'd say go for it.
 
[quote]
You can manually enter a Task ID (Task ID should only be auto generated)
[/quote]
 
I haven't thought of all possible repercussions of a read only TaskID, but it sounds like a reasonable constraint.
(Note that you can turn on the readonly option for the field anytime)
 
[quote]
Task IDs do not show until a dependency is made. (Task ID should show when task is created)
[/quote]
 
Seems like the proper way to handle it.
 
 
--------------------------------------------------------------------------------
Windows XP Home Edition, Service pack 2
Dell Vostro 1500, Ram:3gb, CPU:Core2Duo T7500 2.2ghz

davet

2011/04/10 23:36

Permalink

Armando,
 
Thanks for the feedback. I took another look at Task ID functioning. Now I see that when I manually set the TaskID, the NextTaskID changes (Successor). Consequently it keeps the successor synced to the TaskID...so, think it will work okay as is. However, I think it would be less confusing if the TaskID were auto generated and write protected. I guess it's up to Pierre to make a call on this.
 
Dave

Hi Dave,
 
Regarding your list:
  1. Relationship and rules between start and end is best done through equations. I've updated the sample database with proper equations
    (the reason being that Gantt charts can be based on any date fields and you may not want to always enforce such these rules)
  2. In v0.9.25P4, I've improved the TaskID generation and checking (duplicates are not allowed, but you can re-use unused numbers)
  3. There is no such thing as a "task" in IQ, only items, and not all items are tasks. So only when required are TaskID assigned.
    (you can however create auto-assign rules to have some items (i.e. all items in a grid) automatically get TaskIDs.)
HTH
 

davet

2011/04/11 19:54

Permalink

Pierre,
 
I'm a little confused. It sounds like maybe you are saying that Tasks are just Items, so you don't need a Task ID unless you create a dependency. And, therefore no TaskIDs will be generated until a dependency has been created. Is that true?
 
Regarding the Gantt that is created when I enter and End date that is sooner than a Start date.  Will this continue to work the way it does now? That is will a Gantt bar to be drawn if I enter an End date that is earlier than a Start date?
 
Also, will Gantt charts work differently if I build a Project grid from scratch rather than modify the Projects grid in the Sample database? If so, how will the user know what differences to expect?
 
Dave

Pierre_Admin

2011/04/11 23:27

Permalink

Hi Dave,
  1. Exactly ! TaskIDs are used for Gantt dependencies and for Next Task Actions (actions when an item is marked done, set in Options >> Database
  2. In the new sample database, VBScript equations prevent end < start
  3. No, Sample database or Blank should work the same.
 

davet

2011/04/12 00:10

Permalink

Thanks...that all sounds well and good!