Bugs found in Wrike SaaS
Wrike is a flexible and user-friendly platform for managing projects, tasks, and teams. Its powerful dashboards, real-time editing, and robust collaboration pipelines make it a favored solution for productivity across different business sectors. The platform’s intuitive UI and clear structure minimize ramp-up time and increase transparency regarding project statuses, resources, and deadlines.
Our QAwerk team conducted a thorough Bug Crawl along Wrike’s key workflows, focusing on access management, analytics, and collaborative components. While Wrike delivered a generally smooth and intuitive experience, our analysis revealed several technical issues that, if resolved, would further enhance reliability and professionalism.
Below, we present the most impactful findings, accompanied by environment details, reproduction steps, and documentation.
Access Roles page throws Angular exception
Severity:
Critical
Precondition:
- User logged in.
- navigated to Account management → Access roles.
Steps to Reproduce:
- Log in to the workspace.
- Open browser console.
- Go to “Settings” and open “Access roles”.
- Observe console output.
Environment:
Chrome version 140
Actual Result:
Angular exception: NoSuchMethodError: method not found: ‘toString’ on null; errors in roles_page_template.dart, and related files.
Expected Result:
Access Roles page loads cleanly without frontend errors.
Dashboard shows 503 errors on loading data
Severity:
Critical
Precondition:
User logged in and navigated to the dashboard.
Steps to Reproduce:
- Log in.
- Access “My dashboard”.
- Monitor console during initial load.
Environment:
Chrome version 140
Actual Result:
Multiple POSTs to https://www.wrike.com/app/enhanced/ fail with HTTP 503 Service Unavailable.
Expected Result:
Dashboard loads completely; no 503 errors occur.
Error on report creation (Dart exceptions)
Severity:
Major
Precondition:
User is logged in and navigates to Reports.
Steps to Reproduce:
- Log in.
- Click “More” → “Reports”.
- Choose an Analytics Board or start “Create a Report”.
- Fill required fields (Name, Space, Data source).
- Open console, click “Create”.
Environment:
Chrome version 140
Actual Result:
Console logs Dart error: Uncaught Error at tools_tree_folder_tr_t_service.dart, stream_impl.dart, js_helper.dart.
Expected Result:
The report is created with no frontend/console errors.
WebSocket connection fails on Stream page
Severity:
Major
Precondition:
User logged in, navigated to Stream page.
Steps to Reproduce:
- Log in.
- Open the left sidebar, open the console.
- Go to More → Stream.
- Observe the console for WebSocket errors.
Environment:
Chrome version 140
Actual Result:
WebSocket connection to ‘wss://doceditor.wrike.com:22114/’ failed (html_dart2js.dart).
Expected Result:
Stream page loads with an active, error-free WebSocket connection.
Wrike remains a strong option for collaborative project management, but addressing these backend and frontend bugs is vital for enterprise reliability. Rectifying access role exceptions, report creation errors, dashboard HTTP issues, and stream WebSocket failures will future-proof Wrike for businesses scaling up workflows and demanding seamless operations.
