Closed (cannot reproduce)
Project:
Storm
Version:
6.x-1.36
Component:
Storm Timetracking
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Feb 2011 at 18:13 UTC
Updated:
12 May 2011 at 00:24 UTC
My system is hierarchically organized in Organization => Project => Tasks => Tickets.
Ex “Organization X” => “Project Website Support” => “Task Interface” => “Ticket with a front end using issue”.
Each created ticket has different interventions which are registered as time-tracking for billing purposes.
Time-tracking is, in my understanding, the lowest hierarchic entry in management system and belows to assigned item. In this case it is the ticket.
When I move a ticket from project A to project B, the time-tracking doesn't follow the ticket. It has to be edited and manually moved.
Comments
Comment #1
francewhoaThe storm_contrib module makes it easier to move tickets. It might do what you need.
http://drupal.org/project/storm_contrib
Read more at http://drupal.org/node/817982
To access this feature you must activate the storm_contrib sub-modules titled 'stormticket_assigment'
Comment #2
juliangb commentedIf this is true, then it is a bug to be fixed in Storm rather than requiring any other modules.
@lamachine_fr, the code to automatically move the timetracking does seem to be there. Would it be possible to post some expanded step by step instructions so that this can be reproduced in an automated fashion?
Comment #3
ronline commentedHi juliangb .
The ticket can have attached Expenses and Timetrackings .
If the ticket is moved to another project and / or task and / or organization the attached value should follow.
I didn't test the task case, but I believe it should be the same. All belongings Expenses, Notes, Tickets, Timetrackings should follow the owner => in this case the “Task”.
Tell me if anything unclear.
Comment #4
juliangb commentedI'm talking about instructions a bit like http://drupal.org/node/1060514 if poss please. The more specific, the more it will help me work with you to identify and squash the bug!
Comment #5
ronline commentedSteps to reproduce :
Creating time tracking.
Go to http://website/storm :
Add new Storm Organizations => Organization X and Organization Y
Go to Storm => Organizations => Organization X => add Project X
Go to Storm => Organizations => Organization Y => add Project Y
Go to Storm => Organizations => Organization X => Project X => add Task X
Go to Storm => Organizations => Organization Y => Project Y => add Task Y
Go to Storm => Organizations => Organization X => Project X => Task X => add Timetracking X
Go to Storm => Organizations => Organization X => Project X => Task X => Timetracking X and open “Filtered by Organization” you can see that time tracking hierarchically belongs to Task X.
Migrating task.
Go to Storm => Organizations => Organization X => Project X => Task X => edit Task X => change dropdown value from Organization X to Organization Y.
Bug
The task has been moved to:
Organizations => Organization Y => Task X
but the time tracking still remains under
Organizations => Organization X => Project X
Comment #6
tchurch commented(Sorry I've not been around much but...)
I tested this using your steps.
I moved Task X to Org Y and I must give it a project (Proj Y). I do see Task X under Proj Y and also Time X still under Task X.
I don't see the bug.
I am testing on 1.36 though. Maybe it's not an issue in 1.36?
Comment #7
ronline commentedI am on storm 6.x-1.36
The issue appears if task doesn't move to new project.
So far as Task X sit under Org Y, the Timetracking X stick to the Org X.
Migration will be triggered only when Task X is moved to Org Y => Project Y.
Following the filter layout, timetracking belongs to task.
There are two possibilities:
1. Stick the timetracking to the task and move it where ever it goes.
2. Prevent moving a task without being assigned to new project.
Comment #8
juliangb commented@lamachine_fr, I've just tried this too. I took an example timetracking, moved the task that it relates to. The timetracking moved too. This seems to be as expected and per 1. of your possibilities in #7.
Could you please try this again to see if you still experience this? Perhaps you could also try following your instructions from #5 to the letter to ensure that this is exactly how you've reproduced the bug.
Any more information that will help us reproduce this would be very gratefully received, but otherwise we won't be able to fix anything if we cannot see the bug ourselves!
Comment #9
ronline commentedI've just reproduced the issue.
Create « Organisation X => Project X => Task X => Timetracking X » .
Create « Organisation Y => Project Y ».
Move task to « Organisation Y » so the logical path will be « Organisation Y => Task X » (not to « Organisation Y => Project Y => Task X!! »).
At this stage has the « Organisation Y => Taks X » no timetracking.
The timetracking move only when you manually migrate task to “Organisation Y => Project Y” so the logical path will become “ Organisation Y => Project Y => Task X” .
Fix :
1. Stick the timetracking to the task and move it where ever it goes.
2. Prevent moving a task without being assigned to new project.
I'm running storm 6.x-1.36 and Storm Contrib 6.x-1.x-dev .
Comment #10
juliangb commented@lamachine_fr,
Would you be able to test with the Storm Contrib modules disabled please? This will enable us to more accurately pinpoint where any problem lies.
When you are testing to see whether the timetracking has moved, are you looking at the timetracking node (and fields shown), or on one of the list pages?
Comment #11
ronline commentedIssues shows even with Storm Contrib modules disabled.
I'm looking at the timetracking node.
Comment #12
juliangb commentedI'm going to test this again.
Comment #13
juliangb commentedI've just followed through the instructions quite carefully, and all seems to work as it should.