backlogops 0.1__tar.gz → 0.2__tar.gz

{backlogops-0.1 → backlogops-0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops
-Version: 0.1
+Version: 0.2
 Summary: Library with backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -21,10 +21,10 @@ Classifier: Topic :: Office/Business :: Scheduling
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: config-as-json>=1.2
+Requires-Dist: config-as-json>=1.3
 Requires-Dist: tableio>=1.0
-Requires-Dist: tableio-cfg-json>=0.4
-Requires-Dist: versionreporter>=0.2
+Requires-Dist: tableio-cfg-json>=0.6
+Requires-Dist: versionreporter>=0.3
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -34,16 +34,17 @@ Dynamic: requires-python
 
 There are 3 related packages for backlog operations:
 
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
 
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
 
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 
 ## Available functionality
 
@@ -72,6 +73,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
 
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
+
 - Set planned release dates from the estimated release dates.
 
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -79,7 +83,23 @@ The following functionality is available in all 3 packages:
 
 - Validate the backlog and releases for consistency.
 
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+
+- Order the releases by their planned or estimated date.
+
+- Rename columns when reading a file and when writing a file.
+
+- Map custom status names in input files to backlog item statuses.
+
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+
+- Create stand-alone input or output preset configuration files.
+
+- 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.
 
 ## The operating model
 
@@ -97,45 +117,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
 
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
 
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
 
-- title: The title of the backlog item. Required.
+- `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. Required.
 
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
 
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
 
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
 
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
 
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
 
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
 
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
 
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
 
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 
 Additionally each backlog item can have any number of other fields.
 
@@ -202,7 +222,12 @@ from backlogops import (
   backlog and its releases from and to a table file.
 
 - `read_available_teams`, `write_available_teams`: read and write the
-  available-teams configuration.
+  available-teams workforce on its own.
+
+- `read_backlog_ops_config`, `write_backlog_ops_config`,
+  `get_backlog_ops_config`: read, write, and look up the top-level
+  `BacklogOpsConfig` (workforce, named input and output presets, and the
+  optional backlog item levels).
 
 - `read_key_list`, `write_key_list`: read and write a list of keys.
 
@@ -216,6 +241,9 @@ from backlogops import (
 - `move_keys_first`: reorder so that listed keys (and their children)
   come first.
 
+- `backlog_in_release_order`: reorder the backlog to follow the release
+  order, optionally honouring dependencies.
+
 - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
   and set planned dates from the estimate.
 
@@ -230,9 +258,9 @@ For the full set of public names see the API documentation linked above.
 
 ## Test summary
 
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops-0.1 → backlogops-0.2}/README_pypi.md

@@ -2,16 +2,17 @@
 
 There are 3 related packages for backlog operations:
 
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
 
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
 
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 
 ## Available functionality
 
@@ -40,6 +41,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
 
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
+
 - Set planned release dates from the estimated release dates.
 
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -47,7 +51,23 @@ The following functionality is available in all 3 packages:
 
 - Validate the backlog and releases for consistency.
 
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+
+- Order the releases by their planned or estimated date.
+
+- Rename columns when reading a file and when writing a file.
+
+- Map custom status names in input files to backlog item statuses.
+
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+
+- Create stand-alone input or output preset configuration files.
+
+- 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.
 
 ## The operating model
 
@@ -65,45 +85,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
 
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
 
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
 
-- title: The title of the backlog item. Required.
+- `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. Required.
 
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
 
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
 
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
 
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
 
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
 
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
 
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
 
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
 
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 
 Additionally each backlog item can have any number of other fields.
 
@@ -170,7 +190,12 @@ from backlogops import (
   backlog and its releases from and to a table file.
 
 - `read_available_teams`, `write_available_teams`: read and write the
-  available-teams configuration.
+  available-teams workforce on its own.
+
+- `read_backlog_ops_config`, `write_backlog_ops_config`,
+  `get_backlog_ops_config`: read, write, and look up the top-level
+  `BacklogOpsConfig` (workforce, named input and output presets, and the
+  optional backlog item levels).
 
 - `read_key_list`, `write_key_list`: read and write a list of keys.
 
@@ -184,6 +209,9 @@ from backlogops import (
 - `move_keys_first`: reorder so that listed keys (and their children)
   come first.
 
+- `backlog_in_release_order`: reorder the backlog to follow the release
+  order, optionally honouring dependencies.
+
 - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
   and set planned dates from the estimate.
 
@@ -198,9 +226,9 @@ For the full set of public names see the API documentation linked above.
 
 ## Test summary
 
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops-0.1 → backlogops-0.2}/backlogops.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops
-Version: 0.1
+Version: 0.2
 Summary: Library with backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -21,10 +21,10 @@ Classifier: Topic :: Office/Business :: Scheduling
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: config-as-json>=1.2
+Requires-Dist: config-as-json>=1.3
 Requires-Dist: tableio>=1.0
-Requires-Dist: tableio-cfg-json>=0.4
-Requires-Dist: versionreporter>=0.2
+Requires-Dist: tableio-cfg-json>=0.6
+Requires-Dist: versionreporter>=0.3
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -34,16 +34,17 @@ Dynamic: requires-python
 
 There are 3 related packages for backlog operations:
 
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
 
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
 
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 
 ## Available functionality
 
@@ -72,6 +73,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
 
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
+
 - Set planned release dates from the estimated release dates.
 
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -79,7 +83,23 @@ The following functionality is available in all 3 packages:
 
 - Validate the backlog and releases for consistency.
 
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+
+- Order the releases by their planned or estimated date.
+
+- Rename columns when reading a file and when writing a file.
+
+- Map custom status names in input files to backlog item statuses.
+
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+
+- Create stand-alone input or output preset configuration files.
+
+- 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.
 
 ## The operating model
 
@@ -97,45 +117,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
 
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
 
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
 
-- title: The title of the backlog item. Required.
+- `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. Required.
 
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
 
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
 
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
 
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
 
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
 
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
 
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
 
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
 
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 
 Additionally each backlog item can have any number of other fields.
 
@@ -202,7 +222,12 @@ from backlogops import (
   backlog and its releases from and to a table file.
 
 - `read_available_teams`, `write_available_teams`: read and write the
-  available-teams configuration.
+  available-teams workforce on its own.
+
+- `read_backlog_ops_config`, `write_backlog_ops_config`,
+  `get_backlog_ops_config`: read, write, and look up the top-level
+  `BacklogOpsConfig` (workforce, named input and output presets, and the
+  optional backlog item levels).
 
 - `read_key_list`, `write_key_list`: read and write a list of keys.
 
@@ -216,6 +241,9 @@ from backlogops import (
 - `move_keys_first`: reorder so that listed keys (and their children)
   come first.
 
+- `backlog_in_release_order`: reorder the backlog to follow the release
+  order, optionally honouring dependencies.
+
 - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
   and set planned dates from the estimate.
 
@@ -230,9 +258,9 @@ For the full set of public names see the API documentation linked above.
 
 ## Test summary
 
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops-0.1 → backlogops-0.2}/backlogops.egg-info/SOURCES.txt

@@ -11,17 +11,20 @@ src/backlogops/__init__.py
 src/backlogops/apply_format_rules.py
 src/backlogops/available_teams.py
 src/backlogops/available_teams_config.py
-src/backlogops/available_teams_wizard.py
 src/backlogops/backlog.py
 src/backlogops/backlog_helpers.py
+src/backlogops/backlog_in_release_order.py
+src/backlogops/backlog_ops_config.py
+src/backlogops/backlog_ops_wizard.py
 src/backlogops/backlog_releases.py
 src/backlogops/backlog_releases_io.py
-src/backlogops/console_yes_no_bridge.py
+src/backlogops/blo_version_reporter.py
 src/backlogops/date_ranges.py
 src/backlogops/demo_backlog.py
 src/backlogops/estimate_ready_date.py
 src/backlogops/format_rules.py
 src/backlogops/io_config.py
+src/backlogops/io_preset_wizard.py
 src/backlogops/key_list_io.py
 src/backlogops/levels.py
 src/backlogops/move_keys_first.py
@@ -35,4 +38,5 @@ src/backlogops/releases.py
 src/backlogops/table_create.py
 src/backlogops/table_rows.py
 src/backlogops/team.py
+src/backlogops/wizard_helpers.py
 src/backlogops/work_hours.py

backlogops-0.2/backlogops.egg-info/requires.txt

@@ -0,0 +1,4 @@
+config-as-json>=1.3
+tableio>=1.0
+tableio-cfg-json>=0.6
+versionreporter>=0.3

{backlogops-0.1 → backlogops-0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "backlogops"
-version = "0.1"
+version = "0.2"
 authors = [
   { name="Tom Björkholm", email="klausuler_linnet0q@icloud.com" },
 ]

{backlogops-0.1 → backlogops-0.2}/setup.py

@@ -5,7 +5,7 @@ from setuptools import setup
 
 setup(
   name='backlogops',
-  version='0.1',
+  version='0.2',
   description='Library with backlog operations.',
   author='Tom Björkholm',
   author_email='klausuler_linnet0q@icloud.com',
@@ -14,10 +14,9 @@ setup(
   package_dir={'backlogops': 'src/backlogops'},
   package_data={'backlogops': ['src/py.typed']},
   install_requires=[
-#    'argcomplete >= 3.6.3',
-    'config-as-json >= 1.2',
+    'config-as-json >= 1.3',
     'tableio >= 1.0',
-    'tableio-cfg-json >= 0.4',
-    'versionreporter >= 0.2'
+    'tableio-cfg-json >= 0.6',
+    'versionreporter >= 0.3'
   ]
 )