tcw-cli 2.6.0__tar.gz → 2.6.2__tar.gz

{tcw_cli-2.6.0 → tcw_cli-2.6.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tcw-cli
-Version: 2.6.0
+Version: 2.6.2
 Summary: Taxonomy · Capabilities · Work — a storage-abstracted framework for describing and evolving a software project.
 License:                                  Apache License
                                    Version 2.0, January 2004
@@ -727,7 +727,7 @@ to the transitions.
 
 | Lifecycle step                          | Without Jira                   | With Jira configured                                                                                                                           |
 | --------------------------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| an item is created                      | `tcw work inbox accept`, `new` | `tcw work tracker import <ticket>` claims the ticket (starts it and assigns it to you), then creates a backlog item whose intake is the ticket. With `inbox-query` set, `tcw work inbox accept <ticket>` does the same |
+| an item is created                      | `tcw work inbox accept`, `new` | `tcw work tracker import <ticket>` claims the ticket (starts it and assigns it to you), then creates a backlog item whose intake is the ticket and puts the ticket back where it was, still assigned to you. With `inbox-query` set, `tcw work inbox accept <ticket>` does the same |
 | `request`, `spec`, `plan` stages        | unchanged                      | unchanged                                                                                                                                      |
 | at any time                             | —                              | `tcw work tracker link` / `unlink` records or removes the link between an existing item and a ticket; Jira itself is not touched               |
 | an item has no ticket                   | —                              | `tcw work tracker create <slug>` makes one for it and binds it; `--all` sweeps every open item without one. Needs `work.tracker.create` and `statuses.backlog`. With `create.on-new`, filing an item makes its ticket |
@@ -797,9 +797,9 @@ e-mail address or token themselves.
 
 ```sh
 tcw work tracker list                  # TCW: lists tickets the query selects.   Jira: unchanged
-tcw work tracker import ENG-482         # TCW: creates a backlog item.            Jira: ENG-482 → In Progress, assigned to you
+tcw work tracker import ENG-482         # TCW: creates a backlog item.            Jira: ENG-482 stays in To Do, assigned to you
 #   …the request, spec and plan stages run as usual…
-tcw work start <slug>                   # TCW: backlog → active.                  Jira: confirms the claim import made
+tcw work start <slug>                   # TCW: backlog → active.                  Jira: ENG-482 → In Progress
 tcw work submit <slug>                  # TCW: active → review.                   Jira: ENG-482 → In Review
 tcw work complete <slug> --resolution done --confirm
                                         # TCW: review → completed.                Jira: ENG-482 → Done

{tcw_cli-2.6.0 → tcw_cli-2.6.2}/README.md

@@ -511,7 +511,7 @@ to the transitions.
 
 | Lifecycle step                          | Without Jira                   | With Jira configured                                                                                                                           |
 | --------------------------------------- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| an item is created                      | `tcw work inbox accept`, `new` | `tcw work tracker import <ticket>` claims the ticket (starts it and assigns it to you), then creates a backlog item whose intake is the ticket. With `inbox-query` set, `tcw work inbox accept <ticket>` does the same |
+| an item is created                      | `tcw work inbox accept`, `new` | `tcw work tracker import <ticket>` claims the ticket (starts it and assigns it to you), then creates a backlog item whose intake is the ticket and puts the ticket back where it was, still assigned to you. With `inbox-query` set, `tcw work inbox accept <ticket>` does the same |
 | `request`, `spec`, `plan` stages        | unchanged                      | unchanged                                                                                                                                      |
 | at any time                             | —                              | `tcw work tracker link` / `unlink` records or removes the link between an existing item and a ticket; Jira itself is not touched               |
 | an item has no ticket                   | —                              | `tcw work tracker create <slug>` makes one for it and binds it; `--all` sweeps every open item without one. Needs `work.tracker.create` and `statuses.backlog`. With `create.on-new`, filing an item makes its ticket |
@@ -581,9 +581,9 @@ e-mail address or token themselves.
 
 ```sh
 tcw work tracker list                  # TCW: lists tickets the query selects.   Jira: unchanged
-tcw work tracker import ENG-482         # TCW: creates a backlog item.            Jira: ENG-482 → In Progress, assigned to you
+tcw work tracker import ENG-482         # TCW: creates a backlog item.            Jira: ENG-482 stays in To Do, assigned to you
 #   …the request, spec and plan stages run as usual…
-tcw work start <slug>                   # TCW: backlog → active.                  Jira: confirms the claim import made
+tcw work start <slug>                   # TCW: backlog → active.                  Jira: ENG-482 → In Progress
 tcw work submit <slug>                  # TCW: active → review.                   Jira: ENG-482 → In Review
 tcw work complete <slug> --resolution done --confirm
                                         # TCW: review → completed.                Jira: ENG-482 → Done

{tcw_cli-2.6.0 → tcw_cli-2.6.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "tcw-cli"
-version = "2.6.0"
+version = "2.6.2"
 description = "Taxonomy · Capabilities · Work — a storage-abstracted framework for describing and evolving a software project."
 readme = "README.md"
 requires-python = ">=3.11"

tcw_cli-2.6.2/tcw/__init__.py

@@ -0,0 +1 @@
+__version__ = "2.6.2"