Feature Description
The Gitea kanban board is a good tool for ordering issues, etc., as one does with a kanban board. The problem is that there is no API access to this ordering information, so it's impossible to integrate that information into other tools. In the age of agentic software engineering, this is a critical feature, as it is required to allow agentic systems to pick up work in the order in which it needs to be addressed and has been prioritized.
This isn't just for the development of new features or bug fixes, but it applies more broadly, because we already provide visibility of tags, which agents can easily filter on via API or, by extension, MCP, we are able to have them update issues, close, comment, attach them to PRs, etc., all by virtue of exposing features via the API. We can't have them move them between projects, nor properly file them when they are created, which is a problem when we want to have them assist with project management, work semi-autonomously, or even just want to use voice control to make things happen. As a user who uses voice control when their hands aren't cooperating, this is also an accessibility issue, and it's an easy one to solve!
Screenshots
No response
Feature Description
The Gitea kanban board is a good tool for ordering issues, etc., as one does with a kanban board. The problem is that there is no API access to this ordering information, so it's impossible to integrate that information into other tools. In the age of agentic software engineering, this is a critical feature, as it is required to allow agentic systems to pick up work in the order in which it needs to be addressed and has been prioritized.
This isn't just for the development of new features or bug fixes, but it applies more broadly, because we already provide visibility of tags, which agents can easily filter on via API or, by extension, MCP, we are able to have them update issues, close, comment, attach them to PRs, etc., all by virtue of exposing features via the API. We can't have them move them between projects, nor properly file them when they are created, which is a problem when we want to have them assist with project management, work semi-autonomously, or even just want to use voice control to make things happen. As a user who uses voice control when their hands aren't cooperating, this is also an accessibility issue, and it's an easy one to solve!
Screenshots
No response