backlogops 1.2__tar.gz → 1.3__tar.gz

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops
-Version: 1.2
+Version: 1.3
 Summary: Library with backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -26,9 +26,9 @@ Requires-Dist: cryptography>=50.0.1
 Requires-Dist: jira[cli,opt]>=3.10.5
 Requires-Dist: tableio>=1.1
 Requires-Dist: tableio-cfg-json>=1.4
-Requires-Dist: wizard-ui-bridge[textual]>=1.3
+Requires-Dist: wizard-ui-bridge[textual]>=1.4
 Requires-Dist: versionreporter>=0.4
-Requires-Dist: edit-cfg-json>=0.2.0
+Requires-Dist: edit-cfg-json>=0.3.0
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -77,6 +77,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.
@@ -111,7 +115,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.
 
@@ -130,6 +143,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
@@ -154,7 +171,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.
 
@@ -262,8 +282,10 @@ from backlogops import (
 
 - `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).
+  `BacklogOpsConfig` (workforce, named input and output presets, the
+  status-name map, the guess for unestimated items, the GUI display
+  settings, the Jira configuration, and the optional backlog item
+  levels).
 
 - `read_key_list`, `write_key_list`: read and write a list of keys.
 
@@ -295,6 +317,11 @@ from backlogops import (
 - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
   and set planned dates from the estimate.
 
+- `DefaultStoryPoints`, `use_story_points`: what a backlog item that
+  nobody has estimated counts as, and the story points to work any one
+  item with. The estimate uses them, so an unestimated item does not
+  count as free.
+
 - `estimate_release_dates`, `release_plan_on_estimate`,
   `adjust_release_content`: estimate and plan release dates, and adjust
   release content to fit the planned dates.
@@ -321,14 +348,21 @@ from backlogops import (
 - `JiraIOConfig`, `JiraPreset`: the Jira connection and preset
   configuration.
 
+- `format_add_result`, `format_backlog_updates`, `format_release_result`,
+  `format_release_updates`, `format_rank_result`, `format_order_result`,
+  `format_rename_result`: turn the result of a Jira operation into a
+  listing that opens with what Jira refused or what was skipped.
+  `report_has_problems` answers whether such a listing reports something
+  that did not happen, which is what marks it in a user interface.
+
 For the full set of public names see the API documentation linked above.
 
 ## 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-1.2 → backlogops-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.
 
@@ -226,8 +246,10 @@ from backlogops import (
 
 - `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).
+  `BacklogOpsConfig` (workforce, named input and output presets, the
+  status-name map, the guess for unestimated items, the GUI display
+  settings, the Jira configuration, and the optional backlog item
+  levels).
 
 - `read_key_list`, `write_key_list`: read and write a list of keys.
 
@@ -259,6 +281,11 @@ from backlogops import (
 - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
   and set planned dates from the estimate.
 
+- `DefaultStoryPoints`, `use_story_points`: what a backlog item that
+  nobody has estimated counts as, and the story points to work any one
+  item with. The estimate uses them, so an unestimated item does not
+  count as free.
+
 - `estimate_release_dates`, `release_plan_on_estimate`,
   `adjust_release_content`: estimate and plan release dates, and adjust
   release content to fit the planned dates.
@@ -285,14 +312,21 @@ from backlogops import (
 - `JiraIOConfig`, `JiraPreset`: the Jira connection and preset
   configuration.
 
+- `format_add_result`, `format_backlog_updates`, `format_release_result`,
+  `format_release_updates`, `format_rank_result`, `format_order_result`,
+  `format_rename_result`: turn the result of a Jira operation into a
+  listing that opens with what Jira refused or what was skipped.
+  `report_has_problems` answers whether such a listing reports something
+  that did not happen, which is what marks it in a user interface.
+
 For the full set of public names see the API documentation linked above.
 
 ## 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-1.2 → backlogops-1.3}/backlogops.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops
-Version: 1.2
+Version: 1.3
 Summary: Library with backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -26,9 +26,9 @@ Requires-Dist: cryptography>=50.0.1
 Requires-Dist: jira[cli,opt]>=3.10.5
 Requires-Dist: tableio>=1.1
 Requires-Dist: tableio-cfg-json>=1.4
-Requires-Dist: wizard-ui-bridge[textual]>=1.3
+Requires-Dist: wizard-ui-bridge[textual]>=1.4
 Requires-Dist: versionreporter>=0.4
-Requires-Dist: edit-cfg-json>=0.2.0
+Requires-Dist: edit-cfg-json>=0.3.0
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -77,6 +77,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.
@@ -111,7 +115,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.
 
@@ -130,6 +143,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
@@ -154,7 +171,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.
 
@@ -262,8 +282,10 @@ from backlogops import (
 
 - `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).
+  `BacklogOpsConfig` (workforce, named input and output presets, the
+  status-name map, the guess for unestimated items, the GUI display
+  settings, the Jira configuration, and the optional backlog item
+  levels).
 
 - `read_key_list`, `write_key_list`: read and write a list of keys.
 
@@ -295,6 +317,11 @@ from backlogops import (
 - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
   and set planned dates from the estimate.
 
+- `DefaultStoryPoints`, `use_story_points`: what a backlog item that
+  nobody has estimated counts as, and the story points to work any one
+  item with. The estimate uses them, so an unestimated item does not
+  count as free.
+
 - `estimate_release_dates`, `release_plan_on_estimate`,
   `adjust_release_content`: estimate and plan release dates, and adjust
   release content to fit the planned dates.
@@ -321,14 +348,21 @@ from backlogops import (
 - `JiraIOConfig`, `JiraPreset`: the Jira connection and preset
   configuration.
 
+- `format_add_result`, `format_backlog_updates`, `format_release_result`,
+  `format_release_updates`, `format_rank_result`, `format_order_result`,
+  `format_rename_result`: turn the result of a Jira operation into a
+  listing that opens with what Jira refused or what was skipped.
+  `report_has_problems` answers whether such a listing reports something
+  that did not happen, which is what marks it in a user interface.
+
 For the full set of public names see the API documentation linked above.
 
 ## 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-1.2 → backlogops-1.3}/backlogops.egg-info/SOURCES.txt

@@ -23,6 +23,7 @@ src/backlogops/config_descriptions.py
 src/backlogops/config_editing.py
 src/backlogops/config_file_io.py
 src/backlogops/date_ranges.py
+src/backlogops/default_story_points.py
 src/backlogops/demo_backlog.py
 src/backlogops/estimate_ready_date.py
 src/backlogops/format_rules.py
@@ -45,6 +46,8 @@ src/backlogops/jira_write.py
 src/backlogops/jira_write_fields.py
 src/backlogops/jira_write_format.py
 src/backlogops/jira_write_releases.py
+src/backlogops/jira_write_status.py
+src/backlogops/jira_write_types.py
 src/backlogops/key_list_io.py
 src/backlogops/levels.py
 src/backlogops/move_keys_first.py
@@ -60,6 +63,7 @@ src/backlogops/rename_list_io.py
 src/backlogops/table_create.py
 src/backlogops/table_rows.py
 src/backlogops/team.py
+src/backlogops/use_story_points.py
 src/backlogops/wizard_forms.py
 src/backlogops/wizard_helpers.py
 src/backlogops/wizard_navigator.py

{backlogops-1.2 → backlogops-1.3}/backlogops.egg-info/requires.txt

@@ -3,6 +3,6 @@ cryptography>=50.0.1
 jira[cli,opt]>=3.10.5
 tableio>=1.1
 tableio-cfg-json>=1.4
-wizard-ui-bridge[textual]>=1.3
+wizard-ui-bridge[textual]>=1.4
 versionreporter>=0.4
-edit-cfg-json>=0.2.0
+edit-cfg-json>=0.3.0

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

@@ -5,7 +5,7 @@ from setuptools import setup
 
 setup(
   name='backlogops',
-  version='1.2',
+  version='1.3',
   description='Library with backlog operations.',
   author='Tom Björkholm',
   author_email='klausuler_linnet0q@icloud.com',
@@ -19,8 +19,8 @@ setup(
     'jira[cli,opt] >= 3.10.5',
     'tableio >= 1.1',
     'tableio-cfg-json >= 1.4',
-    'wizard-ui-bridge[textual] >= 1.3',
+    'wizard-ui-bridge[textual] >= 1.4',
     'versionreporter >= 0.4',
-    'edit-cfg-json >= 0.2.0',
+    'edit-cfg-json >= 0.3.0',
   ]
 )

{backlogops-1.2 → backlogops-1.3}/src/backlogops/__init__.py

@@ -36,6 +36,8 @@ from backlogops.config_editing import EDIT_SETTINGS, descriptions_for
 from backlogops.config_file_io import (
     CONFIG_EXTENSION, io_preset_class, read_io_preset, safe_write_config)
 from backlogops.date_ranges import check_date_range, check_no_overlap
+from backlogops.default_story_points import (
+    DefaultStoryPointLevel, DefaultStoryPoints)
 from backlogops.demo_backlog import get_demo_backlog
 from backlogops.estimate_ready_date import (
     estimate_ready_date, set_plan_from_estimate)
@@ -72,11 +74,14 @@ from backlogops.jira_update_releases import (
     UpdatedReleasesInJira, format_release_updates, update_releases_in_jira)
 from backlogops.jira_write import (
     AddedToJira, ExistsInJiraError, FailedItem, ItemNotInJiraError,
-    OnExistingKey, OnMissingKey, StatusMismatch, UnknownIssueTypeError,
+    OnExistingKey, OnMissingKey,
     add_backlog_to_jira, apply_jira_keys, jira_custom_fields,
     jira_editable_fields)
-from backlogops.jira_write_fields import FailedLink
-from backlogops.jira_write_format import format_add_result
+from backlogops.jira_write_fields import FailedField, FailedLink
+from backlogops.jira_write_status import StatusMismatch
+from backlogops.jira_write_types import UnknownIssueTypeError
+from backlogops.jira_write_format import (
+    format_add_result, report_has_problems)
 from backlogops.jira_write_releases import (
     AddedReleasesToJira, FailedRelease, ReleaseExistsError,
     add_releases_to_jira, format_release_result)
@@ -105,6 +110,8 @@ from backlogops.table_rows import (
     display_level_rows, fold_level_name, item_to_row, map_column_order,
     release_to_row, row_to_item, row_to_release)
 from backlogops.team import FteException, Membership, Team
+from backlogops.use_story_points import find_keys_with_children, \
+    use_story_points
 from backlogops.work_hours import (
     CompanyWorkHours, DEFAULT_WORK_WEEK, ExceptionWorkHours, ScheduleWorkHours,
     WeekDay)
@@ -116,9 +123,11 @@ __all__ = [
     'CLEAR_TOKEN_WARNING', 'CONFIG_DESCRIPTIONS', 'CONFIG_EXTENSION',
     'CompanyWorkHours', 'DEFAULT_LEVELS',
     'DEFAULT_WORK_WEEK', 'DEF_BACKLOG_COLUMN_MAP', 'DEF_RELEASE_COLUMN_MAP',
-    'DEF_STATUS_INPUT_MAP', 'DependencyMode', 'EDIT_SETTINGS',
+    'DEF_STATUS_INPUT_MAP', 'DefaultStoryPointLevel', 'DefaultStoryPoints',
+    'DependencyMode', 'EDIT_SETTINGS',
     'ExceptionWorkHours',
-    'ExistsInJiraError', 'FailedItem', 'FailedLink', 'FailedRelease',
+    'ExistsInJiraError', 'FailedField', 'FailedItem', 'FailedLink',
+    'FailedRelease',
     'FailedRename', 'FileExistsCb', 'FormatRules', 'FteException',
     'GUI_DESCRIPTIONS', 'GuiDisplayConfig', 'INPUT_DESCRIPTIONS',
     'InputFormatConfig', 'ItemNotInJiraError', 'JIRA_DESCRIPTIONS',
@@ -145,7 +154,8 @@ __all__ = [
     'display_level_order', 'display_level_rows',
     'encrypt_token_file',
     'encrypt_token_to_file', 'estimate_ready_date', 'estimate_release_dates',
-    'event_finish', 'event_start', 'find_cycle', 'fold_level_name',
+    'event_finish', 'event_start', 'find_cycle', 'find_keys_with_children',
+    'fold_level_name',
     'format_add_result', 'format_backlog', 'format_backlog_updates',
     'format_content_changes', 'format_date_changes', 'format_order_result',
     'format_rank_result', 'format_release_result', 'format_release_updates',
@@ -163,10 +173,11 @@ __all__ = [
     'read_backlog_ops_config', 'read_backlog_releases', 'read_io_preset',
     'read_jira_from_config', 'read_key_list', 'read_name_list', 'read_renames',
     'release_plan_on_estimate', 'release_to_row', 'rename_release_in_jira',
-    'rename_releases_in_jira', 'resolve_input_config', 'resolve_jql',
+    'rename_releases_in_jira', 'report_has_problems',
+    'resolve_input_config', 'resolve_jql',
     'resolve_output_config', 'row_to_item', 'row_to_release',
     'safe_write_config', 'set_plan_from_estimate', 'updatable_backlog_fields',
-    'update_backlog_in_jira', 'update_releases_in_jira',
+    'update_backlog_in_jira', 'update_releases_in_jira', 'use_story_points',
     'write_available_teams', 'write_backlog_ops_config',
     'write_backlog_releases', 'write_content_changes', 'write_date_changes',
     'write_key_list']

{backlogops-1.2 → backlogops-1.3}/src/backlogops/backlog.py

@@ -61,7 +61,12 @@ class BacklogItem:  # pylint: disable=too-many-instance-attributes
              not contain any of the characters , . ; : ( ) [ ] { }.
         level: The level of the backlog item. Required. Must be an integer.
         title: The title of the backlog item. Required.
-        story_points: The story points of the backlog item.
+        story_points: The story points of the backlog item, or None
+                      when nobody has estimated it yet. May be a
+                      fraction, such as 0.5. What the work on the
+                      item is counted as, which is another matter,
+                      is answered by
+                      :func:`backlogops.use_story_points`.
         status: The status of the backlog item.
         parent_key: The key of the parent backlog item. Optional.
                     Must exist as a key in the backlog.
@@ -100,7 +105,7 @@ class BacklogItem:  # pylint: disable=too-many-instance-attributes
     key: str
     level: int
     title: str
-    story_points: int
+    story_points: Optional[float]
     status: Status
     parent_key: Optional[str] = None
     release: Optional[str] = None

{backlogops-1.2 → backlogops-1.3}/src/backlogops/backlog_helpers.py

@@ -128,14 +128,19 @@ def accepts_none(data_type: object) -> bool:
 def _matches_class(value: object, data_type: type) -> bool:
     """Return True if a value matches a plain (unparameterized) class.
 
-    A boolean is rejected where an integer is expected, because a
+    A boolean is rejected where a number is expected, because a
     boolean is rarely a meaningful story point or numeric value here.
+    An integer is accepted where a ``float`` is expected, because that
+    is what the type hint itself means: a hint of ``float`` covers a
+    whole number as well, as the type checker reads it.
     A ``datetime`` is rejected where a ``date`` is expected, even though
     ``datetime`` is a subclass of ``date``, so that a date field never
     silently holds a value carrying a time component.
     """
     if data_type is int:
         return isinstance(value, int) and not isinstance(value, bool)
+    if data_type is float:
+        return isinstance(value, (int, float)) and not isinstance(value, bool)
     if data_type is date:
         return isinstance(value, date) and not isinstance(value, datetime)
     return isinstance(value, data_type)
@@ -422,14 +427,43 @@ def convert_to_str(field_name: str, value: object,
     report_wrong_type(field_name, value, str, stderr_file)
 
 
+def convert_to_float(field_name: str, value: object,
+                     stderr_file: TextIO = sys.stderr) -> float:
+    """Convert a whole or decimal number to a ``float``.
+
+    A value that is already a float is returned unchanged, and a whole
+    number is widened to a float, so that story points written as ``5``
+    and as ``5.0`` are stored as one type. A boolean is rejected, even
+    though Python counts it as a whole number. A string is rejected as
+    well: a numeric field of a backlog item holds a number, and the
+    reading of a table cell that holds text is where such text is
+    turned into a number.
+
+    Args:
+        field_name: The name of the field being converted.
+        value: The number to convert.
+        stderr_file: The file to report errors to.
+
+    Returns:
+        The converted float.
+
+    Raises:
+        TypeError: If the value is not a whole or decimal number.
+    """
+    if isinstance(value, bool) or not isinstance(value, (int, float)):
+        report_wrong_type(field_name, value, float, stderr_file)
+    return float(value)
+
+
 def convert_field_value(field_name: str, value: object, data_type: object,
                         stderr_file: TextIO = sys.stderr) -> object:
     """Convert and validate a single field value against its type hint.
 
     ``None`` is accepted for optional fields. Enum fields are converted
     with :func:`convert_to_enum`, date fields with :func:`convert_to_date`,
-    string fields with :func:`convert_to_str`, and all other fields are
-    checked with :func:`value_matches_type`.
+    string fields with :func:`convert_to_str`, float fields with
+    :func:`convert_to_float`, and all other fields are checked with
+    :func:`value_matches_type`.
 
     Args:
         field_name: The name of the field being converted.
@@ -453,6 +487,8 @@ def convert_field_value(field_name: str, value: object, data_type: object,
         return convert_to_date(field_name, value, stderr_file)
     if inner_type is str:
         return convert_to_str(field_name, value, stderr_file)
+    if inner_type is float:
+        return convert_to_float(field_name, value, stderr_file)
     if not value_matches_type(value, data_type):
         report_wrong_type(field_name, value, data_type, stderr_file)
     return value

{backlogops-1.2 → backlogops-1.3}/src/backlogops/backlog_ops_config.py

@@ -15,6 +15,9 @@ item levels:
 * ``gui_display`` holds the GUI column-rename and level-display settings;
 * ``jira`` is the Jira input and output configuration, bridged to JSON by
   :class:`backlogops.jira_io_config.JiraIOConfig`;
+* ``default_story_points`` is what a backlog item that nobody has
+  estimated counts as, bridged to JSON by
+  :class:`backlogops.default_story_points.DefaultStoryPoints`;
 * ``levels`` is the optional list of backlog item levels. It is omitted
   from the file while it is ``None``; :meth:`BacklogOpsConfig.get_levels`
   then falls back to :data:`backlogops.levels.DEFAULT_LEVELS`. An empty
@@ -45,6 +48,7 @@ from backlogops.available_teams import AvailableTeams
 from backlogops.available_teams_config import AvailableTeamsConfig
 from backlogops.backlog import Status
 from backlogops.backlog_helpers import report_bad_value, report_wrong_type
+from backlogops.default_story_points import DefaultStoryPoints
 from backlogops.io_config import GuiDisplayConfig, InputFormatConfig, \
     OutputFormatConfig, _StatusMapValidator
 from backlogops.jira_io_config import JiraIOConfig
@@ -165,9 +169,10 @@ def _levels_to_json(value: object, *, path_text: str, stderr_file: TextIO,
 class _BacklogOpsReadOldConfig(ReadOldConfiguration):
     """Normalize older backlog-ops configuration files on read.
 
-    Two shape changes are accepted. The named input and output preset
-    maps were added after the first released file; an empty map is
-    supplied when an old file omits them. The workforce members were
+    Two shape changes are accepted. Sections added after a released file,
+    such as the named preset maps and the default story points, are
+    supplied empty when an old file omits them, which for the default
+    story points means guessing nothing. The workforce members were
     later moved from the top level into a nested ``available_teams``
     object; the move rules relocate them so old files keep loading.
     """
@@ -186,7 +191,7 @@ class _BacklogOpsReadOldConfig(ReadOldConfiguration):
         """Return defaults for the members old files may omit."""
         return {('input_configs',): {}, ('output_configs',): {},
                 ('gui_display',): {}, ('status_input_map',): {},
-                ('jira',): {}}
+                ('jira',): {}, ('default_story_points',): {}}
 
 
 DEF_STATUS_INPUT_MAP: dict[str, Status] = {
@@ -241,6 +246,9 @@ class BacklogOpsConfig(Config):  # pylint: disable=too-many-instance-attributes
             stderr_file=stderr_file,
             member_name=member_path(member_name, 'jira'))
         self.levels: Optional[list[Level]] = None
+        self.default_story_points: DefaultStoryPoints = DefaultStoryPoints(
+            stderr_file=stderr_file,
+            member_name=member_path(member_name, 'default_story_points'))
         self._unchecked_dicts = ['status_input_map']
         Config.__init__(self, from_json_data_text=from_json_data_text,
                         from_json_filename=from_json_filename,
@@ -254,7 +262,7 @@ class BacklogOpsConfig(Config):  # pylint: disable=too-many-instance-attributes
 
     @override
     def nested_configs(self) -> NestedConfigs:
-        """Declare the workforce and the named TableIO preset maps."""
+        """Declare the workforce, the preset maps and the other sections."""
         member = ConfigNesting(kind=ConfigNestingKind.MEMBER,
                                config_type=AvailableTeamsConfig)
         in_cfg = ConfigNesting(kind=ConfigNestingKind.DICT_VALUE,
@@ -265,8 +273,11 @@ class BacklogOpsConfig(Config):  # pylint: disable=too-many-instance-attributes
                             config_type=GuiDisplayConfig)
         jira = ConfigNesting(kind=ConfigNestingKind.MEMBER,
                              config_type=JiraIOConfig)
+        points = ConfigNesting(kind=ConfigNestingKind.MEMBER,
+                               config_type=DefaultStoryPoints)
         return {'available_teams': member, 'input_configs': in_cfg,
-                'output_configs': out_cfg, 'gui_display': gui, 'jira': jira}
+                'output_configs': out_cfg, 'gui_display': gui, 'jira': jira,
+                'default_story_points': points}
 
     @override
     def _omit_none_from_json(self) -> list[str]: