Using dinamyc tasks and after updating some completion, the "father" task sets itself to 127%.

I have tasks with between 1-6 child tasks, with different advance in each ans some at 0%.

As soon as I change one task, the parent task goes to 127%

What can I do ?

Thanks.

asked 09 Nov '17, 13:33

Stinkin's gravatar image

Stinkin
2251216
accept rate: 21%


which w2p version? There was an error in w2p3.3.x. I think I corrected that for w2p3.4.

Klaus

permanent link

answered 13 Nov '17, 17:24

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

it is just the normal update process. not sure whether it needs db upgrades. you would see a notice in system manager.

For your test, that would probably even go without upgrade. Or copy the db, and config.php, and use both in a fresh installation.

Klaus

permanent link

answered 14 Nov '17, 02:12

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

I think it wrote the father child relationships wrong into the db.

If your chain of tasks is not too big: just edit and save each, without changes. Then, some things will be recalculated. Does it display correct them? -> that would mean wrong tasks stay wrong, but newly added ones will be ok.

permanent link

answered 15 Nov '17, 13:51

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

I'll try 3.4 and let you know. Should I do something else after unzipping and configuring ?

Thanks

permanent link

answered 13 Nov '17, 17:38

Stinkin's gravatar image

Stinkin
2251216
accept rate: 21%

Just finished installing 3.4 and still the issue stands. I created a new site, installed 3.4 and setup to use my DB (made a backup before). It said it finished updating buy still find 127% o 114% of advance in some task.

Thanks

permanent link

answered 15 Nov '17, 13:28

Stinkin's gravatar image

Stinkin
2251216
accept rate: 21%

edited 15 Nov '17, 13:28

In the screen the father-child are OK. I moved a small string of tasks A ->B ->C, removing the father of each one. Then I created the string again. No change.

At task_path_enumerator, the chain looks good

1510

1510/1537

1510/1537/1538

permanent link

answered 15 Nov '17, 14:10

Stinkin's gravatar image

Stinkin
2251216
accept rate: 21%

if you look at task__path_ enumerator in the db, are there any other (old) tasks having those three ids?

That was exactly the problem that task path enumerator was set incorrectly. Or maybe I did not push the fix to w2p34? Could be in opto3.3.66 or only locally here, or maybe evn lost in some branch and never uploaded,

permanent link

answered 15 Nov '17, 14:49

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

All the refereces to the tasks are inside the project.

I paste a sample of the task table.

task_id task_parent task_percent_complete task_path_enumeration 1510 1510 127 1510 1537 1510 127 1510/1537 1538 1537 100 1510/1537/1538 1539 1510 127 1510/1539 1540 1539 85 1510/1539/1540 1541 1510 0 1510/1541 1542 1541 0 1510/1541/1542

The task 1510 has many other childs, but 1537-1539-1541 only have 1 child.

Thanks for your time and patience Klaus.

permanent link

answered 16 Nov '17, 08:39

Stinkin's gravatar image

Stinkin
2251216
accept rate: 21%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×47
×1
×1

question asked: 09 Nov '17, 13:33

question was seen: 594 times

last updated: 16 Nov '17, 08:39

powered by Bitnami OSQA