Jira 和 Asana 用戶反覆抱怨什麼？按討論串統計及他們表示轉往何處

Building against a named tool, or choosing where to position against it? Here is the count Friction holds for 54 B2B products, with every report linked to the comment it came from: for Jira and Asana, which complaint keeps coming back and where people say they went.

Jira: five of its 21 recurring themes (in order of reports; all dates; 154 Hacker News threads read; theme names as written on https://friction.grain64.com/p/jira/?utm_source=devto)

1. "Slow Jira page and board performance": 26 reports across 33 threads, from 2008 to 2026 (one report can rest on several threads). Typical: "have to wait minutes for the program to respond" (HN, 2025-07).
2. "Time-consuming Jira configuration": 8 reports in 8 threads. Typical: "the power to actually configure it to be sane is always reserved by a few people who don't want to bother" (HN, 2026-05).
3. "Jira feels too burdensome for simple tracking": 7 reports in 7 threads, 2013 to 2026.
4. "High Jira subscription costs": 7 reports in 7 threads. Typical, from a team that moved to Plane: "Jira wanting 26k per year, per customer we have was unacceptable" (HN, 2025-07).
5. "Complex Jira navigation and workflows": 6 reports in 7 threads. Typical: "historically i have been quite critical of Jira - because its always felt so complicated for me" (HN, 2024-09).

Asana: four of its 22 recurring themes (in order of reports; all dates; 92 threads; theme names as written on https://friction.grain64.com/p/asana/?utm_source=devto)

1. "Slow page loads and navigation": 10 reports in 9 threads, 2015 to 2020.
2. "High memory and CPU usage": 6 reports in 9 threads, 2013 to 2023.
3. "Flexible task and workflow structure": 6 reports in 6 threads, 2011 to 2024.
4. "High pricing for paid features": 4 reports in 4 threads. Typical: "columns and some sorting options behind a paywall" (HN, 2024-03).

Which tool should be counted next?

Name the product you build against, replace or compete with, in the comments here or at https://friction.grain64.com/request/?utm_source=devto. A product gets a page when public sources hold at least 10 sourced reports about it; otherwise the request is declined with the reason and the coverage numbers.

Where people say they went

26 Jira reports describe leaving and 16 Asana reports do (https://friction.grain64.com/alternatives/jira/?utm_source=devto, https://friction.grain64.com/alternatives/asana/?utm_source=devto).
Where a destination is named, Jira users name Linear most (5 reports), then GitHub Issues (2) and GitLab Issues (2), and five more tools with one report each, Plane among them; for Asana, Workflowy (2) and Clubhouse (2, from 2018) lead, with six more at one report each. A count is the number of reports naming a tool, not a market share.

Across the category (all dates, four tools; items, not recent reports; https://friction.grain64.com/state-of/project-and-issue-tracking/?utm_source=devto)

How to read these numbers

Sources: Hacker News (plus GitHub issues for open-source tools), so the counts are the developer-tooling view of each product. A count is reports, not users: a report counts once per product however many people agreed. Each product page states how many source threads it rests on (Jira 154, Asana 92), so you can judge the depth before you rely on it.

Check or dispute a report

Each report has a link to flag it, and https://friction.grain64.com/data/ says what is stored and how to ask for removal. Vendors can claim a page for free and reply on any report. Friction covers 54 products.

Written with AI assistance. Posted by Friction's publishing account (Grain64).