Order of Lists is changing when displaying a Board
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
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 open a Board the order of the Lists is changing. It is not every time, but has happened multiple times on a Board.
To Reproduce
Steps to reproduce the behavior:
- Go to the Deck Application
- Click on the Board in question
- Observe that the order of the lists has changed (see images)
- No Errors in Browser or Nextcloud Logs observed.
Expected behavior
I would expect that the order of the Lists on a Board would stay in the same order as they were created and that the only change in order would be done by creating/removing or manually shuffling them.
Screenshots
If applicable, add screenshots to help explain your problem.
Order as created:
Order after redisplaying:
Client details:
- OS: Ubuntu 24.04 LTS Desktop
- Browser Firefox
- Version 145.0.2 (64-bit) - Ubuntu Snap canonical-002 - 1.0
- Device: Desktop
Server details
Operating system: Ubuntu 24.04.3 LTS
Web server: Apache/2.4.58 (Ubuntu)
Database: PostgreSQL 16.11 (Ubuntu 16.11-0ubuntu0.24.04.1)
PHP version: PHP 8.3.6
Nextcloud version: Nextcloud Hub 25 Autumn (32.0.3)
Where did you install Nextcloud from: Latest .bz2 file from Nextcloud
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.
List of activated apps:
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Enabled:
- activity: 5.0.0-dev.0
- app_api: 32.0.0
- bruteforcesettings: 5.0.0-dev.0
- circles: 32.0.0
- cloud_federation_api: 1.16.0
- comments: 1.22.0
- contactsinteraction: 1.13.1
- dashboard: 7.12.0
- dav: 1.34.2
- deck: 1.16.2
- federatedfilesharing: 1.22.0
- federation: 1.22.0
- files: 2.4.0
- files_antivirus: 6.1.0
- files_downloadlimit: 5.0.0-dev.0
- files_pdfviewer: 5.0.0-dev.0
- files_reminders: 1.5.0
- files_sharing: 1.24.1
- files_trashbin: 1.22.0
- files_versions: 1.25.0
- firstrunwizard: 5.0.0-dev.0
- lookup_server_connector: 1.20.0
- nextcloud_announcements: 4.0.0-dev.0
- notes: 4.12.4
- notifications: 5.0.0-dev.0
- oauth2: 1.20.0
- password_policy: 4.0.0-dev.0
- photos: 5.0.0-dev.1
- privacy: 4.0.0-dev.0
- profile: 1.1.0
- provisioning_api: 1.22.0
- recommendations: 5.0.0-dev.0
- related_resources: 3.0.0-dev.0
- serverinfo: 4.0.0-dev.0
- settings: 1.15.1
- sharebymail: 1.22.0
- spreed: 22.0.7
- support: 4.0.0-dev.0
- survey_client: 4.0.0-dev.0
- systemtags: 1.22.0
- tasks: 0.17.1
- text: 6.0.1
- theming: 2.7.0
- twofactor_backupcodes: 1.21.0
- updatenotification: 1.22.0
- user_status: 1.12.0
- viewer: 5.0.0-dev.0
- weather_status: 1.12.0
- webhook_listeners: 1.3.0
- workflowengine: 2.14.0
Disabled: - admin_audit: 1.22.0
- encryption: 2.20.0
- files_external: 1.24.0
- logreader: 5.0.0-dev.0 (installed 5.0.0-dev.0)
- suspicious_login: 10.0.0-dev.0
- twofactor_nextcloud_notification: 6.0.0-dev.0
- twofactor_totp: 14.0.0
- user_ldap: 1.23.0
Nextcloud configuration:
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
{
"system": {
"instanceid": "REMOVED SENSITIVE VALUE",
"passwordsalt": "REMOVED SENSITIVE VALUE",
"secret": "REMOVED SENSITIVE VALUE",
"trusted_domains": [
"pyehub.pyenet.co.nz",
"pyehub"
],
"datadirectory": "REMOVED SENSITIVE VALUE",
"dbtype": "pgsql",
"version": "32.0.3.2",
"overwrite.cli.url": "https://pyehub.pyenet.co.nz/",
"dbname": "REMOVED SENSITIVE VALUE",
"dbhost": "REMOVED SENSITIVE VALUE",
"dbtableprefix": "oc_",
"dbuser": "REMOVED SENSITIVE VALUE",
"dbpassword": "REMOVED SENSITIVE VALUE",
"installed": true,
"htaccess.RewriteBase": "/",
"default_phone_region": "NZ",
"default_locale": "en_NZ",
"default_timezone": "Pacific/Auckland",
"maintenance": false,
"maintenance_window_start": 16,
"skeletondirectory": "",
"templatedirectory": "",
"lost_password_link": "enabled",
"remember_login_cookie_lifetime": 1296000,
"session_lifetime": 3600,
"session_keepalive": true,
"auto_logout": false,
"allow_user_to_change_display_name": true,
"auth.bruteforce.protection.enabled": true,
"auth.bruteforce.max-attempts": 5,
"auth.webauthn.enabled": false,
"mail_smtphost": "REMOVED SENSITIVE VALUE",
"mail_sendmailmode": "smtp",
"mail_domain": "REMOVED SENSITIVE VALUE",
"mail_smtpport": "25",
"mail_smtptimeout": 30,
"mail_from_address": "REMOVED SENSITIVE VALUE",
"updater.release.channel": "stable",
"updatechecker": true,
"has_internet_connection": true,
"check_for_working_wellknown_setup": true,
"check_for_working_htaccess": true,
"check_data_directory_permissions": true,
"log_type": "syslog",
"log_type_audit": "syslog",
"loglevel": 1,
"loglevel_frontend": 2,
"syslog_tag": "Nextcloud-PyeHub",
"logtimezone": "Pacific/Auckland",
"memcache.local": "\OC\Memcache\APCu",
"memcache.distributed": "\OC\Memcache\Redis",
"memcache.locking": "\OC\Memcache\Redis",
"redis": {
"host": "REMOVED SENSITIVE VALUE",
"port": 6379
}
}
}
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
No
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
No errors reported
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
No errors reported
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 reproducing the issue in the Deck application using the listed steps, then compare the list order when opening the same Board repeatedly. Trace the frontend behavior responsible for displaying Board lists and verify that the order remains unchanged except after creation, removal, or manual reordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100