There should be a LONG feature freeze until 5.0 to widdle down the 2,800 issues...

[Pentaphon]

Now that libtorrent 2.0 has been merged and there's no major Bittorrent protocol upgrades on the horizon, I think qBittorrent should go into bug-fixing mode aka no new features until 5.0 to start really taking care of the 2,800 issues that have piled up. I'm sure many of those issues are duplicates and can be cleaned up just by going through them but I'm sure a lot of them are significant bugs that need to be ironed out.

4.4.x has been the least performant release series so far, and I think extra attention should be spent on fixing bugs while libtorrent 2.x gets all their issues ironed out.

Instead of going from 4.4.x to 5.x, there should be a LONG feature freeze that lasts from 4.4.x to 4.5.x, then 4.6.x, then 4.7.x all the way to 4.9.x to really take care of the outstanding issues before moving onto 5.0 instead of making a big jump to 5.0 just for the sake of having a bigger version number.

[xavier2k6]

Nobody is labeling these issues and nobody is making sure it is difficult to create issues that are vague and lead nowhere.

Somebody needs to start cleaning up the old, useless issues.

I & other team members would have to disagree with you there to some degree.

See my comment from #17094 (reply in thread)

Out of the 2,795 Tickets - there are only 279 - Unlabeled

[Pentaphon]

Out of the 2,795 Tickets - there are only 279 - Unlabeled

That's 279 too many. That means there's nobody running a system to make sure those don't exist. The issue template should also help get new issues labeled, but nobody has set that up.

[xavier2k6]

Out of the 2,795 Tickets - there are only 279 - Unlabeled

That's 279 too many. That means there's nobody running a system to make sure those don't exist. The issue template should also help get new issues labeled, but nobody has set that up.

PR's are welcome.

[xavier2k6]

@thalieht May be helpful when searching for duplicates etc.

(I had something else planned for tracker status update but github isn't playing nice)

• All-in-One Definitive List - Open Issues

• All-in-One Definitive List - Open Feature Requests

[thalieht]

Aren't these the same as

• https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aopen+is%3Aissue+-label%3A%22Feature+request%22
• https://github.com/qbittorrent/qBittorrent/issues?q=is%3Aopen+is%3Aissue+label%3A%22Feature+request%22

[xavier2k6]

They are a downloadable text file with all the issues/feature requests in one place......rather than having to go through double/triple digit pages.

With the "links" only 25 items are viewable per page....

With the text files, the issues are all in one place/scrollable, same for feature requests.

[xavier2k6]

I was trying to make an expandable/collapsible list like below but GitHub keeps throwing a wobbler...unsure if it's a discussions limitation or not....

[DeathStalker77]

Quite a lot of open issues :-( Especially for recent versions. Wish I was a coder so I could help out, but I'm on the Design side of things.

-- DS

[xavier2k6]

Quite a lot of open issues :-(

We're getting them down..........slowly

Especially for recent versions.

Expected with multiple build choices available for differenct dependency versions.....Libtorrent v1/v2, Qt 5 & Qt 6.

---

Since this poll was opened on the 25th May 2022 there have been

• 927 Opened Tickets
• 818 Closed Tickets

Issue Tracker Status (19.Nov.2023)

2,770 - Open Tickets

• 1,354 - Open Issues
• 1,416 - Open Feature Requests

---

Open (Issues) Broken down by qBittorrent version

---

Below 4.0.0 = 16

Between 4.0.0 & 4.1.0 = 15

Between 4.1.0 & 4.2.0 = 122

Between 4.2.0 & 4.3.0 = 182

Between 4.3.0 & 4.4.0 = 284

Between 4.4.0 & 4.5.0 = 338

Between 4.5.0 & 4.6.0 = 338

qBittorrent 4.6.0+ = 59

---

Open (Feature Requests) Broken down by qBittorrent version

---

Below 4.0.0 = 375

Between 4.0.0 & 4.1.0 = 64

Between 4.1.0 & 4.2.0 = 191

Between 4.2.0 & 4.3.0 = 154

Between 4.3.0 & 4.4.0 = 191

Between 4.4.0 & 4.5.0 = 193

Between 4.5.0 & 4.6.0 = 224

qBittorrent 4.6.0+ = 24

---

Revisiting the 28 - "Can't reproduce" tickets could reduce further/maintain the reduction of 1,354 - Open Issues < 1,416 - Open Feature Requests

---

@luzpaz - Have a look if you have time.

[luzpaz]

@xavier2k6 this list is awesome. Can you regenerate this weekly by chance ?

[xavier2k6]

I hope to keep on top it weekly yes & if not bi-weekly.

Also, here's another handy list for Windows OS by build number......#12574 (comment), I'm hoping to integrate something like that in to the "issue template" when I get the chance.

[Pentaphon]

Wish I was a coder so I could help out, but I'm on the Design side of things.

Please consider contributing to a new default theme.

[DeathStalker77]

I could certainly provide some color schemes that are easier on the eyes than what I've found so far, but only in the form of color hexes, not creating the actual theme files. I could also provide UI/UX suggestions.

361, impo, is rather a lot of Issues to have currently open. I'm not certain why work is being done on issues with older versions, unless those issues also carry on to the current version. Feature Requests are a different thing. I would like to see those ranked by estimated effort and also by popularity, in order to prioritize them most effectively.

--- DS

[luzpaz]

Is there a way we can get more support for upstream libtorrent. There are a lot of pending upstream issues that will help us clear qbit bugtracker queue substantially?

[xavier2k6]

@luzpaz @thalieht I created a newer list in #20109

[xavier2k6]

Windows Server 2022 search string to be added:
Windows Server 2022

Some Windows 7/SP1/8/8.1/10/11 issues where no build version available will be tagged/added as 6.1.760x / 6.x.9xxxx / 10.0.1xxxx & 10.0.22xxx respectively.

Windows 11 - 10.0.22xxx

Windows 10 - 10.0.1xxxx

Windows 8/8.1 - 6.x.9xxxx

Windows 7/SP1 - 6.1.760x

[xavier2k6]

at 2,806 now......will need to spend more time on this.

[luzpaz]

Nice work lately on bugtracker cleanup, @xavier2k6! 🥇

[Pentaphon]

I agree but there need to be new ways to keep users from opening frivolous issues so that we stop getting so many issues that result in duplicates and issues that do not make any sense.

[xavier2k6]

Nice work lately on bugtracker cleanup, @xavier2k6! 🥇

@thalieht has to get that praise 🎉

I haven't closed off that many issues, just created some more easier search strings above......must do another update on the list probably at the wknd & then try & go through some more obsolete tickets.

there need to be new ways to keep users from opening frivolous issues so that we stop getting so many issues that result in duplicates and issues that do not make any sense.

Unfortunately, this will always happen as users will not always search through tickets for duplicates etc & some just never come back to provide further feedback....this can be evidenced by a users profile (one hit wonders as I call them) just joined github/1st issue on qbittorrent etc.

[xavier2k6]

some users come here just to have a rant & offer nothing constructive for example -> #20244 (One of the 1 hit wonders)

[Kenya-West]

Also my issue was left unanswered

[xavier2k6]

👻

I take the place of user accounts that have been deleted

(Issues)

• Regression since 4.5.0 on torrent tracker status #19674
• Matched RSS articles not downloading when Rule set to Download #18875
• Torrent list rows gets smaller when horizontal scroll and larger when going back #18871
• Crash on macOS "EXC_BAD_INSTRUCTION (SIGILL)" #18827
• RSS fetch cannot be switched off #18337
• Add Torrent Link not working if use proxy #14532
• Leftover fastresume files being loaded to session even without .torrent files #13547
• System network status changes doesn't update in Windows #13213
• Downloading torrent progress lost upon crash and files overwritten without recheck #13199
• Force recheck progress goes above 100% #13101
• Change how fastresumes are written to disk #13000
• Default category preference not saved for future torrents #12311
• Starting a very large torrent causes qBittorrent to hang #9424

[xavier2k6]

Some search strings with in:body filter
synology
freenas
unraid
flatpak
ubuntu
debian
docker
openwrt
opensuse
fedora
pclinuxos
popos
mint
endeavouros
centos
manjaro
gentoo
freebsd
NixOS
raspbian
slackware
arch linux
alpine
artix
raspberry

---

ios
safari
edge
firefox
chrome
android

[xavier2k6]

@Pentaphon I hope you don't mind me posting on your poll with what may seem like some random information but it serves a use to me & others to help with issues & also is informative of work being done by the team to reduce issue tickets etc.

[Pentaphon]

I hope you don't mind me posting on your poll with what may seem like some random information but it serves a use to me & others to help with issues & also is informative of work being done by the team to reduce issue tickets etc.

That's fine with me. The issues remain at 2,800 even after 2 years so there's a lot to do to get that down to a reasonable size. It doesn't look like we are doing bugfix releases until 5.0 but hopefully 5.x.x will take a long time to finally get those issues widdled down and a new system can be put in place to keep everything minimized and organized.