Open piiskop opened 4 years ago
Please fill in the complete issue template, especially the Deck version, server logs and browser console logs (press F12)
I updated the issue description with requested data. Filling in the complete template makes no sense as most of that information is irrelevant to the issue. If you need some certain data please tell me and I send it.
Thank you for filling in the requested information.
Filling in the complete template makes no sense as most of that information is irrelevant to the issue.
This might be your opinion and if you provide support for a software project, you can of course omit any templates for your issue. We have limited free time and resources to maintain, develop and support these kind of projects. Asking each and every detail is annoying, takes time and most often hides relevant information. Most apps have a rapid development cycle and "latest" as version is outdated before somebody picked up an issue - the reported bug might already be solved in the actual current version.
Since this is the repository of @juliushaertl i don't talk officially, but you make fixing bugs easier for everyone if you just fill in the complete issue template in the future. 🙂
Not much more to add :wink:
The console log also looks like you checked on the tab with github. Please check your browser console when performing the move operation in the tab with the deck app. Also the nextcloud log doesn't show any related entries. Is this all produced when trying to perform a move?
I changed both logs to be relevant to the issue. The logs shown have all appeared during I refreshed the page, clicked the menu of the card and clicked the move element in the menu.
Describe the bug Opening a jump menu on a card and clicking "Move card" does sometimes nothing. Expected behavior "Move card" has a functionality behind it that is triggered. **Deck version 1.1.2 Server log**
Browser console log