ClickUp Mobile

We have a lot of options in a dropdown Custom Field, and we are constantly scrolling through that list when selecting it on mobile. On the webapp, you can type in the first few letters and find the option you need quickly. We really need this function on mobile!

I could like it if I can use it on my mobile phone. Now I use Google Keep but whiteboards could add some value.

You can now add audio clips to task comments! 🎉 This request is for adding the functionality to other places in the mobile experience.

I would like to be able to take hand written notes on my tablet

It would be much better experience if the app could save the state whether i use list view or cards.. etc. So, that i return to the same view.

A feature that can add multiple accounts so you don't have to logout and then login to your other other/different email account

ClickUp’s automation engine is one of its most powerful features, allowing users to automate repetitive actions, trigger custom workflows, and maintain consistency across tasks. However, this functionality remains largely confined to the web and desktop applications. On mobile (iOS and Android), users can view tasks, add comments, and update statuses, but they cannot create, edit, delete, or even browse automations. This creates a significant gap in the user experience. Many teams today work on‑the‑go, relying solely on their mobile devices. When a critical automation needs to be adjusted—or a new one added—they are forced to switch to a desktop or browser. This friction disrupts workflows and reduces the value of ClickUp as a truly mobile‑first productivity tool. Proposed solution I propose that ClickUp introduces a full automation management interface in its mobile apps, enabling users to: · Add new automations – Create automation rules directly from the mobile app, with the same flexibility as the web version (triggers, conditions, actions). · Delete existing automations – Remove outdated or unnecessary rules without needing a desktop. · Find and browse automations – Provide a dedicated “Automations” section (e.g., within the Folder, List, or Space settings) where users can search, filter, and view all active rules. · Integrate automation setup into the mobile flow – Allow users to set up automations while they are in the context of a task, list, or folder, making the process intuitive. Why this matters Work from anywhere – Modern teams are not tied to desks. A manager reviewing a project on a train should be able to tweak an automation that moves tasks when priority changes. A freelancer using an iPad as their main device should have full control over their workspace automation. Consistency across platforms – ClickUp prides itself on feature parity, but automation remains a notable exception. Bringing it to mobile aligns with the product’s “everything in one place” promise. Real‑time responsiveness – When an automation fails or needs adjustment, waiting until the next desktop session can cause delays and errors. Mobile access allows instant fixes. Suggested implementation details · Navigation – Add “Automations” as a section inside the Space / Folder / List settings, consistent with the web layout. For quick access, it could also appear in the main navigation sidebar under “More” for power users. · Creation flow – Use a step‑by‑step wizard similar to the web, optimized for mobile screens. The interface should support the full range of triggers (status change, due date, custom field update, etc.) and actions (assign, change status, post comment, etc.). · Search & filter – For workspaces with dozens or hundreds of automations, include a search bar and filters (by folder, list, trigger type) to help users find specific rules. · Offline support – Automations themselves are server‑side, but the management interface should gracefully handle offline states, showing cached data when possible and queuing changes for sync. Integration with existing mobile features · Push notifications – When an automation fails or is triggered, mobile users already receive notifications. They could be given an option to “Edit automation” directly from that notification. · Context menus – When viewing a task, list, or folder, a long‑press or three‑dot menu could include a shortcut to “Automations in this list,” making discovery easier. Potential challenges & solutions · Screen real estate – Automation rules can be complex. Use collapsible cards, progressive disclosure, and clean typography to keep the interface manageable. · Performance – Loading many automations could be heavy; implement pagination and caching. · Consistency with web – Ensure that automations created on mobile follow the same validation rules and permissions (e.g., only admins can edit certain automations). Expected benefits · Increased productivity – Users can manage automations wherever they are, reducing context switching. · Higher adoption of automations – When mobile users can easily set up rules, they are more likely to explore and use automations. · Improved team agility – Teams can iterate on workflows during meetings, stand‑ups, or while on the go, without waiting to reach a computer. Conclusion Automations are a cornerstone of ClickUp’s value proposition. By extending full automation management to mobile, ClickUp would empower users to manage their workflows anytime, anywhere, and truly deliver on the promise of a unified productivity platform. I hope this request is considered for a future mobile update. Thank you.

Context We use ClickUp as an all-in-one app (documentation, task execution, and communication). ClickUp already has Relationships and References (mentions/backlinks), but information is still fragmented across Docs, tasks, and Chat. As the workspace grows, it becomes hard to understand “what is connected to what” around a topic, and where key decisions were discussed. Problem There is no unified, graph-style visualization of connections across Docs, tasks, and chat discussions. Topic-based discussions in Chat are hard to track over time; you cannot quickly see all threads related to a topic, who participated, and which tasks/docs resulted from the discussion. Decision context gets lost; tasks exist, but it is unclear which conversation led to the decision and why. Proposed solution Introduce a dedicated Graph View (Obsidian-style) that shows nodes and edges across: Docs and Doc pages Tasks and subtasks Chat: channels and especially chat threads (threads as first-class, linkable entities) The graph should reuse existing links and add a small set of missing primitives: A) Reuse existing link types Task Relationships: linked tasks, linked docs, dependencies References/backlinks: generated by @mentions across the workspace B) Add missing capabilities for “topic-based chat” Topic linking for chat threads: ability to link a chat thread to: a Topic entity (new concept), or a dedicated “Topic” tag/label system optionally also link the thread directly to a Doc/task (“this thread is about X”) Goal: make “chats by topic” navigable and durable, not just chronological messages. Core use cases Topic map: open a Topic (e.g., “Pricing”, “June campaign”, “Client onboarding”) and see: related Docs related tasks/subtasks all related chat threads where it was discussed Who discussed it: for every chat thread node, show: participants (avatars + count, ideally top contributors) time window (first/last activity) Decision traceability: go from a strategy Doc to the discussions that led to decisions, and to the execution tasks that implement them (and vice versa). Find orphan items: identify Docs/tasks/threads with no links. MVP requirements (minimum viable) A Graph View available at Workspace/Space/Folder/List scope, plus “neighborhood view” starting from a Doc/task/thread. Nodes: Doc, page, task, subtask, chat thread. Edges: existing relationships + references (@mentions) + “thread linked to topic”. Participant visibility on chat thread nodes. Filters: node type, edge type, task status, assignee, channel, time range. Permissions-aware: only show items the viewer has access to. Click to open: clicking a node opens the underlying Doc/task/thread. Nice-to-have (after MVP) Expand neighbors on demand (depth 1-3) for performance. Activity weighting/heatmap to highlight highly active discussion threads. “Create task from thread” automatically keeps the graph link. “Topic page” that acts as a hub (Doc/page with embedded graph widget and linked items). Acceptance criteria From a Topic, I can open Graph View and instantly see all related chat threads, docs, and tasks. I can filter to only chat threads and answer “who discussed this?” quickly. I can navigate Doc -> thread -> task and back without manual search. Why this matters ClickUp already has the underlying relationship data (Relationships + References). A unified graph that includes Chat would turn ClickUp into a true second-brain system where decisions, discussions, and execution are connected and easy to trace.