Skip to content

(RFC) feat: make the default project optional - #1007

Draft
karaolidis wants to merge 1 commit into
ankitpokhrel:mainfrom
karaolidis:feat/multi-project-improvements
Draft

(RFC) feat: make the default project optional#1007
karaolidis wants to merge 1 commit into
ankitpokhrel:mainfrom
karaolidis:feat/multi-project-improvements

Conversation

@karaolidis

Copy link
Copy Markdown

POC for making the default project optional (#942, #611, #760, probably others).

Not asking to merge immediately, just want to know if this direction is acceptable before cleaning up.

Today project is required and the answer is raw JQL (#420). This PR makes the following changes:

  • init --no-project / --no-board, and init now asks instead of forcing it (backwards incompatible)
  • no default project -> issue list/epic list span all projects
  • create/clone/epic commands still require a project (prompt for -p)
  • issue create -p OTHER resolves issue types live, so any project works per-command

Builds on the existing hasProjectFilter/Raw() code from #395 (rewrote the regex
as a tokenizer so project inside quotes isn't matched).

init can now be run with --no-project/--no-board. Without a default project,
list commands span all projects; create/clone/epic commands still require -p.
Passing -p to `issue create` resolves issue types from the API instead of the
cached config.

Signed-off-by: Nikolaos Karaolidis <nick@karaolidis.com>
@karaolidis karaolidis changed the title feat: make the default project optional (RFC) feat: make the default project optional Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant