description:Successful response, returns a list of items
"401":
$ref:"#/components/responses/UnauthorizedError"
operationId:getTheAgendaItems
summary:List all items on the agenda
security:
-secretBearerAuth:[]
description:|
This returns all items currently on the agenda for a Fachschaftssitzung. A few of the standard items are auto-generated, the rest is directly sourced from the todo tool _Taiga_ ([fsco.li/todo](https://fsco.li/todo)).
@@ -66,6 +56,77 @@ paths:
However, we currently don't model multiple agendas (and maybe never will). To still keep the pattern, we therefore used an id of `-` to signify something like “_the one_ agenda, like, you know what we're talking about”. Should we ever introduce several agendas, distinguished
by ids, we could in a compatible way adjust the API to also allow actual ids in the path.
All agenda items (including the updated ones), just as if someone made a GET request.
"400":
$ref:"#/components/responses/BadRequestError"
"401":
$ref:"#/components/responses/UnauthorizedError"
operationId:patchTheAgendaItems
summary:Change items on the agenda
security:
-secretBearerAuth:[]
description:|
This changes the status of the specified items currently on the agenda for a Fachschaftssitzung sourced from Taiga.
Items without a `taiga` reference in the list are ignored. For items with a `taiga` reference, everything but the reference is ignored.
The `taiga.id` field is used to identify the user stories in Taiga, whose statuses are updated according to the `taiga.status` field.
Then, the agenda is re-retrieved from Taiga (just like with the `GET` path) and returned.
### Permission concept: Auditability
Any logged-in user can change the status of an item. When the status of an item is changed, a comment with the name of the user is posted
in the item. This should be most comfortable (anyone in the meeting will be able to change items, with no further administrative efforts required),
while still limiting abuse: If a notorious user were to persistently mis-use, they could either be technically blocked, or in some other
form socially reprimanded (e.g. by being sent a sternly worded message to stop).
### Is there a way to only change a single item (or a subset of it)?
Sure. Just only include them in the request body and the rest will be left untouched.
### Can I change any item with this?
Yes. The audit concept should make sure that if someone uses this to change the state of random other items, it is caught soon enough. Then, measures can still be implemented to taste.
/version:
summary:Path used to get details about the version of this application.
