Changing user story status moves the user story to the Unclassified swimlane

[abelizarov-nicct]

Description

If I change user story status with Python API, the user story moves to the Unclassified Kanban swimlane. This happens with both https://api.taiga.io and local hosted Taiga.

Steps to reproduce

The code is like this:

from taiga import TaigaAPI

api = TaigaAPI(host=...)
api.auth(username=..., password=...)
project = api.projects.get_by_slug(project_slug)
story = project.get_userstory_by_ref(user_story_key)
story.status = new_status_id
story.update()

Versions

• Python 3.10.12.
• Taiga Python API library: 1.3.0

Expected behaviour

The status of the user story should change. The story should move in the Kanban swimlane to the new state. The swimlane should not change.

Actual behaviour

The status of the story does change. This is correct.

But the user story also moves to the Unclassified swimlane. This is incorrect.

Additional information

If I change the status in Web UI, the user story stays in its swimlane.

I tried to change the user story swimlane:

story.swimlane = new_swimlane
story.update()

This only works if new_swimlane=None, then this moves the story to the Unclassified swimlane.
If new_swimlane is an integer id of the swimlane, this doesn't work.

[protoroto]

@abelizarov-nicct Thanks for reporting this: I'll notify when a new version with the fix is released

[protoroto]

@abelizarov-nicct I've just released 1.3.1 version that should address this issue. Could you please check if everything is working as expected now?

[psybers]

@protoroto I can confirm the old behavior/bug, as well as it working fine in the latest release.

[protoroto]

@psybers That's good! @abelizarov-nicct I'm going to close this issue, feel free to open a new one if you're experiencing this problem again.