Accept team names and IDs, and state names, wherever the CLI takes them

CHANGELOG.md

@@ -4,6 +4,8 @@
 
 ### Added
 
+- every command that takes a team now accepts its key, name, or UUID, resolved through one shared lookup: `team states`, `team members`, `team delete`, `label list/create/delete --team`, `cycle list/view --team`, `project list/create/update --team`, `document list/create/update --team`, and `issue query/mine/create/update --team`. Keys stay canonical and win over a same-spelled name; an unknown team errors with the list of valid keys instead of an empty result or a raw API error. Previously only keys worked, which is why [#276](https://github.com/schpet/linear-cli/issues/276) asked for `team list --json` as a name-to-key lookup
+- `issue query --state` and `issue mine --state` accept a workflow state name or ID as well as the six state types, looked up within the queried team scope (all teams under `--all-teams`, where a name matches every team's same-named state). An unknown name errors and lists the scope's states, and types and names can be mixed
 - `project update --content <markdown>` and `--content-file <path>` replace a project's long-form overview body, matching the flags `project create` already had. Previously the only way to change the body after creation was a hand-written `projectUpdate` mutation through `linear api`
 - `--json` (`-j`) on `team list`, `cycle list`, `cycle view`, `milestone list`, `milestone view`, and `project view`, the last read commands without machine-readable output. List commands emit the same `{ nodes, pageInfo }` connection shape as the other list commands, after the same filtering and ordering as the table; view commands emit the GraphQL object as fetched, including every issue rather than the ten-item preview, and `milestone view --all --json` includes every page. (A 2.0.0 entry claimed `cycle list --json`; that change never actually landed.) ([#276](https://github.com/schpet/linear-cli/issues/276); thanks @lakardion)
 

README.md

@@ -137,6 +137,7 @@ linear issue list -w   # open issue list in web browser
 linear issue list -a   # open issue list in Linear.app
 linear issue query --search "login bug"  # search issues by text in your configured team
 linear issue query --search "oauth timeout" --team ENG --json  # structured search output for agents
+linear issue query --team "Engineering" --state "In Review" --json  # teams by key, name, or ID; states by type, name, or ID
 linear issue query --all-teams --json --limit 0  # export all issues as JSON
 linear issue start     # create/switch to issue branch and mark as started
 linear issue create    # create a new issue (interactive prompts)
@@ -205,7 +206,7 @@ linear project update <projectId> --content-file overview.md  # replace the proj
 ### cycle commands
 
 ```bash
-linear cycle list --team ENG          # list a team's cycles
+linear cycle list --team ENG          # list a team's cycles (--team takes a key, name, or ID)
 linear cycle list --team ENG --json   # as JSON
 linear cycle view 12 --team ENG       # view a cycle by number or name
 linear cycle view 12 --team ENG --json  # cycle details and its issues, as JSON

docs/usage.md

@@ -35,6 +35,10 @@ linear issue list --all-states
 
 # List multiple states
 linear issue list --state unstarted --state started
+
+# A state name or ID works too, and mixes with types
+linear issue list --state "In Review"
+linear issue list --state started --state "In Review"
 ```
 
 filter by assignee:
@@ -56,8 +60,9 @@ linear issue list --all-assignees
 other options:
 
 ```bash
-# List issues for specific team
+# List issues for specific team (key, name, or ID)
 linear issue list --team TEAM
+linear issue list --team "Team Name"
 
 # Sort by priority instead of manual order
 linear issue list --sort priority
@@ -138,7 +143,7 @@ linear issue create --estimate 3
 # Create with labels
 linear issue create --label bug --label frontend
 
-# Create for specific team
+# Create for specific team (key, name, or ID)
 linear issue create --team TEAM
 
 # Create and start working on it
@@ -210,6 +215,8 @@ linear issue delete TEAM-123
 
 ### teams
 
+wherever a command takes a team, pass its key, its name, or its UUID. keys are canonical; an unknown team errors and lists the valid keys.
+
 #### list teams
 
 ```bash
@@ -237,6 +244,7 @@ list members of a specific team:
 
 ```bash
 linear team members TEAM
+linear team members "Team Name"
 ```
 
 #### create a team

skills/linear-cli/references/cycle.md

@@ -37,9 +37,9 @@ Description:
 
 Options:
 
-  -h, --help           - Show this help.                      
-  --workspace  <slug>  - Target workspace (uses credentials)  
-  --team       <team>  - Team key (defaults to current team)  
+  -h, --help           - Show this help.                                   
+  --workspace  <slug>  - Target workspace (uses credentials)               
+  --team       <team>  - Team key, name, or ID (defaults to current team)  
   -j, --json           - Output as JSON
 ```
 
@@ -56,8 +56,8 @@ Description:
 
 Options:
 
-  -h, --help           - Show this help.                      
-  --workspace  <slug>  - Target workspace (uses credentials)  
-  --team       <team>  - Team key (defaults to current team)  
+  -h, --help           - Show this help.                                   
+  --workspace  <slug>  - Target workspace (uses credentials)               
+  --team       <team>  - Team key, name, or ID (defaults to current team)  
   -j, --json           - Output as JSON
 ```

skills/linear-cli/references/document.md

@@ -53,7 +53,7 @@ Options:
   --project           <project>     - Attach to project (UUID, slug ID, or name)                                        
   --issue             <issue>       - Attach to issue (identifier like TC-123)                                          
   --initiative        <initiative>  - Attach to initiative (UUID, slug ID, or name)                                     
-  --team              <team>        - Attach to team (key); with --cycle, scopes the cycle lookup instead               
+  --team              <team>        - Attach to team (key, name, or ID); with --cycle, scopes the cycle lookup instead  
   --cycle             <cycle>       - Attach to cycle: name, number, 'active'/'now', 'next', 'previous', or a relative  
                                       offset like +1 (team from --team or config)                                       
   --release           <release>     - Attach to release (UUID, name, or version)                                        
@@ -100,7 +100,7 @@ Options:
   --project     <project>     - Filter by project (UUID, slug ID, or name)                                                     
   --issue       <issue>       - Filter by issue (identifier like TC-123)                                                       
   --initiative  <initiative>  - Filter by initiative (UUID, slug ID, or name)                                                  
-  --team        <team>        - Filter by team (key); with --cycle, scopes the cycle lookup instead                            
+  --team        <team>        - Filter by team (key, name, or ID); with --cycle, scopes the cycle lookup instead               
   --cycle       <cycle>       - Filter by cycle: name, number, 'active'/'now', 'next', 'previous', or a relative               
                                 offset like +1 (team from --team or config)                                                    
   --release     <release>     - Filter by release (UUID, name, or version)                                                     
@@ -135,7 +135,8 @@ Options:
   --project           <project>     - Re-point to project (UUID, slug ID, or name); replaces the current attachment     
   --issue             <issue>       - Re-point to issue (identifier like TC-123); replaces the current attachment       
   --initiative        <initiative>  - Re-point to initiative (UUID, slug ID, or name); replaces the current attachment  
-  --team              <team>        - Re-point to team (key); with --cycle, scopes the cycle lookup instead             
+  --team              <team>        - Re-point to team (key, name, or ID); with --cycle, scopes the cycle lookup        
+                                      instead                                                                           
   --cycle             <cycle>       - Re-point to cycle: name, number, 'active'/'now', 'next', 'previous', or a         
                                       relative offset like +1 (team from --team or config)                              
   --release           <release>     - Re-point to release (UUID, name, or version); replaces the current attachment