Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add endpoint to create new Deck Board and Lists within a Deck

Aperta
  • Qualcosa non va?
#241 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
72/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, tooling

Direzione di ricerca

Start in ex_app/lib/all_tools/deck.py by reading list_boards and add_card, then consult the linked Deck API documentation for the board and stack endpoints. Add confirmed tools for creating a board and a stack, returning the IDs needed by add_card. Done means both tools use the existing API base and expose the returned board or stack data.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using: 34.0.4 (Context Agent 2.8.0, Collectives 4.6.1)

Is your feature request related to a problem? Please describe.

The Context Agent can't create a Deck board or a list (stack) inside a board. It can only list the boards that already existed.

The Deck tools in ex_app/lib/all_tools/deck.py cover reading boards and cards (list_boards, list_board_cards, list_card_comments) and working with cards (add_card, add_card_label, assign_card_to_user, delete_card, and the card comment tools). All of the card tools need an existing board_id and stack_id.

An AI agent should be able work with a simple request like "set up a Kanban board for project X with To Do / In Progress / Done and add these tasks". At the moment, the Board and the Lists must be created manually by a human user.

Describe the solution you'd like

Add tools to deck.py that wrap the existing Deck REST API (/index.php/apps/deck/api/v1.0, the same base the current Deck tools use):

  • create_board(title, color): wraps POST /boards (title, color). It returns the new board's id, labels and stacks so the agent can go straight on to add_card.
  • create_stack(board_id, title, order): wraps POST /boards/{boardId}/stacks (title, order). It returns the new stack's id.

Both should probably be marked as dangerous tools (needing user confirmation), like add_card.

Nice to have, maybe as a follow-up:

  • create_board could take an optional list of stack titles (e.g. ["To Do", "In Progress", "Done"]) so a ready-to-use board takes one tool call.
  • update_stack(board_id, stack_id, title, order): wraps PUT /boards/{boardId}/stacks/{stackId} to rename or reorder a list.
  • delete_stack(board_id, stack_id): wraps DELETE /boards/{boardId}/stacks/{stackId}, with confirmation.
  • share_board(board_id, participant, type, permission_edit, permission_share, permission_manage): wraps POST /boards/{boardId}/acl (type: 0 user, 1 group, 7 circle). It should default to the least permissions (no share or manage). This matches the existing share_with_user / share_with_group / share_with_circle tools for files.

Describe alternatives you've considered

  • Creating the board and its lists by hand in the Deck UI and letting the agent add the cards. This works, and it's what I do now, but it breaks the flow and the agent has to stop and ask each time.

Additional context

Lingua principale
Python
Stelle
24
Fork
16
Merge medio
7g 15h
PR unite (30g)
4

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/context_agent

Tutte le issue di nextcloud/context_agent

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.