Upcoming cards section do contain unassigned cards without Due date in the web application.
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- 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.
Describe the bug When I go to my Deck to Upcoming Cards section in the nextcloud web, I see even unassigned cards without Due date. According to Upcomming Analyzer: https://upcoming-analyzer.niedermann.it I should not see them. And also I do not see them in the Android app. Only on web.
To Reproduce Steps to reproduce the behavior:
- Create a new board.
- Share the board with some other account in the nextcloud innstance.
- Create a list in the board.
- Create a card in the board, no due date, no assignment.
- Go to Upcoming cards Section, you see the Test card in the No due section.
Expected behavior You should not see unassigned cards without Due date in the Upcoming cards section.
Screenshots

Client details:
- OS: Ubuntu 22.04 LTS
- Vivaldi Browser
- browser version 5.6. - but irrelevant, same was on Chrome.
- Device: Desktop
Server details
Operating system: Ubuntu 22.04 LTS
Web server: nginx
Database: mysql
PHP version: 8.1
Nextcloud version: 25.0.2
Where did you install Nextcloud from: Nextcloud download page, and upgraded in app ever since. No containers, it is installed directly into an AWS ec2 instance.
Signing status:
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
No errors have been found.
Just realized after I clicked on the Send button. This change has not happened recently, it has happened 7 months+. I do not know the exact date, only that I`ve created set of Backlog documents after the change to get rid of all the cards that should not be visible there.
I just recently realized, that the android app is not showing me these, so I have investigated more and found it is likely a bug.