Hi,

Project'Or RIA is one of the good solutions to help you.
My advice : Set your objectives as Projects and Actions as activities.
Your "complétude" should yhen be "Status".
Priority of Activity can be your priority.

One other option is to manage Actions as ... Actions.
You will loose the WBS numbering, but will have priority as you wish. (you can then define the WBS number in the name...)

Hope this will help you.

Thanks a lot for your reply !

1 - I think I will get xxx.x actions to be sub-sub-sub projects of my main objectives, as it shows nicely on the wbs similarly as my main document, and that each of those actions means quite a bit of work and is a real 'project' by itself. Wondering, though... if needed, can I reorder the wbs ?

2 - Now I think I will have to undestand better the differences between activities and actions at the software level... For example, one of our actions(project) have a planning already associated, with different key events distributed on a 2 years period. To see that planning visually, should I create as many activities or actions under that project as there are key dates ? Or should I use Jalons for that ?

well, back to testing, sounds really promising 🙂

Wondering, though... if needed, can I reorder the wbs ?

No if you manage actions as Actions, as you'll have to set WBS in the name of the action.
YES if you manage actions as Activities : you'll be able to move order in the Gantt planning view.

To see that planning visually, should I create as many activities or actions under that project as there are key dates ? Or should I use Jalons for that ?

As you wish...
The main differences are:
- Milestones have no stars date, only target date; Activities have both.
- Milestones have no duration
- Activities can be assigned to some work, to have planning calculated

Great !

thank you Babynus for the helpful clarifications.
the reordering was a bit tricky, but it really is easy !

1 - Solution is taking shape, I am crafting a planning.
I have some milestones that moved from their respective validated dates to today's date location after I pressed a button 'compute activity planning' (arghhh, why !) So I have milestones with the planned date set to today and could not find yet how to change...

2 - I saw a csv file to import activities, is it possible to use a similar one to populate my 200 projects and subprojects lines ?

well thanks again for your quick answers and time spent helping out

1 - Solution is taking shape, I am crafting a planning.
I have some milestones that moved from their respective validated dates to today's date location after I pressed a button 'compute activity planning' (arghhh, why !) So I have milestones with the planned date set to today and could not find yet how to change...

It is because of planning mode. The default planning mode for milestones is "floating", this means you must define a predecessor task, and the milestone will automatically move to the end of the task. Set planning mode to "fixed" and planned date will be set to your validated date.

2 - I saw a csv file to import activities, is it possible to use a similar one to populate my 200 projects and subprojects lines ?

Yes, you can import projects as easily as Activities. Just take care if the ids.
If you want to have project B sub-project of A you must know id of A to define idProject of B as id of A.

well, still progressing, and working on import, hoping not to spend more time on solution than creating all new. After some trials, I eventually had some little test file imported, but something is not right about wbs. (I used csv example as base, but had to insert a type column with the right id's value, something that was not obvious, after getting frustrated with 'invalid controls - type mandatory')

I imported a file (

) containing 4 lines, a sub project of a main one, a sub project for it, and 2 sub projects for the later. Imported project shows names, id, type and status as they should.

in the projects tab, they do show, with the right 'is a sub project of' listed, but wbs is not right, (instead of 2.1, 2.1.1, 2.1.1.1 and 2.1.1.2, they show as 3, 4, 5 and 6 respectively)
In planning view, the project names don't show up.

Any idea on what I should do to be able to import my projects with a correct wbs and project name ?

Hi,

I reproduced the behavior you describe.
It seems to be a bug on import.
Ticket #1178 recorded.

As a workaround : I just updated project 20 : reset "is sub-project of" to null and then set it back to correct value : all is fixed, even sub-projects of 20 are correctly updated automatically.

sad bug ! Thanks for your quick reply, though...
I saw the mentionned ticket #1178 in the track section, but can't add to it... Any way I could help ?

I imported a bigger test file, workaround does work, but only for reseted project line, not updating subs and such, quite a tedious work for 200+ projects...

In planning mode, if I click on a 'unnamed' project and save it, name then shows, but wbs is not corrected.

Lookind at database, it seems the actionsplanningelement table misses values for imported data (such as fields refname, topId, topRefType, topRefId), beside the wrong values in fields wbs and wbsSortable

Thnaks for this complemtentary infirmation.
I added it as a note to the ticket.
Will be some help to find a fixing...

would you have an idea where I should look to understand the import processs ? I have minimal knowledge about php and mysql but I may help somehow. Maybe there is just one column to fill in the import for the wbs to be calculated rightly :woohoo:

should I open a separate thread to get input from the forum ?

The main code for import is in /model/Importable.php, in the import() method.
But the issue may also be in the /model/PlanningElement.php.

I'll have a look as soon as I get some time...
(very busy this week, sorry)

Hi,

I found the fix.
Not easy to find :S

It is due to forcing of the ID (I really never use it on my projects).
In this case, the function called to save is ... $object->insert()...
Import is the only way that calls this function. Any other means use $object->save().
Unluckily, although $object->insert() realizes a save calling SqlElement::saveSqlElement, the save() method of all the objects is not called, so all calculated fields are not updated.

So the fix is : on /model/persistence/SqlElement.php, replace lines 307 and following from

  public function save() {
    return $this->saveSqlElement();
  }

  public function insert() { // Specific function to force insert with a defined id - Reserved to Import fonction
    return $this->saveSqlElement(false, false, true);
  }

to

  public function save() {
    if (isset($this->_onlyCallSpecificSaveFunction) and $this->_onlyCallSpecificSaveFunction==true) return;
    return $this->saveSqlElement();
  }

  public function insert() { // Specific function to force insert with a defined id - Reserved to Import fonction
    $this->_onlyCallSpecificSaveFunction=true;
    $this->save(); // To force the update of fields calculated in the save function ...
    $this->_onlyCallSpecificSaveFunction=false;
    return $this->saveSqlElement(false, false, true);
  }

This fix will be deployed on V3.5.0

Babynus the genius !

Great thanks for that quick fix !
I will try it now...