+1 This would be very beneficial for using Pagure to manage development and things like the Changes process, where state matters and is fluid.

+1 This would be very beneficial for using Pagure to manage development and things like the Changes process, where state matters and is fluid.

I envision per-repo board that can be optionally filtered by milestone and use the repo's issue statuses as columns. Each issue would be a card that shows some of the metadata (owner, labels)

While not kanban (or taiga integration), the milestones / roadmap pages in master are now quite a bit different:

https://pagure.io/pagure/pull-request/3311

Would the idea here be to integrate directly with a specific taiga instance? or implement a kanban-style page directly in pagure?

Note:
- taiga integration has been asked in https://pagure.io/pagure/issue/266
- the kanban board style representation of the tickets was asked in https://pagure.io/pagure/issue/1727

I'm kinda leaning more for the second than the former since it would allow a kanban bord approach in pagure rather than relying on 3rd party but on the other side it's also more code to maintain in pagure.

The milestone and roadmap pages are good, and certainly cover some of the use cases, but card style views would certainly help. I'd suggested taiga, mainly because there's API access, just as there is with trello, so adding in a modular/configurable interface would allow (hopefully) minimal additional code creation, as well as a pluggable arch.

Taiga's also used by rcm and so would require less effort to convince them to change. I'm not opposed to writing a new system, but I don't see the full value of it unless the integration piece is more challenging than envisioned.

No comments or progress in four years, for the same reason the related issues where closed. As far I can see no one ever started working on an integration or contributed some code, going to close the issue.