About dates for Issue: in Redmine we can determine the start date and the taskjuggler display this date as "start", and when we compute in Taskjuggler this date can moved. But for some issue we need fixed start date (it's important for us), and for this purpose we use TJ sheduled. If we use TJ sheduled we must have start date and end date in Redmine, because this dates displayed in tjp-file as "start" and "end". And when we compute in Taskjuggler this dates don't move. And we can use TJ sheduled for completed issue, if we use it in computing in Taskjuggler.
Maybe in the controller code I have unnecessary code line, but I want to test it when I will debug a program on test project.
I still don't understand for what we need TJ start time for Issue, but I think that it's not important for now.
I think that I must to write the Instruction how we want to use pluging and send it to you. After that, I think, you can understand what we want to obtain from using of pluging.
From namiko999:
About dates for Issue: in Redmine we can determine the start date and the taskjuggler display this date as "start", and when we compute in Taskjuggler this date can moved. But for some issue we need fixed start date (it's important for us), and for this purpose we use TJ sheduled. If we use TJ sheduled we must have start date and end date in Redmine, because this dates displayed in tjp-file as "start" and "end". And when we compute in Taskjuggler this dates don't move. And we can use TJ sheduled for completed issue, if we use it in computing in Taskjuggler. Maybe in the controller code I have unnecessary code line, but I want to test it when I will debug a program on test project. I still don't understand for what we need TJ start time for Issue, but I think that it's not important for now.
I think that I must to write the Instruction how we want to use pluging and send it to you. After that, I think, you can understand what we want to obtain from using of pluging.