Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
abelizarov-nicct opened this issue May 27, 2024 · 0 comments

Comments

@abelizarov-nicct
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant