nextcloud / nextcloud/call_summary_bot
Re-add Agenda items if they are unchecked
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 14
- Forks
- 3
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 6
Description
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: 31.0.7
Is your feature request related to a problem? Please describe.
At the moment whenever you a call start the agenda is generated. But after closing the call the agenda gets cleared and is empty. This makes it hard to use the agenda in rooms where calls with different usergroups could happen or if some taks are not covered.
Describe the solution you'd like
I would like that all unchecked agenda points automaiclally stay on the agenda until checked.
Describe alternatives you've considered
The alternative atm is to manually add all open points again after a call which is also a bit hard because you can't easly copy it from the call summary.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the agenda is generated when a call starts and cleared when it ends. Identify where agenda items and their checked state are stored, then verify that unchecked points remain available for later calls while completed points do not; add or update tests for this behavior if the project has coverage for agenda handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100