You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I searched existing issues and did not find a duplicate.
I am describing a concrete problem or use case.
Area
apps/mobile new-task flow.
Problem or use case
Opening New Task always begins at the project picker even when one project was used moments ago. Repeatedly creating tasks in the same project requires selecting that project each time.
Proposed solution
When New Task opens and there is a valid recently active project, start on that project composer. Keep the existing back action so the user can return to the project picker, and fall back to the picker when no recent project is available.
Why this matters
It removes a repetitive navigation step from the common case while preserving explicit project selection.
Smallest useful scope
Use the existing recent-project ordering already available to the mobile client. Do not persist a new preference or change project sorting. Apply the default only when starting a fresh new-task flow.
Alternatives considered
Persisting a separate default-project preference adds settings and state. Always showing the picker is predictable but slower for repeated work.
Risks or tradeoffs
Automatic navigation can surprise users who expect the picker. The selected project must still exist in the active environment, and back navigation must remain obvious and reliable.
This discussion was converted from issue #5785 on August 15, 2026 09:50.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/mobilenew-task flow.Problem or use case
Opening New Task always begins at the project picker even when one project was used moments ago. Repeatedly creating tasks in the same project requires selecting that project each time.
Proposed solution
When New Task opens and there is a valid recently active project, start on that project composer. Keep the existing back action so the user can return to the project picker, and fall back to the picker when no recent project is available.
Why this matters
It removes a repetitive navigation step from the common case while preserving explicit project selection.
Smallest useful scope
Use the existing recent-project ordering already available to the mobile client. Do not persist a new preference or change project sorting. Apply the default only when starting a fresh new-task flow.
Alternatives considered
Persisting a separate default-project preference adds settings and state. Always showing the picker is predictable but slower for repeated work.
Risks or tradeoffs
Automatic navigation can surprise users who expect the picker. The selected project must still exist in the active environment, and back navigation must remain obvious and reliable.
Contribution
All reactions