After cloning a board, columns appear in a different order than in the source 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
After cloning a board, columns appear in a different order than in the source board.
To Reproduce
Steps to reproduce the behavior:
- Create a board ("Board 1")
- Add a few columns to it (i had six of them)
- Click three dots next to the board name and click "Clone board"
- Copy is created ("Board 1 Copy")
- Columns in the copy are in a different order
Expected behavior
Columns are in the same order as in the original board
Client details:
- OS: Linux
- Browser: Firefox
- Version 110.0
- Device: desktop
Server details
Operating system: Ubuntu 18.04
Web server: Apache
Database: PostgreSQL
PHP version:
Nextcloud version: 25.0.3
Where did you install Nextcloud from: Nextcloud AIO (Docker)
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
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, …)
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Logs
Nextcloud log (data/nextcloud.log)
Insert your Nextcloud log here
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
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
Reproduce the issue by creating a board with several columns, cloning it, and comparing the source and copy orders. Trace the board-cloning flow and the code that loads or renders columns, then add a regression test if the relevant test area is identified. Done means cloned boards preserve the source column order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100