we have some peculiarities in projects, projectdesigner and importasks from project which are clearly bugs or at least undesirable. They make task import go crazy. 1) projectdesigner allows to set start date after end date (bug). whereas addedit does a validity check. 2) project addedit allows to set task start date ealier than project start date. That might be desirable or not? I could envision some rare occasions, but overall, this rather seems to be a bug. 3) point 2) drives task import crazy, because it does not maintain this task to be starting before official project start. This task is shifted to day after project start (?? why not same day??), so the overall project duration will be longer.\nNow, if we allow 2), then import must copy it without changing the project. Or we call 2) a bug and force users to backshift the project start if they add tasks starting before project start. I think we must do something concerning 2), as users adding tasks will rarely look at the project start dates. The minimum should be a warning (this task starts earlier than the official project start - do you want to shift the project start automatically?). KLaus

asked 16 Feb '14, 10:12

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

edited 16 Feb '14, 10:37


another bug: if I 'repair' the above mentioned dates, and set new project start to say Feb 12th, the first task is imported to Feb 13th. No peculiarities for that task, all times within working day etc. Same shift by 1 day occurs for the other tasks. Also, Feb 12th is not on a weekend, so no reason to shift to a (following) working day. maybe the + 1 is wrong here in importtasks:\n> $timeOffset = $original_start_date->dateDiff($project_start_date) + 1; I think another bug is that we shift to the next working day for UTC, not for the user's time zone. see:\n> $project_start_date = new w2p_Utilities_Date( $this->_AppUI->convertToSystemTZ($project_start_date)); $project_start_date->next_working_day(); Lastly, we might want to set $preserveHours to true in that call, so if we shift to another working day we do not change the times with respect to the original project Oh, and another one:\nwe would be safer if we shift all tasks by new project start - old project start.\nNow, we shift by new project start date - start date of first task of old project.\nThat start date of first task currently may be different from project start date, it could be later or earlier.\nI could envision offcial project start earlier than first task start, so that notification emails come up a little earlier. My feeling would be to use the offset between the two project start dates so that we have identical copies (However sane/insane those projects are).\nThe handling whether tsaks can start before/after project start should be done in addedit, not in importtasks. My overall comment is that this is not unusable, but peculiar and not correct either.\nIt seems nobody really uses it, because we never see bug report on this other than mine. How do others copy their projets or templates? Or does everybody manually adjust all these peculiarities? Klaus
permanent link

answered 16 Feb '14, 10:50

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

edited 16 Feb '14, 11:08

this removes some of the bugs in post 2: https://github.com/opto/web2project/tree/importtasks_date_weekday Now, if new project start = old project start, importtasks identically reproduces the dates of the old project. I think that would be the expected behaviour. Klaus
permanent link

answered 17 Feb '14, 08:24

opto's gravatar image

opto ♦
82341104131
accept rate: 10%

answered 17 Feb '14, 08:24

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
×25
×11
×3

question asked: 16 Feb '14, 10:12

question was seen: 397 times

last updated: 17 Feb '14, 08:24

powered by Bitnami OSQA