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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-gui
-Version: 1.2
+Version: 1.3
 Summary: Graphical user interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -21,11 +21,11 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: backlogops>=1.2
+Requires-Dist: backlogops>=1.3
 Requires-Dist: argcomplete>=3.7.2
-Requires-Dist: wizard-ui-bridge>=1.3
-Requires-Dist: wizard-tk-bridge>=1.3
-Requires-Dist: edit-cfg-json-tk>=0.2.0
+Requires-Dist: wizard-ui-bridge>=1.4
+Requires-Dist: wizard-tk-bridge>=1.4
+Requires-Dist: edit-cfg-json-tk>=0.3.0
 Requires-Dist: versionreporter>=0.4
 Dynamic: author
 Dynamic: license-file
@@ -75,6 +75,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.
@@ -109,7 +113,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.
 
@@ -128,6 +141,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
@@ -152,7 +169,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.
 
@@ -253,9 +273,11 @@ python -m backlogops_gui
 python -m backlogops_gui -c config_file.cfg
 ````
 
-At first startup you do not have any configuration file yet,
-so when you start the application it will start the configuration
-wizard.
+At first startup you do not have any configuration file yet, so the
+application shows a *No configuration* dialog offering to run the
+configuration wizard, load an existing configuration file, or exit.
+Cancelling the wizard or the file chooser returns to that dialog, so
+the application starts only once a configuration is in place.
 
 ## Main window
 
@@ -323,6 +345,17 @@ is in the menus.
 The backlog window shows 2 read-only tables: one with the backlog and
 one with the list of releases. You will want to use the menus.
 
+At the top of the window an information region records where the data
+came from and when it was read, marks the window once you change the
+backlog, and offers a **Read again** button that re-reads the same
+source (the same file, or the same Jira preset and filter) in place. A
+re-read with unsaved changes asks for confirmation first.
+
+Each Jira action answers in a copy-pasteable pop-up that leads with what
+did not happen: what Jira refused, then what was skipped, and last what
+succeeded. When something was refused the pop-up title is marked
+*NOT ALL SUCCEEDED*, so it is visible even behind another window.
+
 - Backlog
 
     - Order by keys...
@@ -365,10 +398,10 @@ one with the list of releases. You will want to use the menus.
 
 ## 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_gui-1.2 → backlogops_gui-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.
 
@@ -219,9 +239,11 @@ python -m backlogops_gui
 python -m backlogops_gui -c config_file.cfg
 ````
 
-At first startup you do not have any configuration file yet,
-so when you start the application it will start the configuration
-wizard.
+At first startup you do not have any configuration file yet, so the
+application shows a *No configuration* dialog offering to run the
+configuration wizard, load an existing configuration file, or exit.
+Cancelling the wizard or the file chooser returns to that dialog, so
+the application starts only once a configuration is in place.
 
 ## Main window
 
@@ -289,6 +311,17 @@ is in the menus.
 The backlog window shows 2 read-only tables: one with the backlog and
 one with the list of releases. You will want to use the menus.
 
+At the top of the window an information region records where the data
+came from and when it was read, marks the window once you change the
+backlog, and offers a **Read again** button that re-reads the same
+source (the same file, or the same Jira preset and filter) in place. A
+re-read with unsaved changes asks for confirmation first.
+
+Each Jira action answers in a copy-pasteable pop-up that leads with what
+did not happen: what Jira refused, then what was skipped, and last what
+succeeded. When something was refused the pop-up title is marked
+*NOT ALL SUCCEEDED*, so it is visible even behind another window.
+
 - Backlog
 
     - Order by keys...
@@ -331,10 +364,10 @@ one with the list of releases. You will want to use the menus.
 
 ## 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_gui-1.2 → backlogops_gui-1.3}/backlogops_gui.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-gui
-Version: 1.2
+Version: 1.3
 Summary: Graphical user interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -21,11 +21,11 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: backlogops>=1.2
+Requires-Dist: backlogops>=1.3
 Requires-Dist: argcomplete>=3.7.2
-Requires-Dist: wizard-ui-bridge>=1.3
-Requires-Dist: wizard-tk-bridge>=1.3
-Requires-Dist: edit-cfg-json-tk>=0.2.0
+Requires-Dist: wizard-ui-bridge>=1.4
+Requires-Dist: wizard-tk-bridge>=1.4
+Requires-Dist: edit-cfg-json-tk>=0.3.0
 Requires-Dist: versionreporter>=0.4
 Dynamic: author
 Dynamic: license-file
@@ -75,6 +75,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.
@@ -109,7 +113,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.
 
@@ -128,6 +141,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
@@ -152,7 +169,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.
 
@@ -253,9 +273,11 @@ python -m backlogops_gui
 python -m backlogops_gui -c config_file.cfg
 ````
 
-At first startup you do not have any configuration file yet,
-so when you start the application it will start the configuration
-wizard.
+At first startup you do not have any configuration file yet, so the
+application shows a *No configuration* dialog offering to run the
+configuration wizard, load an existing configuration file, or exit.
+Cancelling the wizard or the file chooser returns to that dialog, so
+the application starts only once a configuration is in place.
 
 ## Main window
 
@@ -323,6 +345,17 @@ is in the menus.
 The backlog window shows 2 read-only tables: one with the backlog and
 one with the list of releases. You will want to use the menus.
 
+At the top of the window an information region records where the data
+came from and when it was read, marks the window once you change the
+backlog, and offers a **Read again** button that re-reads the same
+source (the same file, or the same Jira preset and filter) in place. A
+re-read with unsaved changes asks for confirmation first.
+
+Each Jira action answers in a copy-pasteable pop-up that leads with what
+did not happen: what Jira refused, then what was skipped, and last what
+succeeded. When something was refused the pop-up title is marked
+*NOT ALL SUCCEEDED*, so it is visible even behind another window.
+
 - Backlog
 
     - Order by keys...
@@ -365,10 +398,10 @@ one with the list of releases. You will want to use the menus.
 
 ## 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_gui-1.3/backlogops_gui.egg-info/requires.txt

@@ -0,0 +1,6 @@
+backlogops>=1.3
+argcomplete>=3.7.2
+wizard-ui-bridge>=1.4
+wizard-tk-bridge>=1.4
+edit-cfg-json-tk>=0.3.0
+versionreporter>=0.4

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

@@ -5,7 +5,7 @@ from setuptools import setup
 
 setup(
   name='backlogops-gui',
-  version='1.2',
+  version='1.3',
   description='Graphical user interface for backlog operations.',
   author='Tom Björkholm',
   author_email='klausuler_linnet0q@icloud.com',
@@ -19,11 +19,11 @@ setup(
     ]
   },
   install_requires=[
-    'backlogops >= 1.2',
+    'backlogops >= 1.3',
     'argcomplete >= 3.7.2',
-    'wizard-ui-bridge >= 1.3',
-    'wizard-tk-bridge >= 1.3',
-    'edit-cfg-json-tk >= 0.2.0',
+    'wizard-ui-bridge >= 1.4',
+    'wizard-tk-bridge >= 1.4',
+    'edit-cfg-json-tk >= 0.3.0',
     'versionreporter >= 0.4'
   ]
 )

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/application.py

@@ -3,7 +3,7 @@
 
 The application opens a main window whose menu reads a backlog from a file
 or from Jira, loads or replaces the active configuration from a file, runs
-the teams configuration wizard, edits a configuration or a stand-alone
+the backlog-ops configuration wizard, edits a configuration or a stand-alone
 preset file in the folding editor of
 :mod:`backlogops_gui.config_edit`, creates a stand-alone input or output
 preset file, migrates a stand-alone preset file to the current format,
@@ -17,8 +17,8 @@ modified, and offers a "Read again" button that re-reads the same source.
 On macOS the menu bar sits at the top of the display rather than in
 the window, so the main window body shows a short description, the current
 configuration status, and a log of the most recent diagnostic messages, to
-make clear that the application is running. The teams configuration is
-taken from the file given with ``-c`` or from the configured locations;
+make clear that the application is running. The backlog-ops configuration
+is taken from the file given with ``-c`` or from the configured locations;
 when no configuration is found a startup dialog offers to run the wizard,
 load a configuration file, or exit. Cancelling the wizard or a dialog
 returns to that choice, so the application ends only when the user exits.
@@ -44,6 +44,7 @@ from config_as_json.file_extension import fix_file_extension
 from wizard_tk_bridge import WizardUiBridgeTk
 from backlogops import (
     AvailableTeams, BacklogOpsConfig, BacklogReleases, CONFIG_EXTENSION,
+    DefaultStoryPoints,
     GuiDisplayConfig, InputFormatConfig, Levels, OutputFormatConfig, Status,
     get_demo_backlog, get_backlog_ops_config, backlog_ops_wizard,
     preset_wizard, read_backlog_ops_config, read_io_preset, safe_write_config,
@@ -198,6 +199,10 @@ class BacklogApp:
         """Return the configured backlog item levels, or None when absent."""
         return self.config.get_levels() if self.config else None
 
+    def def_points(self) -> Optional[DefaultStoryPoints]:
+        """Return what an unestimated item is worked with, or None."""
+        return self.config.default_story_points if self.config else None
+
     def status_map(self) -> Optional[dict[str, Status]]:
         """Return the library-wide status input map, or None when absent."""
         return self.config.get_status_input_map() if self.config else None
@@ -614,8 +619,8 @@ class BacklogApp:
             rename_releases=self.jira.renamer.rename_action())
         BacklogWindow(self.root, data, title, self.out_presets,
                       self.available_teams, self.log, self.levels,
-                      self.gui_display, warning, handlers, source=source,
-                      reload=reload)
+                      self.gui_display, warning, handlers,
+                      def_points=self.def_points, source=source, reload=reload)
 
     def report_versions(self) -> None:
         """Report version information into the log on a worker thread.

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/backlog_actions.py

@@ -16,7 +16,8 @@ import tkinter as tk
 from datetime import timedelta
 from typing import Callable, Optional, TextIO
 from backlogops import (
-    AddedToJira, AvailableTeams, BacklogReleases, Levels, OutputFormatConfig,
+    AddedToJira, AvailableTeams, BacklogReleases, DefaultStoryPoints, Levels,
+    OutputFormatConfig,
     ReleaseChanges, ReleaseDateChanges, UpdatedBacklogInJira, allow_overwrite,
     apply_jira_keys, format_add_result, format_backlog_updates,
     format_content_changes, format_date_changes, get_keys_in_order,
@@ -248,11 +249,17 @@ def _run_change(parent: tk.Misc,
 
 # pylint: disable-next=too-many-arguments,too-many-positional-arguments
 def estimate_date(parent: tk.Misc, data: BacklogReleases,
-                  teams: Optional[AvailableTeams], sink: TextIO,
+                  teams: Optional[AvailableTeams],
+                  points: Optional[DefaultStoryPoints], sink: TextIO,
                   refresh: Callable[[], None],
                   on_error: Callable[[str, str], None],
                   on_info: Callable[[str, str], None]) -> None:
-    """Ask for the start date and estimate the ready dates."""
+    """Ask for the start date and estimate the ready dates.
+
+    An unestimated backlog item is worked with what the configuration
+    guesses for its level, so the guess of the loaded configuration is
+    passed on with the workforce.
+    """
     if teams is None:
         on_error('No configuration',
                  'There is no teams configuration to estimate from.')
@@ -261,10 +268,12 @@ def estimate_date(parent: tk.Misc, data: BacklogReleases,
     if choice is None:
         return
     ready_teams, start = teams, choice.start_date
+    guess = DefaultStoryPoints() if points is None else points
 
     def change() -> tuple[str, Optional[Callable[[str], None]]]:
         """Estimate the dates and return the release date change report."""
-        changes = data.estimate_ready_date(ready_teams, start, sink)
+        changes = data.estimate_ready_date(ready_teams, start, sink,
+                                           default_story_points=guess)
         return _date_report(changes, sink)
     _run_change(parent, change, refresh, on_error, on_info,
                 'Could not estimate ready date', 'Release date changes')

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/backlog_io.py

@@ -4,7 +4,7 @@
 These helpers wrap the library read and write functions and resolve the
 format the same way the command line does: an empty value infers the
 format from the file name, a value of only letters and digits is a preset
-name looked up in the presets from the teams configuration, and any other
+name looked up in the presets of the backlog-ops configuration, and any other
 value is the path of a stand-alone format configuration file. Diagnostics
 go to the given sink, because a graphical application shows them in a log
 view rather than on a console.

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/backlog_window.py

@@ -26,10 +26,12 @@ from wizard_tk_bridge.auto_scroll import auto_hide
 from wizard_tk_bridge.close_binding import CLOSE_ACCELERATOR, bind_close
 from backlogops import (
     AddedReleasesToJira, AddedToJira, AvailableTeams, BacklogReleases,
+    DefaultStoryPoints,
     GuiDisplayConfig, Levels, OrderedReleasesInJira, OutputFormatConfig,
     RankedInJira, RenamedReleasesInJira, UpdatedBacklogInJira,
     UpdatedReleasesInJira, format_order_result, format_rank_result,
-    format_release_result, format_release_updates, format_rename_result)
+    format_release_result, format_release_updates, format_rename_result,
+    report_has_problems)
 from backlogops_gui.backlog_actions import (
     adjust_content, apply_add_result, apply_update_result, estimate_date,
     extract_keys, order_by_deps, order_by_keys, order_by_release, order_dates,
@@ -41,6 +43,8 @@ from backlogops_gui.table_view import (
 RELEASE_COLUMN_WIDTH = 110
 WARNING_WRAP = 760
 MODIFIED_MARK = ' — Modified'
+PROBLEM_MARK = ' — NOT ALL SUCCEEDED'
+"""Added to a Jira pop-up title when the listing reports a problem."""
 
 
 def current_time() -> datetime:
@@ -112,6 +116,8 @@ class BacklogWindow:
                      [], GuiDisplayConfig] = GuiDisplayConfig,
                  warning: Optional[str] = None,
                  jira: Optional[JiraHandlers] = None, *,
+                 def_points: Callable[
+                     [], Optional[DefaultStoryPoints]] = lambda: None,
                  source: Optional[BacklogSource] = None,
                  reload: Optional[Callable[
                      [Callable[[BacklogReleases, Optional[str]], None]],
@@ -123,7 +129,8 @@ class BacklogWindow:
             data: The backlog and releases to show.
             title: The window title, typically the source file name.
             presets: Callable returning the current output presets.
-            teams: Callable returning the loaded teams configuration.
+            teams: Callable returning the loaded workforce, or None when
+                no configuration is loaded.
             sink: Stream that receives low-level write diagnostics.
             levels: Callable returning the configured levels, or None for
                 the default levels.
@@ -135,6 +142,8 @@ class BacklogWindow:
             jira: The Jira menu handlers to offer, or None for none. Each
                 handler is None when its operation is unavailable, which
                 disables its menu item.
+            def_points: Callable returning what the configuration works an
+                unestimated backlog item with, or None for none.
             source: Where the data came from and when it was read. When
                 given, an information region is shown at the top of the
                 window; when None no information region is shown.
@@ -146,6 +155,7 @@ class BacklogWindow:
         self._data = data
         self._presets = presets
         self._teams = teams
+        self._def_points = def_points
         self._sink = sink
         self._levels = levels
         self._gui_display = gui_display
@@ -461,8 +471,8 @@ class BacklogWindow:
 
     def _estimate_date(self) -> None:
         """Estimate the ready dates and refresh the tables."""
-        estimate_date(self._win, self._data, self._teams(), self._sink,
-                      self._changed_refresh, self._report_error,
+        estimate_date(self._win, self._data, self._teams(), self._def_points(),
+                      self._sink, self._changed_refresh, self._report_error,
                       self._report_info)
 
     def _set_plan(self) -> None:
@@ -503,7 +513,18 @@ class BacklogWindow:
 
     def _show_add_report(self, text: str) -> None:
         """Show the add result text in a copy-pasteable pop-up."""
-        show_text_report(self._win, 'Added to Jira', text)
+        self._show_jira_report('Added to Jira', text)
+
+    def _show_jira_report(self, title: str, text: str) -> None:
+        """Show a Jira result listing, marking a title with problems.
+
+        A listing reporting something that did not happen gets a marked
+        title, so the user sees that not everything succeeded even when
+        the pop-up shows only its first lines or the log is hidden behind
+        another window.
+        """
+        mark = PROBLEM_MARK if report_has_problems(text) else ''
+        show_text_report(self._win, f'{title}{mark}', text)
 
     def _releases_add(self) -> None:
         """Add the shown releases to Jira and show the result lists."""
@@ -516,8 +537,8 @@ class BacklogWindow:
         A release name never changes, so the shown releases already match
         what was added and no rebuild of the tables is needed.
         """
-        show_text_report(self._win, 'Add releases to Jira',
-                         format_release_result(result))
+        self._show_jira_report('Add releases to Jira',
+                               format_release_result(result))
 
     def _releases_update(self) -> None:
         """Update the shown releases in Jira and show the result lists."""
@@ -531,8 +552,8 @@ class BacklogWindow:
         failed releases. An update changes only the Jira versions, not the
         shown releases, so no rebuild of the tables is needed.
         """
-        show_text_report(self._win, 'Update releases in Jira',
-                         format_release_updates(result))
+        self._show_jira_report('Update releases in Jira',
+                               format_release_updates(result))
 
     def _backlog_update(self) -> None:
         """Update the shown backlog in Jira and show the result lists."""
@@ -551,7 +572,7 @@ class BacklogWindow:
 
     def _show_update_report(self, text: str) -> None:
         """Show the backlog update result text in a copy-pasteable pop-up."""
-        show_text_report(self._win, 'Update backlog in Jira', text)
+        self._show_jira_report('Update backlog in Jira', text)
 
     def _rank_jira(self) -> None:
         """Move chosen issues in the Jira rank order and show the result."""
@@ -564,8 +585,8 @@ class BacklogWindow:
         Ranking changes only the Jira rank of issues, not the shown
         backlog, so no rebuild of the tables is needed.
         """
-        show_text_report(self._win, 'Rank items in Jira',
-                         format_rank_result(result))
+        self._show_jira_report('Rank items in Jira',
+                               format_rank_result(result))
 
     def _releases_order(self) -> None:
         """Order the releases in Jira and show the result lists."""
@@ -578,8 +599,8 @@ class BacklogWindow:
         Ordering changes only the Jira version order, not the shown
         releases, so no rebuild of the tables is needed.
         """
-        show_text_report(self._win, 'Order releases in Jira',
-                         format_order_result(result))
+        self._show_jira_report('Order releases in Jira',
+                               format_order_result(result))
 
     def _releases_rename(self) -> None:
         """Rename the shown releases in Jira and show the result lists."""
@@ -592,5 +613,5 @@ class BacklogWindow:
         Renaming changes only the Jira version names, not the shown
         releases, so no rebuild of the tables is needed.
         """
-        show_text_report(self._win, 'Rename releases in Jira',
-                         format_rename_result(result))
+        self._show_jira_report('Rename releases in Jira',
+                               format_rename_result(result))

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/format_dialogs.py

@@ -2,7 +2,7 @@
 """File-format option dialogs for reading and writing backlog files.
 
 The format options mirror the command line: the format is either inferred
-from the file name, taken from a named preset stored in the teams
+from the file name, taken from a named preset stored in the backlog-ops
 configuration, or read from a stand-alone configuration file. Writing also
 offers to put the releases before the backlog. The chosen format is
 returned as a single value understood by the resolver in

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/jira_dialogs.py

@@ -560,7 +560,7 @@ class JiraRankDialog(ModalDialog):
         load_keys_into(self._win, self._text, self._sink)
 
     def _confirm(self) -> None:
-        """Store the preset, filter, keys and end, requiring preset+keys."""
+        """Store the preset, filter, keys and anchor, needing preset+keys."""
         name = self._preset.get()
         if not name:
             messagebox.showerror('No Jira preset', 'Select a Jira preset.',

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/jira_rank.py

@@ -1,12 +1,14 @@
 #! /usr/local/bin/python3
-"""Move issues to the front or end of a Jira backlog by rank.
-
-The ranker offers a handler that asks for a preset, the keys to move and
-which end to move them to, then ranks them in Jira on a worker thread and
-hands the result back to the GUI thread. It is available only when a
-configuration with Jira presets is loaded. The backlog and the current
-ranking come from Jira through the preset, not from the shown backlog, so
-the handler does not need the shown data.
+"""Move issues to a chosen anchor of a Jira backlog by rank.
+
+The ranker offers a handler that asks for a preset, an issue filter, the
+keys to move, the anchor to move them to and whether to honour relations,
+then ranks them in Jira on a worker thread and hands the result back to the
+GUI thread. The anchor is either end of the backlog or the first or last of
+the listed keys. It is available only when a configuration with Jira presets
+is loaded. The backlog and the current ranking come from Jira through the
+preset, not from the shown backlog, so the handler does not need the shown
+data.
 """
 
 # Copyright (c) 2026, Tom Björkholm
@@ -20,7 +22,7 @@ from backlogops_gui.jira_dialogs import JiraRankOptions, ask_jira_rank
 
 # pylint: disable-next=too-few-public-methods
 class JiraRanker(JiraAction):
-    """Moves issues to the front or end of a Jira backlog by rank."""
+    """Moves issues to a chosen anchor of a Jira backlog by rank."""
 
     def rank_action(self) -> Optional[Callable[
             [Callable[[RankedInJira], None]], None]]:
@@ -28,7 +30,7 @@ class JiraRanker(JiraAction):
         return self._rank if self._available() else None
 
     def _rank(self, on_done: Callable[[RankedInJira], None]) -> None:
-        """Ask for a preset, filter, keys and end, then rank in Jira."""
+        """Ask for a preset, filter, keys and anchor, then rank in Jira."""
         options = ask_jira_rank(self._app.root, self._preset_filters(),
                                 self._app.log)
         if options is None:

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/jira_update.py

@@ -110,11 +110,16 @@ class JiraUpdater(JiraAction):
 
         def done(result: UpdatedBacklogInJira) -> None:
             """Hand the result to the window and log the completed update."""
+            added = result.added
             summary = (
                 f"Updated {len(result.updated)} backlog items in Jira; "
                 f"{len(result.already_correct)} already correct; "
                 f"{len(result.ignored)} ignored; "
-                f"{len(result.added.stored)} added "
-                f"(preset '{name}').\n")
+                f"{len(added.stored)} added; "
+                f"{len(added.failed)} not added; "
+                f"{len(result.failed_fields) + len(added.failed_fields)} "
+                "fields not set; "
+                f"{len(result.failed_links) + len(added.failed_links)} "
+                f"links not written (preset '{name}').\n")
             self._finish(on_done, result, summary)
         self._dispatch('Could not update backlog in Jira', name, call, done)

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/jira_write.py

@@ -70,7 +70,10 @@ class JiraWriter(JiraAction):
         def done(result: AddedToJira) -> None:
             """Hand the result to the window and log the completed write."""
             summary = (f"Added {len(result.stored)} backlog items to Jira; "
-                       f"{len(result.already_present)} already present "
+                       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 "
                        f"(preset '{name}').\n")
             self._finish(on_done, result, summary)
         self._dispatch('Could not add to Jira', name, call, done)

backlogops_gui-1.3/src/backlogops_gui/report_windows.py

@@ -0,0 +1,85 @@
+#! /usr/local/bin/python3
+"""Read-only text pop-ups for change listings and text reports.
+
+A change listing is shown with a Save-to-file and a Dismiss button, so the
+user can keep a record of what an action changed. A text report is shown
+read-only but copy-pasteable, with only a Dismiss button. Both show their
+text in a non-wrapping box with a vertical and a horizontal scrollbar, so
+the user sees that the text continues past the visible part of the window.
+Both return the created window so a caller or a test can drive or close it.
+"""
+
+# Copyright (c) 2026, Tom Björkholm
+# MIT License
+
+import tkinter as tk
+from typing import Callable
+from wizard_tk_bridge.close_binding import bind_close
+
+
+def _add_scrollbars(frame: tk.Frame, box: tk.Text) -> None:
+    """Add the vertical and horizontal scrollbars driving the text box."""
+    vertical = tk.Scrollbar(frame, orient='vertical', command=box.yview)
+    horizontal = tk.Scrollbar(frame, orient='horizontal', command=box.xview)
+    box.configure(yscrollcommand=vertical.set, xscrollcommand=horizontal.set)
+    vertical.grid(row=0, column=1, sticky='ns')
+    horizontal.grid(row=1, column=0, sticky='ew')
+
+
+def _scrolled_text(parent: tk.Misc, text: str, width: int,
+                   height: int) -> None:
+    """Pack a read-only scrollable box showing the text in the parent.
+
+    The text is shown in a disabled box, which still lets the user select
+    and copy it. The box does not wrap, so a line longer than the window
+    is reached with the horizontal scrollbar.
+    """
+    frame = tk.Frame(parent)
+    frame.pack(padx=12, pady=(10, 4), fill='both', expand=True)
+    frame.rowconfigure(0, weight=1)
+    frame.columnconfigure(0, weight=1)
+    box = tk.Text(frame, width=width, height=height, wrap='none')
+    box.insert('1.0', text)
+    box.configure(state='disabled')
+    box.grid(row=0, column=0, sticky='nsew')
+    _add_scrollbars(frame, box)
+
+
+def show_change_list(parent: tk.Misc, title: str, text: str,
+                     on_save: Callable[[], None]) -> tk.Toplevel:
+    """Show a change listing with Save-to-file and Dismiss buttons.
+
+    The listing is shown read-only in a scrollable box. The Save button
+    calls ``on_save`` and the Dismiss button closes the window. The created
+    window is returned so a caller (or a test) can drive or close it.
+    """
+    win = tk.Toplevel(parent)
+    win.title(title)
+    if isinstance(parent, tk.Wm):
+        win.transient(parent)
+    _scrolled_text(win, text, 50, 12)
+    button_bar = tk.Frame(win)
+    button_bar.pack(padx=12, pady=10, fill='x')
+    tk.Button(button_bar, text='Save to file…',
+              command=on_save).pack(side='left')
+    tk.Button(button_bar, text='Dismiss',
+              command=win.destroy).pack(side='right')
+    bind_close(win)
+    return win
+
+
+def show_text_report(parent: tk.Misc, title: str, text: str) -> tk.Toplevel:
+    """Show read-only, copy-pasteable text with a Dismiss button.
+
+    The report is shown in a scrollable box tall enough to show a listing
+    with a few entries per section without scrolling. The created window
+    is returned so a caller or a test can drive or close it.
+    """
+    win = tk.Toplevel(parent)
+    win.title(title)
+    if isinstance(parent, tk.Wm):
+        win.transient(parent)
+    _scrolled_text(win, text, 72, 24)
+    tk.Button(win, text='Dismiss', command=win.destroy).pack(padx=12, pady=10)
+    bind_close(win)
+    return win

{backlogops_gui-1.2 → backlogops_gui-1.3}/src/backlogops_gui/table_view.py

@@ -7,8 +7,10 @@ so the on-screen colors match a written spreadsheet: the status cell and the
 estimated-ready-date cell are highlighted by the format rules, and the other
 cells are left plain. The columns are the union of the field names met in the
 rows, kept in first-seen order, and every cell is rendered as text so the
-table can show any value type. A per-table column-name map can rename a
-column or drop it from the display, as the GUI display configuration decides.
+table can show any value type; a decimal number loses the trailing zeros
+it does not need, so story points read as ``1`` and ``0.5``. A per-table
+column-name map can rename a column or drop it from the display, as the GUI
+display configuration decides.
 """
 
 # Copyright (c) 2026, Tom Björkholm
@@ -42,7 +44,16 @@ def _columns(rows: Sequence[dict[str, ValueFmt]]) -> list[str]:
 
 
 def _cell_text(value: Value) -> str:
-    """Return one cell value rendered as display text."""
+    """Return one cell value rendered as display text.
+
+    A decimal number is shown without the trailing zeros it does not
+    need, so half a story point reads as ``0.5`` and a whole one as
+    ``1`` rather than ``1.0``. A whole number is already written
+    without a decimal point, and a boolean is not a decimal number in
+    Python, so both keep their own text.
+    """
+    if isinstance(value, float):
+        return f'{value:g}'
     return '' if value is None else str(value)
 
 

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

@@ -1,6 +0,0 @@
-backlogops>=1.2
-argcomplete>=3.7.2
-wizard-ui-bridge>=1.3
-wizard-tk-bridge>=1.3
-edit-cfg-json-tk>=0.2.0
-versionreporter>=0.4

backlogops_gui-1.2/src/backlogops_gui/report_windows.py

@@ -1,61 +0,0 @@
-#! /usr/local/bin/python3
-"""Read-only text pop-ups for change listings and text reports.
-
-A change listing is shown with a Save-to-file and a Dismiss button, so the
-user can keep a record of what an action changed. A text report is shown
-read-only but copy-pasteable, with only a Dismiss button. Both return the
-created window so a caller or a test can drive or close it.
-"""
-
-# Copyright (c) 2026, Tom Björkholm
-# MIT License
-
-import tkinter as tk
-from typing import Callable
-from wizard_tk_bridge.close_binding import bind_close
-
-
-def show_change_list(parent: tk.Misc, title: str, text: str,
-                     on_save: Callable[[], None]) -> tk.Toplevel:
-    """Show a change listing with Save-to-file and Dismiss buttons.
-
-    The listing is shown read-only. The Save button calls ``on_save`` and
-    the Dismiss button closes the window. The created window is returned
-    so a caller (or a test) can drive or close it.
-    """
-    win = tk.Toplevel(parent)
-    win.title(title)
-    if isinstance(parent, tk.Wm):
-        win.transient(parent)
-    box = tk.Text(win, width=50, height=12, wrap='none')
-    box.insert('1.0', text)
-    box.configure(state='disabled')
-    box.pack(padx=12, pady=(10, 4), fill='both', expand=True)
-    button_bar = tk.Frame(win)
-    button_bar.pack(padx=12, pady=10, fill='x')
-    tk.Button(button_bar, text='Save to file…',
-              command=on_save).pack(side='left')
-    tk.Button(button_bar, text='Dismiss',
-              command=win.destroy).pack(side='right')
-    bind_close(win)
-    return win
-
-
-def show_text_report(parent: tk.Misc, title: str, text: str) -> tk.Toplevel:
-    """Show read-only, copy-pasteable text with a Dismiss button.
-
-    The text is shown in a disabled text box, which still lets the user
-    select and copy it. The created window is returned so a caller or a
-    test can drive or close it.
-    """
-    win = tk.Toplevel(parent)
-    win.title(title)
-    if isinstance(parent, tk.Wm):
-        win.transient(parent)
-    box = tk.Text(win, width=50, height=14, wrap='none')
-    box.insert('1.0', text)
-    box.configure(state='disabled')
-    box.pack(padx=12, pady=(10, 4), fill='both', expand=True)
-    tk.Button(win, text='Dismiss', command=win.destroy).pack(padx=12, pady=10)
-    bind_close(win)
-    return win