Changing project-organization relationship causes problems
jurgenhaas - October 6, 2009 - 10:41
| Project: | Storm |
| Version: | 7.x-1.x-dev |
| Component: | Storm.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Magnity |
| Status: | closed |
Description
When I apply for new projects, I initially create a new project in Storm and assign that to a dummy organization. Only if and when I get the order for the project do I create the real organization and reassign that project to this new org, which now is a customer.
Problem is, that all attached notes, etc. still come with the assignment of the correct project and the dummy organization. Which means that those notes are never displayed in Storm anywhere anymore.
This means, when changing the org of a project, all other nodes need to be checked and updated too.
#1
Is anyone up for this?
#2
Hi Jurgen,
Personally I've got a lot on at the moment so it would be a case of getting to this (as with all the other issues) when time permits.
If anyone else wants to write a patch that'd be great too. It should be a case of either doing some processing on node_update or firing a hook on node_update for other modules to sort themselves out. I'd prefer the latter though.
#3
here is the patch for updating organization automatically for tasks, tickets and notes (basically it is the same code). it is not the best solution, but it is a start.
#4
Looks like a good start - although i'm a bit confused as to why the
$tasks = array();lines keep popping up.Obviously we'd need to put something in on update of tasks and tickets too.
#5
Assigning to self - have coded about half of this (live on demo site), and will commit once its all finished.
#6
Attached patch should fix Drupal 6 branch. Will roll in -dev version from midnight.
Needs porting to Drupal 7.
(Drupal 7 branch is currently unstable but needs to keep up with changes).
#7
Committed to D7 (HEAD)
#8
Automatically closed -- issue fixed for 2 weeks with no activity.