"Incomplete" is not a valid bug status

[Daniel Holbach]

According to https://launchpad.net/+apidoc/devel.html#bug_task "Incomplete" is a valid task status. It seems that the correct bug statuses for "Incomplete" are "Incomplete (with response)" and "Incomplete (without response)".

IMO the docs should be updated and a error thrown (or maybe the sum of both Incomplete statuses shown?)

Thanks.

[Julian Edwards (julian-edwards)]

The docs are correct, it's supposed to map the "Incomplete" to "Incomplete (without response)" internally when setting.

[Gary Poster (gary)]

Hi Daniel. I can't duplicate on a local instance with the most recent version of launchpadlib.

>>> t = bug.bug_tasks[0]
>>> t.status = u'Incomplete'
>>> t.lp_save()
>>> bug.bug_tasks[0].status
u'Incomplete'

(I also verified through the browser that the change had been applied.)

When doing this I noticed that the following does not work, which really is nasty:

>>> bug.bug_tasks[0].status = u'Incomplete'
>>> bug.bug_tasks[0].lp_save()
>>> bug.bug_tasks[0].status
u'New'

Yuck. That's because bug.bug_tasks[0] is a different object each time. :-(

Could you let us know what version of launchpadlib you are using, or any other details you can think of that might help? This should do the trick for getting the version:

python -c 'import launchpadlib; print launchpadlib.__version__'

Thanks!

[Leo Arias (elopio)]

I think Daniel is referring to bug #922769.