3 ms·
I don't agree with your assessment, but I want to encourage you to raise bug tickets on YouTrack (their answer to Jira). In the last 10 years, I have had more
by throwaway2037 2y ago
I don't agree with your assessment, but I want to encourage you to raise bug tickets on YouTrack (their answer to Jira). In the last 10 years, I have had more than 100 (no joke!) of my bug tickets fixed by JetBrains. If you write a good description with a min-repro, they will fix it.
> I wish it was a more stable product
Can you give a specific example of a bug that you encountered?
- kubav027 2y agoI have tried that and all issues were already reported. It still took them a few months to resolve it. See examples of last year serious bugs: https://youtrack.jetbrains.com/issue/PY-72046 https://youtrack.jetbrains.com/issue/PY-72046 https://youtrack.jetbrains.com/issue/PY-79448 https://youtrack.jetbrains.com/issue/PY-79448 https://youtrack.jetbrains.com/issue/PY-78077 https://youtrack.jetbrains.com/issue/PY-78077 I can't get how poetry support problems were introduced. They have made new patch release just before Christmas holidays which introduced major problem (IDE periodically updates package lock file). It took them 3 months to fix it. After a few weeks they reintroduced the bug and said that it is feature and added registry option to revert to old functionality. I still do not understand what is the reason for updating package lock file.
- atombender 1y agoNot the parent, but I have to agree with them. I'm a steadfast IntelliJ user, but every release seems to break something different. I almost always file a report, many of which remain unresolved. In several cases I've reported bugs that are promptly marked as a duplicate of a years-old bug. For example: * The Go plugin appears to make the IDE is very slow (>10 seconds) at detecting files changed outside the app. https://youtrack.jetbrains.com/issue/GO-18510/IDE-is-very-slow-at-detecting-file-changes https://youtrack.jetbrains.com/issue/GO-18510/IDE-is-very-sl... (1 month old now) * The file modification icon gets stuck (saving doesn't clear it), possibly because of some Git state tracking. https://youtrack.jetbrains.com/issue/GO-18094/File-modification-icon-shown-even-after-saving https://youtrack.jetbrains.com/issue/GO-18094/File-modificat... (3 years) * The "next/previous error" navigation shows the line error but then immediately hides it again. https://youtrack.jetbrains.com/issue/IJPL-156089/Next-Highlighted-Error-tooltip-disappears-immediately-during-scrolling https://youtrack.jetbrains.com/issue/IJPL-156089/Next-Highli... (11 months old) All three relate to what I would call core functionality, rather some rare, niche language feature. They all disproportionately affect my daily use. How can a serious company let bugs like these hang around, not for one week, or two weeks, or a month, but three years? My guess from the amount of churn in YouTrack is they're churning out too many features creating more bugs at a higher rate than they can fix them, and are simply overwhelmed, and their triage process must be deprioritizing a lot of basic stuff. My most recent bug: After upgrading to 2025.1, the IDE freezes completely 1-2 times a day, requiring a force quit. I reported the bug 10 days ago, collecting all the output they ask for in such cases, and all I've gotten are crickets. https://youtrack.jetbrains.com/issue/IDEA-371932/IDE-freezes-and-must-be-force-quit https://youtrack.jetbrains.com/issue/IDEA-371932/IDE-freezes...