Closed GoogleCodeExporter closed 9 years ago
I expect you are trying to close the issue too after committing time?
It looks like the closing of the issue failes then.
I'll have to add logging functionality to better analyse this.
Could you verify the time is logged in redmine?
Thanks!
Original comment by bas.them...@gmail.com
on 17 Feb 2013 at 9:26
no time is not locked at all and checkbox for issue closing is not checked.
Original comment by fabismai...@gmail.com
on 17 Feb 2013 at 12:04
It's strange. The error in the screenshot only occurs if you try to update the
current selected issue.
It can occur at three points:
1. When checking to close the issue after committing time.
2. When starting/continuing time measurement and in settings enable to update
from state x to state y.
3. When updating an issue by editing it in the issue form.
After translating the German error to English, I got: "Parent task is not valid"
Which would mean the issue you are trying to alter/are measuring time for has a
parent issue.
In the API version linked to version 2.0.3.0 is a problem with parents in
issues.
The new(next) version is linked to a newer API version where this is fixed.
I think the time should be logged in Redmine; otherwise you should not get the
"Work logged successfully" but something like "Exception: <the server error>"
Kind regards
Original comment by bas.them...@gmail.com
on 20 Feb 2013 at 12:20
I am using redmine 2.2.3 and next version looks like to vert version 2.3. Did
you mean that?
> After translating the German error to English, I got: "Parent task is not
valid"
Thats correct.
>Could you verify the time is logged in redmine?
Time is not logged.
Howerver i have to check that there is no cross plugin bug which bugs api.
See https://github.com/kawasima/redmine_impasse/issues/195
Original comment by fabismai...@gmail.com
on 20 Feb 2013 at 12:56
If the 'not logging time' is caused by this plugin, you should also not be able
to update the issue (use an issue without parent ;) to test this).
The update-time is changed though, if I read the issue correctly.
Original comment by bas.them...@gmail.com
on 20 Feb 2013 at 1:22
The bug seems to be gone with 2.04 Will test deeper next week.
Original comment by fabismai...@gmail.com
on 22 Feb 2013 at 4:53
Any news on the bug? Is it solved?
Original comment by bas.them...@gmail.com
on 21 Mar 2013 at 12:26
I assume it is solved.
Original comment by bas.them...@gmail.com
on 6 Jun 2013 at 9:06
Original issue reported on code.google.com by
fabismai...@gmail.com
on 15 Feb 2013 at 11:23Attachments: