Repository navigation
Feature request: manipulate project issue status #3295
Description
Description of the problem, including code/CLI snippet
My team is currently moving to tracking issues using the issue status introduced in Gitlab 18.2:
https://about.gitlab.com/releases/2025/07/17/gitlab-18-2-released/#custom-workflow-statuses-for-issues-and-tasks
My company uses this library to automate opening gitlab issues. Below is a snippet from said automation. I tried to get at what I could send in the create() method by dumping issue to JSON and got the following (company info redacted)
{
"id": 177073754,
"iid": ...,
"project_id": ...,
"title": "...",
"description": "...",
"state": "opened",
"created_at": "2025-11-13T21:49:44.290Z",
"updated_at": "2025-11-13T21:49:44.290Z",
"closed_at": null,
"closed_by": null,
"labels": [
...
],
"milestone": {
"id": 4775912,
"iid": ...,
"project_id": ...,
"title": "Development",
"description": "Development (non-production) work that has yet to merge.",
"state": "active",
"created_at": "2021-10-01T18:45:11.056Z",
"updated_at": "2025-02-27T21:17:20.634Z",
"due_date": "2030-06-30",
"start_date": "2026-06-01",
"expired": false,
"web_url": "..."
},
"assignees": [],
"author": {
"id": 31427160,
"username": "project_..._bot_...",
"public_email": null,
"name": "...",
"state": "active",
"locked": false,
"avatar_url": "...",
"web_url": "..."
},
"type": "ISSUE",
"assignee": null,
"user_notes_count": 0,
"merge_requests_count": 0,
"upvotes": 0,
"downvotes": 0,
"due_date": null,
"confidential": false,
"discussion_locked": null,
"issue_type": "issue",
"web_url": "...",
"time_stats": {
"time_estimate": 0,
"total_time_spent": 0,
"human_time_estimate": null,
"human_total_time_spent": null
},
"task_completion_status": {
"count": 1,
"completed_count": 0
},
"weight": 1,
"blocking_issues_count": 0,
"has_tasks": false,
"_links": {
"self": "...",
"notes": "...",
"award_emoji": "...",
"project": "...",
"closed_as_duplicate_of": null
},
"references": {
"short": "...",
"relative": "...",
"full": "..."
},
"severity": "UNKNOWN",
"subscribed": true,
"moved_to_id": null,
"imported": false,
"imported_from": "none",
"service_desk_reply_to": null,
"epic_iid": ...,
"epic": {
"id": ...,
"iid": ...,
"title": "..",
"url": "",
"group_id": ...
},
"iteration": null,
"health_status": null
}
Unfortunately, I was not able to discern from this information how to set the status. Please let me know if it exists and this is a case of user error.
Expected Behavior
issue: ProjectIssue = jointsProject.issues.create(
{
'title': issueTitle,
'description': issueDescription,
'status': 'Approval Queue', # This is what I'd like to work, or some equivalent
'labels': [ ],
'milestone_id': developmentMilestoneID,
'epic_iid': epicID,
'weight': 1,
}
)
Actual Behavior
Specifications
- python-gitlab version: 7.0.0
- Gitlab server version (or gitlab.com): GitLab Enterprise Edition 18.6.0-pre b618d849058
Activity
totternessZB commentedon Nov 13, 2025
I'm not sure if this library is using REST or GraphQL under the hood, but it appears as though this feature hasn't even made it into the REST API yet.
https://gitlab.com/gitlab-org/gitlab/-/issues/560083
I've subscribed to that issue and will poke the issue here whenever that gets merged.
github-actions commentedon Jan 16, 2026
This issue was marked stale because it has been open 60 days with
no activity. Please remove the stale label or comment on this
issue. Otherwise, it will be closed in 15 days.
As an open-source project, we rely on community contributions to
address many of the reported issues. Without a proposed fix or
active work towards a solution it is our policy to close inactive
issues. This is documented in CONTRIBUTING.rst
How to keep this issue open:
investigate a fix, please comment and let us know.
solution, that would be fantastic.
will also prevent closure.
We value your input. If you can help provide a fix, we'd be happy
to keep this issue open and support your efforts.
This is documented in CONTRIBUTING.rst
https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst
totternessZB commentedon Jan 16, 2026
Issue has had no activity due to the REST API still not being implemented. See the gitlab issue above. Once that is resolved, this can actually be completed
github-actions commentedon Mar 18, 2026
This issue was marked stale because it has been open 60 days with
no activity. Please remove the stale label or comment on this
issue. Otherwise, it will be closed in 15 days.
As an open-source project, we rely on community contributions to
address many of the reported issues. Without a proposed fix or
active work towards a solution it is our policy to close inactive
issues. This is documented in CONTRIBUTING.rst
How to keep this issue open:
investigate a fix, please comment and let us know.
solution, that would be fantastic.
will also prevent closure.
We value your input. If you can help provide a fix, we'd be happy
to keep this issue open and support your efforts.
This is documented in CONTRIBUTING.rst
https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst
totternessZB commentedon Mar 18, 2026
commenting to prevent from going stale. Comment here still applies
github-actions commentedon May 18, 2026
This issue was marked stale because it has been open 60 days with
no activity. Please remove the stale label or comment on this
issue. Otherwise, it will be closed in 15 days.
As an open-source project, we rely on community contributions to
address many of the reported issues. Without a proposed fix or
active work towards a solution it is our policy to close inactive
issues. This is documented in CONTRIBUTING.rst
How to keep this issue open:
investigate a fix, please comment and let us know.
solution, that would be fantastic.
will also prevent closure.
We value your input. If you can help provide a fix, we'd be happy
to keep this issue open and support your efforts.
This is documented in CONTRIBUTING.rst
https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst
totternessZB commentedon May 18, 2026
commenting to prevent from going stale. Comment here still applies
github-actions commentedon Jul 19, 2026
This issue was marked stale because it has been open 60 days with
no activity. Please remove the stale label or comment on this
issue. Otherwise, it will be closed in 15 days.
As an open-source project, we rely on community contributions to
address many of the reported issues. Without a proposed fix or
active work towards a solution it is our policy to close inactive
issues. This is documented in CONTRIBUTING.rst
How to keep this issue open:
investigate a fix, please comment and let us know.
solution, that would be fantastic.
will also prevent closure.
We value your input. If you can help provide a fix, we'd be happy
to keep this issue open and support your efforts.
This is documented in CONTRIBUTING.rst
https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst
totternessZB commentedon Jul 20, 2026
commenting to prevent from going stale. Comment here still applies
github-actions commentedon Sep 19, 2026
This issue was marked stale because it has been open 60 days with
no activity. Please remove the stale label or comment on this
issue. Otherwise, it will be closed in 15 days.
As an open-source project, we rely on community contributions to
address many of the reported issues. Without a proposed fix or
active work towards a solution it is our policy to close inactive
issues. This is documented in CONTRIBUTING.rst
How to keep this issue open:
investigate a fix, please comment and let us know.
solution, that would be fantastic.
will also prevent closure.
We value your input. If you can help provide a fix, we'd be happy
to keep this issue open and support your efforts.
This is documented in CONTRIBUTING.rst
https://github.com/python-gitlab/python-gitlab/blob/main/CONTRIBUTING.rst
totternessZB commentedon Sep 21, 2026
commenting to prevent from going stale. Comment here still applies