Currently it seems impossible to move a task within projects. So if you create a (sub-)task and later recognize that it does not have the right relation to the a parent project, that can't be changed by normal UI.

Or have I overseen something?

A better solution than hiding this reference field would be to make it accessible under "advanded". What do you think?

Comments

manuelBS’s picture

manuelBS commented
Status: Active » Needs review

Did you check the Tasks-Tree of each project or subtask list? There you can move the tasks with drag&drop. Does this work for you?

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Status: Needs review » Needs work

No I don't think so. What I meant is not to move the task within a project, but from one project to another (for example because a task was created in the wrong project!).

I think a solution would be to make a field "parent project" on the task edit page visible?

manuelBS’s picture

manuelBS commented

Yes this will be a solution. But if there are already timetrackings on the project or billables created this may lead to inconsitency. So I am not sure yet if this is a good thing. And other opinions?

dm_mash’s picture

dm_mash commented

I agree that this would be a useful feature. We are trying to also use ERPAL for tracking some everyday to-dos which do not belong to any other project, are limited to 1-2 tasks and do not deserve setting up separate projects for them. For this matter we have a pseudo-project containing these tasks. But from time to time such tasks can grow bigger and get some unanticipated development. That's where they should get their own project!
Maybe our use case is not typical, but still..

Speaking about possible inconsistencies... at least there could be a warning label next to this field. Isn't moving timetrackings, billables etc. also possible somehow?

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented

@#4: This is not as special as you think. We're doing the same and by the way, this could be an interesting general point for the future ;)

dm_mash’s picture

dm_mash commented
Issue summary: View changes

As a workaround in our installation we enabled altering field_project_ref from comments. All goes well so far, existing timetrackings go to new project too. Subtasks, billables, etc. are not tested though.

manuelBS’s picture

manuelBS commented

Subtasks and need to change the project_ref, too. Anyway the views should work. As timetrackings are only referenced to the task, they will will move to you new project including billable.
You need just to take care that you may get in trouble if your new project's price mode does not allow to set timetrackings to "billable". Your customer will not like this but ERPAL will not prevent this.