search

Lissy93 / dashy

🚀 A self-hostable personal dashboard built for you. Includes status-checking, widgets, themes, icon packs, a UI editor and tons more!
https://dashy.to
MIT License
18.17k stars 1.37k forks source link

Bot Improvements and reorganizing Tickets #1419

Closed CrazyWolf13 closed 9 months ago

CrazyWolf13 commented 11 months ago

Hello @Lissy93 Please stop your @liss-bot from closing Tickets automatically due to inactivity. In my eyes this really stops the ticket system from working correctly. If no even contraversial.-

I see huge amouts of still relevant Tickets that were just closed due to inactivity, even tough the user has written like 3 times it's still relevant.

This is also really annoying if a user wants to search about an issue, can't find an existing, creates a new and then someone has to manually search through all tickets just to see exactly the same but closed by your bot because of inactivity.

I totally see the reason behind this and think that this bot really is of a nice core idea, but in the current state of this project being full of bugs, bugs being reported day by day but barely any fixes nor updates in a huge time.

I hope you can rethink about this process and really start investing some time into dashy or searching a new owner, because it's just really sad to see this very well done project with insanely great documentation and your eye to the details just slowly dying due to inactivity.

Just have a look at how many stars you got, there are like 1.5k People waiting for updates and bug fixes and hoping you can return to development into dashy. But in the current state more and more people will turn down.

CrazyWolf13 commented 11 months ago

More or less important Issues which should be considered to be reopened, which were closed due to inactivity but most likely still relevant: Already filtered out a huge list of potential not relevant anymore, feature request or just really stale issues. Edit: Took me a whole day, hope it's helpful for any contributor or @Lissy93

894 (Safari Support)

647 (Unraid Problems)

638 (Testing Needed, Referenced Issue by Lissy93 still open)

637 (yarn start or yarn build)

842 (Description text overlapping)

836 (dashy very slow on many urls sql backend)

799 (A lot to do here still....)

835 (Multiple context menus)

831 (config not saving correctly)

825 (time based theme switch)

903 (hideDetails on weather widget)

890 (guest access on keycloak)

877 (docker rebuild on every startup)

857 (base_url inconsitently used)

937 (certain icons unavailable)

913 (subpages search field broken)

1004 (description overflow and possible fix)

997 (Transport Widget - Elizabeth Line)

959 (Material Design Icons broken unicode icons)

1063 (Auth)

1059 (hl-Icons broken)

1035 (openweather icon)

1012 (themes on docker not working properly)

1055 (Font-Awesome api key)

1042 (Weird Icons and fix to this included)

1077 (Font-Awesome Problems)

1142 (Weather-API Problems)

1137 (search in non alphanumerical characters)

1116 (weather forecast broken)

1108 (hotkeys broken)

1202 (SVG Logo for Homelab-Icons Repo requested)

1191 (starting View problems)

1176 (on Login don't Redirect)

1172 (APOD widget broken)

1164 (Wakxcode Icons Announcement)

1242 (Custom CSS)

1255 (Safari Support)

1239 (Clock Widget other Font)

1238 (date.gethour) low priority

1296 (Custom CSS)

Priority; ios support (#894 ) Authentification overhaul Drag'n Drop Feature, better support for rearranging sections and items through config

I see those as such of the most problematic things and most asked next to yml problems and yarn build and or yarn start

Lissy93 commented 11 months ago

@CrazyWolf13 - my hero! Thanks for all that :)

This weekend I've gone through these, and below is the update for each of the above tickets.

Also, I've updated the time it takes for a ticket to be marked as stale from 30 days, to 360 days (1 year)

✅ Fixed this weekend (in #1425):

📋 Todo, I've re-opened these issues:

📋🤔 Todo, I've re-opened, but am not sure of the solutions

❌ Closing / Keeping Closed:

🚏 Awaiting user response:

Lissy93 commented 11 months ago

On a side note, @CrazyWolf13 I really appreciate the time you took to go through those tickets. I often feel like I'm drowning in issues, PRs, questions and other notifications, but your ticket provided a nice list to work through.

Thank you! 💕

I've given you write-access to the planning board to prioritize upcoming fixed and features.

At the moment I'm (starting to) work on V3, which changes the way the config is read, removing the need for users to re-build the app for changes to take effect. In the meantime, I'm going to get a few more of those bug fixes done, and publish a new release.

Lissy93 commented 11 months ago

On another side note, there are still a lot of tickets to get through. If there are any full-stack devs out there, with Vue + Node + Docker experience, who would like to help with this project, that would be really awesome.

CrazyWolf13 commented 11 months ago

Hi Lissy

First off all Happy New Year 🎉

Thank you for looking into these Issues and already fixing a lot of them! Great that you could change the delay of your bot, once the project becomes more active again this can surely be turned back down.

No problem, felt like it was needed and this feels like a project that definitely deserves this.

If you ever feel like this again or have anything where I can support you please hit me on I'd love to support dashy as much as possible.

Thank you for the access that is amazing, will take some time today to look through the planning board and analyze it.

Thanks ❤️

CrazyWolf13 commented 9 months ago

Hi @Lissy93

After jumping through some new issues, I noticed quite a lot of duplicates. While having some time (Which turned into like 7h😂) free today I worked through all open issues to search duplicates and find issues that have already been fixed or are stale and external problems.

Hope you can give them a quick read and decide if they can really be closed, as proposed.

With this up to 36 issues could be closed, which would greatly clean up the issues section.

Thanks ❤️

Questions which already have an answer:

1448

1449

1451

Not Dashy related issues:

1437

Others, Feedback

1412

1399

Duplicates:

1378

1398

1311

1388

990

1381

1357

1161 -> Basically the same, here a directory outside of root directory is requested.

1035

367

1281

1336

1429

1251

A PR has been pushed to fix this issue:

1372

1255

1174

1142

1116

1035

1042

774 -> Can't reproduce and commits were pushed

747

Is most likely already resolved, but stale:

1333

1329

1319

1268

1086

770 -> Works fine with iframe, even with auth via pwd and username

Stale and can't reproduce

1323

489

Already planned:

1457

Lissy93 commented 9 months ago

Thanks so much @CrazyWolf13 💖

I've gone through each of these, and either closed or triaged each ticket

Questions which already have an answer:

1448

1449

1451

Closed 👍

Not Dashy related issues:

1437

Closed 👍

Others, Feedback

1412 (I may remove the bot comment about staring the repo)

1399

Closed, except for #1251, #1035, #990

Duplicates:

1378

1398

1311

1388

990 (kept open, and closed other duplicates)

1381

1357

1161 -> Basically the same, here a directory outside of root directory is requested.

1035 (kept open, as duplicates have been closed)

367

1281

1336

1429

1251 (kept open, and closed the other dup)

A PR has been pushed to fix this issue:

1372

1255

1174

1142

1116

1035

1042

774 -> Can't reproduce and commits were pushed

747

Closed 👍

Is most likely already resolved, but stale:

1333

1329

1319

1268 (submitted PR to update docs)

1086

770 -> Works fine with iframe, even with auth via pwd and username

Closed 👍

Stale and can't reproduce

1323

489 - (I think I should depreciate the use of GitHub Wiki, and instead write a script to automate keeping the website up-to-date with the docs)

Closed 👍

Already planned:

1457

CrazyWolf13 commented 9 months ago

Thank you! Happy to help 😊