backlogops-cli 1.2__tar.gz → 1.3__tar.gz

{backlogops_cli-1.2 → backlogops_cli-1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-cli
-Version: 1.2
+Version: 1.3
 Summary: Command line interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -24,9 +24,9 @@ Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 Requires-Dist: argcomplete>=3.7.2
-Requires-Dist: backlogops>=1.2
-Requires-Dist: wizard-ui-bridge[textual]>=1.3
-Requires-Dist: edit-cfg-json-textual>=0.2.0
+Requires-Dist: backlogops>=1.3
+Requires-Dist: wizard-ui-bridge[textual]>=1.4
+Requires-Dist: edit-cfg-json-textual>=0.3.0
 Requires-Dist: versionreporter>=0.4
 Dynamic: author
 Dynamic: license-file
@@ -76,6 +76,10 @@ The following functionality is available in all 3 packages:
 - Estimate ready date for the backlog items based on available teams, team
   velocity, vacation dates, periods with half time work, etc.
 
+- Configure what a backlog item that nobody has estimated counts as, per backlog
+  item level, so that an unestimated item does not make the estimated dates too
+  optimistic.
+
 - Extract backlog keys at given backlog item levels.
 
 - Reorder the backlog so that the dependencies are satisfied.
@@ -110,7 +114,16 @@ The following functionality is available in all 3 packages:
 - Migrate an older configuration or preset file to the current file format.
 
 - A wizard to create a backlog-ops configuration file with the workforce, named
-  input and output presets, level names, and status name mapping.
+  input and output presets, level names, status name mapping, the guess for
+  unestimated items, how the graphical user interface shows the data, and the
+  Jira integration.
+
+- An editor showing a whole configuration file or a stand-alone preset file at
+  once, folded where it is deep, to change a single value without stepping
+  through the wizard.
+
+- Encrypt the Jira API token to a pass-phrase-protected file, so that no
+  configuration file holds the token in clear text.
 
 - Read a backlog and releases from Jira into a backlog and release table.
 
@@ -129,6 +142,10 @@ The following functionality is available in all 3 packages:
 - Move backlog items to a chosen anchor in the Jira rank order, following a key
   list.
 
+- Report what a Jira operation did not do. Every Jira result opens with what
+  Jira refused or what was skipped, so a value that was not written is visible
+  without reading the whole listing.
+
 ## The operating model
 
 The operating model that most of the functionality is designed for is that the
@@ -153,7 +170,10 @@ the library:
 
 - `title` The title of the backlog item. Required.
 
-- `story_points` The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Optional. An item with no
+  story points is one that nobody has estimated yet, and what such an item is
+  worked with when a completion date is estimated is configured. May be a
+  fraction, such as 0.5.
 
 - `status` The status of the backlog item. Required.
 
@@ -322,10 +342,10 @@ backlogops_cli serves 2 purposes:
 
 ## Test summary
 
-- Test result: 2309 passed, 1 deselected in 58s
+- Test result: 2555 passed, 1 deselected in 58s
 - No flake8 warnings.
 - No mypy errors found.
 - No pylint warnings.
 - No python layout warnings.
-- Built version(s): 1.2
+- Built version(s): 1.3
 - Build and test using Python 3.14.7

{backlogops_cli-1.2 → backlogops_cli-1.3}/README_pypi.md

@@ -41,6 +41,10 @@ The following functionality is available in all 3 packages:
 - Estimate ready date for the backlog items based on available teams, team
   velocity, vacation dates, periods with half time work, etc.
 
+- Configure what a backlog item that nobody has estimated counts as, per backlog
+  item level, so that an unestimated item does not make the estimated dates too
+  optimistic.
+
 - Extract backlog keys at given backlog item levels.
 
 - Reorder the backlog so that the dependencies are satisfied.
@@ -75,7 +79,16 @@ The following functionality is available in all 3 packages:
 - Migrate an older configuration or preset file to the current file format.
 
 - A wizard to create a backlog-ops configuration file with the workforce, named
-  input and output presets, level names, and status name mapping.
+  input and output presets, level names, status name mapping, the guess for
+  unestimated items, how the graphical user interface shows the data, and the
+  Jira integration.
+
+- An editor showing a whole configuration file or a stand-alone preset file at
+  once, folded where it is deep, to change a single value without stepping
+  through the wizard.
+
+- Encrypt the Jira API token to a pass-phrase-protected file, so that no
+  configuration file holds the token in clear text.
 
 - Read a backlog and releases from Jira into a backlog and release table.
 
@@ -94,6 +107,10 @@ The following functionality is available in all 3 packages:
 - Move backlog items to a chosen anchor in the Jira rank order, following a key
   list.
 
+- Report what a Jira operation did not do. Every Jira result opens with what
+  Jira refused or what was skipped, so a value that was not written is visible
+  without reading the whole listing.
+
 ## The operating model
 
 The operating model that most of the functionality is designed for is that the
@@ -118,7 +135,10 @@ the library:
 
 - `title` The title of the backlog item. Required.
 
-- `story_points` The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Optional. An item with no
+  story points is one that nobody has estimated yet, and what such an item is
+  worked with when a completion date is estimated is configured. May be a
+  fraction, such as 0.5.
 
 - `status` The status of the backlog item. Required.
 
@@ -287,10 +307,10 @@ backlogops_cli serves 2 purposes:
 
 ## Test summary
 
-- Test result: 2309 passed, 1 deselected in 58s
+- Test result: 2555 passed, 1 deselected in 58s
 - No flake8 warnings.
 - No mypy errors found.
 - No pylint warnings.
 - No python layout warnings.
-- Built version(s): 1.2
+- Built version(s): 1.3
 - Build and test using Python 3.14.7

{backlogops_cli-1.2 → backlogops_cli-1.3}/backlogops_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-cli
-Version: 1.2
+Version: 1.3
 Summary: Command line interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -24,9 +24,9 @@ Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 Requires-Dist: argcomplete>=3.7.2
-Requires-Dist: backlogops>=1.2
-Requires-Dist: wizard-ui-bridge[textual]>=1.3
-Requires-Dist: edit-cfg-json-textual>=0.2.0
+Requires-Dist: backlogops>=1.3
+Requires-Dist: wizard-ui-bridge[textual]>=1.4
+Requires-Dist: edit-cfg-json-textual>=0.3.0
 Requires-Dist: versionreporter>=0.4
 Dynamic: author
 Dynamic: license-file
@@ -76,6 +76,10 @@ The following functionality is available in all 3 packages:
 - Estimate ready date for the backlog items based on available teams, team
   velocity, vacation dates, periods with half time work, etc.
 
+- Configure what a backlog item that nobody has estimated counts as, per backlog
+  item level, so that an unestimated item does not make the estimated dates too
+  optimistic.
+
 - Extract backlog keys at given backlog item levels.
 
 - Reorder the backlog so that the dependencies are satisfied.
@@ -110,7 +114,16 @@ The following functionality is available in all 3 packages:
 - Migrate an older configuration or preset file to the current file format.
 
 - A wizard to create a backlog-ops configuration file with the workforce, named
-  input and output presets, level names, and status name mapping.
+  input and output presets, level names, status name mapping, the guess for
+  unestimated items, how the graphical user interface shows the data, and the
+  Jira integration.
+
+- An editor showing a whole configuration file or a stand-alone preset file at
+  once, folded where it is deep, to change a single value without stepping
+  through the wizard.
+
+- Encrypt the Jira API token to a pass-phrase-protected file, so that no
+  configuration file holds the token in clear text.
 
 - Read a backlog and releases from Jira into a backlog and release table.
 
@@ -129,6 +142,10 @@ The following functionality is available in all 3 packages:
 - Move backlog items to a chosen anchor in the Jira rank order, following a key
   list.
 
+- Report what a Jira operation did not do. Every Jira result opens with what
+  Jira refused or what was skipped, so a value that was not written is visible
+  without reading the whole listing.
+
 ## The operating model
 
 The operating model that most of the functionality is designed for is that the
@@ -153,7 +170,10 @@ the library:
 
 - `title` The title of the backlog item. Required.
 
-- `story_points` The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Optional. An item with no
+  story points is one that nobody has estimated yet, and what such an item is
+  worked with when a completion date is estimated is configured. May be a
+  fraction, such as 0.5.
 
 - `status` The status of the backlog item. Required.
 
@@ -322,10 +342,10 @@ backlogops_cli serves 2 purposes:
 
 ## Test summary
 
-- Test result: 2309 passed, 1 deselected in 58s
+- Test result: 2555 passed, 1 deselected in 58s
 - No flake8 warnings.
 - No mypy errors found.
 - No pylint warnings.
 - No python layout warnings.
-- Built version(s): 1.2
+- Built version(s): 1.3
 - Build and test using Python 3.14.7

backlogops_cli-1.3/backlogops_cli.egg-info/requires.txt

@@ -0,0 +1,5 @@
+argcomplete>=3.7.2
+backlogops>=1.3
+wizard-ui-bridge[textual]>=1.4
+edit-cfg-json-textual>=0.3.0
+versionreporter>=0.4

{backlogops_cli-1.2 → backlogops_cli-1.3}/setup.py

@@ -5,7 +5,7 @@ from setuptools import setup
 
 setup(
   name='backlogops-cli',
-  version='1.2',
+  version='1.3',
   description='Command line interface for backlog operations.',
   author='Tom Björkholm',
   author_email='klausuler_linnet0q@icloud.com',
@@ -15,9 +15,9 @@ setup(
   package_data={'backlogops_cli': ['src/py.typed']},
   install_requires=[
     'argcomplete >= 3.7.2',
-    'backlogops >= 1.2',
-    'wizard-ui-bridge[textual] >= 1.3',
-    'edit-cfg-json-textual >= 0.2.0',
+    'backlogops >= 1.3',
+    'wizard-ui-bridge[textual] >= 1.4',
+    'edit-cfg-json-textual >= 0.3.0',
     'versionreporter >= 0.4'
   ]
 )

{backlogops_cli-1.2 → backlogops_cli-1.3}/src/backlogops_cli/_command_io.py

@@ -145,12 +145,14 @@ def add_config_arg(parser: argparse.ArgumentParser) -> None:
     """Add the ``-c``/``--config`` backlog-ops configuration argument.
 
     The configuration file holds the workforce, the named input and output
-    presets, the levels and the global status map. Without ``-c`` the file
-    is discovered the same way as the GUI.
+    presets, the levels, the global status map, the guess for unestimated
+    items, the GUI display settings and the Jira configuration. Without
+    ``-c`` the file is discovered the same way as the GUI.
     """
     parser.add_argument('-c', '--config', dest='config',
                         help='Backlog-ops configuration file (workforce, '
-                        'named presets, levels, status map). Without -c the '
+                        'named presets, levels, status map, default story '
+                        'points, Jira configuration). Without -c the '
                         'file is found from $BACKLOGOPS_CFG, else '
                         'backlogops.cfg in $BACKLOGOPS_DIR, else '
                         '$HOME/.backlogops.cfg.')

{backlogops_cli-1.2 → backlogops_cli-1.3}/src/backlogops_cli/add_to_jira.py

@@ -70,6 +70,7 @@ def _add(parsed: argparse.Namespace, config: BacklogOpsConfig,
     print(f'Added {len(result.stored)} items to Jira; '
           f'{len(result.already_present)} already present; '
           f'{len(result.failed)} failed; '
+          f'{len(result.failed_fields)} fields not set; '
           f'{len(result.failed_links)} links not written.', file=sys.stderr)
     return result
 

{backlogops_cli-1.2 → backlogops_cli-1.3}/src/backlogops_cli/encrypt_token_file.py

@@ -4,7 +4,7 @@
 Read a clear text API token from a file or from standard input, encrypt it
 with a pass phrase and write the encrypted token to a file. The pass phrase
 is requested on the terminal and is not echoed. The clear text token file
-is not modified, unless the the encrypted token file is the same as the
+is not modified, unless the encrypted token file is the same as the
 clear text token file, in which case the clear text token file is overwritten
 with the encrypted token. The encrypted token file is written atomically,
 so that it is either the old version or the new version, and never a

{backlogops_cli-1.2 → backlogops_cli-1.3}/src/backlogops_cli/estimate_ready_date.py

@@ -6,7 +6,8 @@ estimates the ready date of each backlog item from the available teams,
 as documented for :func:`backlogops.estimate_ready_date`. The teams
 configuration (velocity, work hours, vacations and so on) is taken from
 the file given by ``--config`` or, when that is absent, from the
-configured backlog-ops file. The backlog with the estimated dates and the
+configured backlog-ops file, and so is what a backlog item that nobody
+has estimated is worked with. The backlog with the estimated dates and the
 releases are written to the output file. The input and output formats are
 inferred from the file name extensions, but can be overridden by a
 configuration file or by a named preset.
@@ -58,8 +59,9 @@ def _estimate(parsed: argparse.Namespace, config: Optional[BacklogOpsConfig],
     None here; the assertion makes that explicit for the type checker.
     """
     assert isinstance(config, BacklogOpsConfig)
-    changes = data.estimate_ready_date(config.available_teams,
-                                       _start_date(parsed))
+    changes = data.estimate_ready_date(
+        config.available_teams, _start_date(parsed),
+        default_story_points=config.default_story_points)
     if parsed.set_plan:
         data.set_plan_from_estimate()
     return date_report(changes, overwrite_callback(parsed.force))

{backlogops_cli-1.2 → backlogops_cli-1.3}/src/backlogops_cli/update_backlog_in_jira.py

@@ -20,8 +20,9 @@ selected fields are updated the same way under either value. With ``--rank``
 the items are also ranked in Jira to match the backlog order, at the chosen
 anchor.
 
-The updated, already-correct, ignored, added and failed items are printed
-to stdout as labelled lists, unless ``-q``/``--quiet`` is given. An
+The updated, already-correct, ignored and added items, and what Jira
+refused to add, to set or to link, are printed to stdout as labelled
+lists, unless ``-q``/``--quiet`` is given. An
 encrypted Jira token is unlocked by a pass phrase asked on the terminal
 only when it is needed.
 """
@@ -128,7 +129,11 @@ def _report_summary(result: UpdatedBacklogInJira) -> None:
     print(f'Updated {len(result.updated)} items in Jira; '
           f'{len(result.already_correct)} already correct; '
           f'{len(result.ignored)} ignored; {len(result.added.stored)} added; '
-          f'{len(result.failed)} failed.', file=sys.stderr)
+          f'{len(result.added.failed)} not added; '
+          f'{len(result.failed_fields) + len(result.added.failed_fields)} '
+          'fields not set; '
+          f'{len(result.failed_links) + len(result.added.failed_links)} '
+          'links not written.', file=sys.stderr)
 
 
 def _run(parsed: argparse.Namespace) -> int:

backlogops_cli-1.2/backlogops_cli.egg-info/requires.txt

@@ -1,5 +0,0 @@
-argcomplete>=3.7.2
-backlogops>=1.2
-wizard-ui-bridge[textual]>=1.3
-edit-cfg-json-textual>=0.2.0
-versionreporter>=0.4