backlogops 1.3__tar.gz → 1.5__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (83) hide show
  1. {backlogops-1.3/backlogops.egg-info → backlogops-1.5}/PKG-INFO +49 -21
  2. backlogops-1.3/PKG-INFO → backlogops-1.5/README_pypi.md +40 -49
  3. backlogops-1.3/README_pypi.md → backlogops-1.5/backlogops.egg-info/PKG-INFO +77 -13
  4. {backlogops-1.3 → backlogops-1.5}/backlogops.egg-info/SOURCES.txt +8 -0
  5. backlogops-1.5/backlogops.egg-info/requires.txt +8 -0
  6. {backlogops-1.3 → backlogops-1.5}/pyproject.toml +1 -0
  7. {backlogops-1.3 → backlogops-1.5}/setup.py +8 -8
  8. {backlogops-1.3 → backlogops-1.5}/src/backlogops/__init__.py +27 -11
  9. {backlogops-1.3 → backlogops-1.5}/src/backlogops/available_teams_config.py +5 -0
  10. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog.py +25 -4
  11. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog_helpers.py +48 -10
  12. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog_ops_config.py +21 -8
  13. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog_ops_wizard.py +75 -93
  14. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog_releases.py +38 -0
  15. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog_releases_io.py +43 -6
  16. {backlogops-1.3 → backlogops-1.5}/src/backlogops/blo_version_reporter.py +5 -3
  17. {backlogops-1.3 → backlogops-1.5}/src/backlogops/config_descriptions.py +82 -9
  18. {backlogops-1.3 → backlogops-1.5}/src/backlogops/config_editing.py +14 -11
  19. {backlogops-1.3 → backlogops-1.5}/src/backlogops/config_file_io.py +1 -1
  20. backlogops-1.5/src/backlogops/default_story_points.py +157 -0
  21. backlogops-1.5/src/backlogops/duration_text.py +79 -0
  22. backlogops-1.5/src/backlogops/estimate_ready_date.py +176 -0
  23. backlogops-1.5/src/backlogops/estimate_rt_ready_date.py +156 -0
  24. backlogops-1.5/src/backlogops/estimate_wizard.py +404 -0
  25. {backlogops-1.3 → backlogops-1.5}/src/backlogops/io_config.py +51 -12
  26. {backlogops-1.3 → backlogops-1.5}/src/backlogops/io_preset_wizard.py +7 -10
  27. backlogops-1.5/src/backlogops/jira_field_json.py +117 -0
  28. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_io_config.py +19 -3
  29. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_read.py +35 -5
  30. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_update_backlog.py +47 -32
  31. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_write.py +47 -24
  32. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_write_fields.py +15 -3
  33. backlogops-1.5/src/backlogops/jira_write_time.py +124 -0
  34. backlogops-1.5/src/backlogops/level_defaults.py +352 -0
  35. backlogops-1.5/src/backlogops/ready_date_schedule.py +325 -0
  36. backlogops-1.5/src/backlogops/remaining_time_config.py +289 -0
  37. {backlogops-1.3 → backlogops-1.5}/src/backlogops/table_rows.py +68 -6
  38. {backlogops-1.3 → backlogops-1.5}/src/backlogops/team.py +45 -1
  39. {backlogops-1.3 → backlogops-1.5}/src/backlogops/use_story_points.py +3 -2
  40. {backlogops-1.3 → backlogops-1.5}/src/backlogops/wizard_helpers.py +4 -110
  41. {backlogops-1.3 → backlogops-1.5}/src/backlogops/wizard_navigator.py +59 -24
  42. backlogops-1.3/backlogops.egg-info/requires.txt +0 -8
  43. backlogops-1.3/src/backlogops/default_story_points.py +0 -371
  44. backlogops-1.3/src/backlogops/estimate_ready_date.py +0 -439
  45. {backlogops-1.3 → backlogops-1.5}/LICENSE.txt +0 -0
  46. {backlogops-1.3 → backlogops-1.5}/backlogops.egg-info/dependency_links.txt +0 -0
  47. {backlogops-1.3 → backlogops-1.5}/backlogops.egg-info/top_level.txt +0 -0
  48. {backlogops-1.3 → backlogops-1.5}/setup.cfg +0 -0
  49. {backlogops-1.3 → backlogops-1.5}/src/backlogops/apply_format_rules.py +0 -0
  50. {backlogops-1.3 → backlogops-1.5}/src/backlogops/available_teams.py +0 -0
  51. {backlogops-1.3 → backlogops-1.5}/src/backlogops/backlog_in_release_order.py +0 -0
  52. {backlogops-1.3 → backlogops-1.5}/src/backlogops/date_ranges.py +0 -0
  53. {backlogops-1.3 → backlogops-1.5}/src/backlogops/demo_backlog.py +0 -0
  54. {backlogops-1.3 → backlogops-1.5}/src/backlogops/format_rules.py +0 -0
  55. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_connect.py +0 -0
  56. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_order_releases.py +0 -0
  57. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_rank_backlog.py +0 -0
  58. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_rank_by_keys.py +0 -0
  59. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_rank_move_keys.py +0 -0
  60. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_rename_releases.py +0 -0
  61. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_search.py +0 -0
  62. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_token.py +0 -0
  63. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_update_releases.py +0 -0
  64. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_wizard.py +0 -0
  65. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_write_format.py +0 -0
  66. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_write_releases.py +0 -0
  67. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_write_status.py +0 -0
  68. {backlogops-1.3 → backlogops-1.5}/src/backlogops/jira_write_types.py +0 -0
  69. {backlogops-1.3 → backlogops-1.5}/src/backlogops/key_list_io.py +0 -0
  70. {backlogops-1.3 → backlogops-1.5}/src/backlogops/levels.py +0 -0
  71. {backlogops-1.3 → backlogops-1.5}/src/backlogops/move_keys_first.py +0 -0
  72. {backlogops-1.3 → backlogops-1.5}/src/backlogops/name_list_io.py +0 -0
  73. {backlogops-1.3 → backlogops-1.5}/src/backlogops/no_text_io.py +0 -0
  74. {backlogops-1.3 → backlogops-1.5}/src/backlogops/order_by_dependencies.py +0 -0
  75. {backlogops-1.3 → backlogops-1.5}/src/backlogops/person.py +0 -0
  76. {backlogops-1.3 → backlogops-1.5}/src/backlogops/py.typed +0 -0
  77. {backlogops-1.3 → backlogops-1.5}/src/backlogops/release_backlog_updates.py +0 -0
  78. {backlogops-1.3 → backlogops-1.5}/src/backlogops/release_change_io.py +0 -0
  79. {backlogops-1.3 → backlogops-1.5}/src/backlogops/releases.py +0 -0
  80. {backlogops-1.3 → backlogops-1.5}/src/backlogops/rename_list_io.py +0 -0
  81. {backlogops-1.3 → backlogops-1.5}/src/backlogops/table_create.py +0 -0
  82. {backlogops-1.3 → backlogops-1.5}/src/backlogops/wizard_forms.py +0 -0
  83. {backlogops-1.3 → backlogops-1.5}/src/backlogops/work_hours.py +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: backlogops
3
- Version: 1.3
3
+ Version: 1.5
4
4
  Summary: Library with backlog operations.
5
5
  Author: Tom Björkholm
6
6
  Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -13,6 +13,7 @@ Classifier: Programming Language :: Python :: 3
13
13
  Classifier: Programming Language :: Python :: 3.12
14
14
  Classifier: Programming Language :: Python :: 3.13
15
15
  Classifier: Programming Language :: Python :: 3.14
16
+ Classifier: Programming Language :: Python :: 3.15
16
17
  Classifier: Operating System :: OS Independent
17
18
  Classifier: Intended Audience :: Developers
18
19
  Classifier: Topic :: Software Development :: Libraries :: Python Modules
@@ -21,14 +22,14 @@ Classifier: Typing :: Typed
21
22
  Requires-Python: >=3.12
22
23
  Description-Content-Type: text/markdown
23
24
  License-File: LICENSE.txt
24
- Requires-Dist: config-as-json>=1.7
25
- Requires-Dist: cryptography>=50.0.1
25
+ Requires-Dist: config-as-json>=1.8
26
+ Requires-Dist: cryptography>=50.0.2
26
27
  Requires-Dist: jira[cli,opt]>=3.10.5
27
- Requires-Dist: tableio>=1.1
28
- Requires-Dist: tableio-cfg-json>=1.4
29
- Requires-Dist: wizard-ui-bridge[textual]>=1.4
30
- Requires-Dist: versionreporter>=0.4
31
- Requires-Dist: edit-cfg-json>=0.3.0
28
+ Requires-Dist: tableio>=1.3
29
+ Requires-Dist: tableio-cfg-json>=2.0
30
+ Requires-Dist: wizard-ui-bridge[textual]>=1.5
31
+ Requires-Dist: versionreporter>=0.5
32
+ Requires-Dist: edit-cfg-json>=1.0.0
32
33
  Dynamic: author
33
34
  Dynamic: license-file
34
35
  Dynamic: requires-dist
@@ -77,6 +78,10 @@ The following functionality is available in all 3 packages:
77
78
  - Estimate ready date for the backlog items based on available teams, team
78
79
  velocity, vacation dates, periods with half time work, etc.
79
80
 
81
+ - Alternatively, where remaining time estimates are required, estimate ready
82
+ dates from the remaining time of the backlog items and the focus factor of the
83
+ teams (story points are recommended).
84
+
80
85
  - Configure what a backlog item that nobody has estimated counts as, per backlog
81
86
  item level, so that an unestimated item does not make the estimated dates too
82
87
  optimistic.
@@ -105,6 +110,9 @@ The following functionality is available in all 3 packages:
105
110
 
106
111
  - Rename columns when reading a file and when writing a file.
107
112
 
113
+ - Leave out columns that are empty on every row, when writing a file and when
114
+ showing the backlog in the GUI.
115
+
108
116
  - Map custom status names in input files to backlog item statuses.
109
117
 
110
118
  - Choose how backlog item levels are written: by number, by name, or both, and
@@ -116,8 +124,8 @@ The following functionality is available in all 3 packages:
116
124
 
117
125
  - A wizard to create a backlog-ops configuration file with the workforce, named
118
126
  input and output presets, level names, status name mapping, the guess for
119
- unestimated items, how the graphical user interface shows the data, and the
120
- Jira integration.
127
+ unestimated items, whether remaining time estimates are also used, how the
128
+ graphical user interface shows the data, and the Jira integration.
121
129
 
122
130
  - An editor showing a whole configuration file or a stand-alone preset file at
123
131
  once, folded where it is deep, to change a single value without stepping
@@ -147,6 +155,10 @@ The following functionality is available in all 3 packages:
147
155
  Jira refused or what was skipped, so a value that was not written is visible
148
156
  without reading the whole listing.
149
157
 
158
+ - Show the custom fields of Jira, the fields an issue's edit screen accepts, and
159
+ the raw JSON Jira holds for a field of an issue, to find the correct Jira
160
+ field mapping.
161
+
150
162
  ## The operating model
151
163
 
152
164
  The operating model that most of the functionality is designed for is that the
@@ -155,8 +167,8 @@ are ordered by priority and dependencies to allow the teams to work in the
155
167
  backlog order. Each backlog item and each release may have a planned ready date,
156
168
  that records what has been communicated to the customer. Each backlog item and
157
169
  each release may have an estimated ready date, that is calculated from the
158
- current backlog state, the team velocity, and what we know about the
159
- availability of the team members.
170
+ current backlog state, the team velocity (or, for remaining time estimates, the
171
+ focus factor), and what we know about the availability of the team members.
160
172
 
161
173
  ## The backlog item fields
162
174
 
@@ -191,7 +203,11 @@ the library:
191
203
 
192
204
  - `team` The team responsible for the backlog item. Optional. Must not be empty
193
205
  string. Must be a valid team name. If None the item can be done by any team.
194
- If not None. the item can only be done by the specified team.
206
+ If not None, the item can only be done by the specified team.
207
+
208
+ - `remaining_time` The remaining time of the backlog item, as ideal focused work
209
+ time of one person. Optional. Only used by the alternative remaining time
210
+ estimates; story points are recommended. Must not be negative.
195
211
 
196
212
  - `depends_on_f2s` The list of keys of the backlog items that must have been
197
213
  finished before the current item can start. May be empty.
@@ -231,7 +247,7 @@ pip install --upgrade backlogops
231
247
 
232
248
  For a better understanding of how to use the library, CLI or GUI, see the user
233
249
  documentation:
234
- [Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc//using_backlogops/README.md)
250
+ [Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/using_backlogops/README.md)
235
251
 
236
252
  ## API documentation
237
253
 
@@ -275,7 +291,9 @@ from backlogops import (
275
291
  ### Reading and writing
276
292
 
277
293
  - `read_backlog_releases`, `write_backlog_releases`: read and write a
278
- backlog and its releases from and to a table file.
294
+ backlog and its releases from and to a table file, including the
295
+ remaining time of each item, and leaving out columns that are empty
296
+ on every row when the output preset asks for it.
279
297
 
280
298
  - `read_available_teams`, `write_available_teams`: read and write the
281
299
  available-teams workforce on its own.
@@ -283,9 +301,9 @@ from backlogops import (
283
301
  - `read_backlog_ops_config`, `write_backlog_ops_config`,
284
302
  `get_backlog_ops_config`: read, write, and look up the top-level
285
303
  `BacklogOpsConfig` (workforce, named input and output presets, the
286
- status-name map, the guess for unestimated items, the GUI display
287
- settings, the Jira configuration, and the optional backlog item
288
- levels).
304
+ status-name map, the guess for unestimated items, whether remaining
305
+ time estimates are also used, the GUI display settings, the Jira
306
+ configuration, and the optional backlog item levels).
289
307
 
290
308
  - `read_key_list`, `write_key_list`: read and write a list of keys.
291
309
 
@@ -317,11 +335,21 @@ from backlogops import (
317
335
  - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
318
336
  and set planned dates from the estimate.
319
337
 
338
+ - `estimate_rt_ready_date`, `FeatureDisabled`: estimate ready dates from
339
+ remaining time and the focus factor of the teams instead of from story
340
+ points, refused with `FeatureDisabled` unless remaining time estimates
341
+ are enabled.
342
+
320
343
  - `DefaultStoryPoints`, `use_story_points`: what a backlog item that
321
344
  nobody has estimated counts as, and the story points to work any one
322
345
  item with. The estimate uses them, so an unestimated item does not
323
346
  count as free.
324
347
 
348
+ - `RemainingTimeConfig`, `parse_duration`, `format_duration`: whether
349
+ remaining time estimates are also used beside story points (story
350
+ points are recommended), with the focus factor and the guess for
351
+ unestimated items, and a remaining time read from and written as text.
352
+
325
353
  - `estimate_release_dates`, `release_plan_on_estimate`,
326
354
  `adjust_release_content`: estimate and plan release dates, and adjust
327
355
  release content to fit the planned dates.
@@ -359,10 +387,10 @@ For the full set of public names see the API documentation linked above.
359
387
 
360
388
  ## Test summary
361
389
 
362
- - Test result: 2555 passed, 1 deselected in 58s
390
+ - Test result: 2963 passed, 1 deselected in 74s (0:01:14)
363
391
  - No flake8 warnings.
364
392
  - No mypy errors found.
365
393
  - No pylint warnings.
366
394
  - No python layout warnings.
367
- - Built version(s): 1.3
368
- - Build and test using Python 3.14.7
395
+ - Built version(s): 1.5
396
+ - Build and test using Python 3.15.2
@@ -1,39 +1,3 @@
1
- Metadata-Version: 2.4
2
- Name: backlogops
3
- Version: 1.3
4
- Summary: Library with backlog operations.
5
- Author: Tom Björkholm
6
- Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
7
- License-Expression: MIT
8
- Project-URL: Homepage, https://github.com/tom-bjorkholm/backlog-ops
9
- Project-URL: Source code, https://github.com/tom-bjorkholm/backlog-ops
10
- Project-URL: Documentation, https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/
11
- Keywords: backlog,release planning,agile,scrum,scheduling,roadmap,project management,product owner,product management
12
- Classifier: Programming Language :: Python :: 3
13
- Classifier: Programming Language :: Python :: 3.12
14
- Classifier: Programming Language :: Python :: 3.13
15
- Classifier: Programming Language :: Python :: 3.14
16
- Classifier: Operating System :: OS Independent
17
- Classifier: Intended Audience :: Developers
18
- Classifier: Topic :: Software Development :: Libraries :: Python Modules
19
- Classifier: Topic :: Office/Business :: Scheduling
20
- Classifier: Typing :: Typed
21
- Requires-Python: >=3.12
22
- Description-Content-Type: text/markdown
23
- License-File: LICENSE.txt
24
- Requires-Dist: config-as-json>=1.7
25
- Requires-Dist: cryptography>=50.0.1
26
- Requires-Dist: jira[cli,opt]>=3.10.5
27
- Requires-Dist: tableio>=1.1
28
- Requires-Dist: tableio-cfg-json>=1.4
29
- Requires-Dist: wizard-ui-bridge[textual]>=1.4
30
- Requires-Dist: versionreporter>=0.4
31
- Requires-Dist: edit-cfg-json>=0.3.0
32
- Dynamic: author
33
- Dynamic: license-file
34
- Dynamic: requires-dist
35
- Dynamic: requires-python
36
-
37
1
  # backlogops
38
2
 
39
3
  There are 3 related packages for backlog operations:
@@ -77,6 +41,10 @@ The following functionality is available in all 3 packages:
77
41
  - Estimate ready date for the backlog items based on available teams, team
78
42
  velocity, vacation dates, periods with half time work, etc.
79
43
 
44
+ - Alternatively, where remaining time estimates are required, estimate ready
45
+ dates from the remaining time of the backlog items and the focus factor of the
46
+ teams (story points are recommended).
47
+
80
48
  - Configure what a backlog item that nobody has estimated counts as, per backlog
81
49
  item level, so that an unestimated item does not make the estimated dates too
82
50
  optimistic.
@@ -105,6 +73,9 @@ The following functionality is available in all 3 packages:
105
73
 
106
74
  - Rename columns when reading a file and when writing a file.
107
75
 
76
+ - Leave out columns that are empty on every row, when writing a file and when
77
+ showing the backlog in the GUI.
78
+
108
79
  - Map custom status names in input files to backlog item statuses.
109
80
 
110
81
  - Choose how backlog item levels are written: by number, by name, or both, and
@@ -116,8 +87,8 @@ The following functionality is available in all 3 packages:
116
87
 
117
88
  - A wizard to create a backlog-ops configuration file with the workforce, named
118
89
  input and output presets, level names, status name mapping, the guess for
119
- unestimated items, how the graphical user interface shows the data, and the
120
- Jira integration.
90
+ unestimated items, whether remaining time estimates are also used, how the
91
+ graphical user interface shows the data, and the Jira integration.
121
92
 
122
93
  - An editor showing a whole configuration file or a stand-alone preset file at
123
94
  once, folded where it is deep, to change a single value without stepping
@@ -147,6 +118,10 @@ The following functionality is available in all 3 packages:
147
118
  Jira refused or what was skipped, so a value that was not written is visible
148
119
  without reading the whole listing.
149
120
 
121
+ - Show the custom fields of Jira, the fields an issue's edit screen accepts, and
122
+ the raw JSON Jira holds for a field of an issue, to find the correct Jira
123
+ field mapping.
124
+
150
125
  ## The operating model
151
126
 
152
127
  The operating model that most of the functionality is designed for is that the
@@ -155,8 +130,8 @@ are ordered by priority and dependencies to allow the teams to work in the
155
130
  backlog order. Each backlog item and each release may have a planned ready date,
156
131
  that records what has been communicated to the customer. Each backlog item and
157
132
  each release may have an estimated ready date, that is calculated from the
158
- current backlog state, the team velocity, and what we know about the
159
- availability of the team members.
133
+ current backlog state, the team velocity (or, for remaining time estimates, the
134
+ focus factor), and what we know about the availability of the team members.
160
135
 
161
136
  ## The backlog item fields
162
137
 
@@ -191,7 +166,11 @@ the library:
191
166
 
192
167
  - `team` The team responsible for the backlog item. Optional. Must not be empty
193
168
  string. Must be a valid team name. If None the item can be done by any team.
194
- If not None. the item can only be done by the specified team.
169
+ If not None, the item can only be done by the specified team.
170
+
171
+ - `remaining_time` The remaining time of the backlog item, as ideal focused work
172
+ time of one person. Optional. Only used by the alternative remaining time
173
+ estimates; story points are recommended. Must not be negative.
195
174
 
196
175
  - `depends_on_f2s` The list of keys of the backlog items that must have been
197
176
  finished before the current item can start. May be empty.
@@ -231,7 +210,7 @@ pip install --upgrade backlogops
231
210
 
232
211
  For a better understanding of how to use the library, CLI or GUI, see the user
233
212
  documentation:
234
- [Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc//using_backlogops/README.md)
213
+ [Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/using_backlogops/README.md)
235
214
 
236
215
  ## API documentation
237
216
 
@@ -275,7 +254,9 @@ from backlogops import (
275
254
  ### Reading and writing
276
255
 
277
256
  - `read_backlog_releases`, `write_backlog_releases`: read and write a
278
- backlog and its releases from and to a table file.
257
+ backlog and its releases from and to a table file, including the
258
+ remaining time of each item, and leaving out columns that are empty
259
+ on every row when the output preset asks for it.
279
260
 
280
261
  - `read_available_teams`, `write_available_teams`: read and write the
281
262
  available-teams workforce on its own.
@@ -283,9 +264,9 @@ from backlogops import (
283
264
  - `read_backlog_ops_config`, `write_backlog_ops_config`,
284
265
  `get_backlog_ops_config`: read, write, and look up the top-level
285
266
  `BacklogOpsConfig` (workforce, named input and output presets, the
286
- status-name map, the guess for unestimated items, the GUI display
287
- settings, the Jira configuration, and the optional backlog item
288
- levels).
267
+ status-name map, the guess for unestimated items, whether remaining
268
+ time estimates are also used, the GUI display settings, the Jira
269
+ configuration, and the optional backlog item levels).
289
270
 
290
271
  - `read_key_list`, `write_key_list`: read and write a list of keys.
291
272
 
@@ -317,11 +298,21 @@ from backlogops import (
317
298
  - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
318
299
  and set planned dates from the estimate.
319
300
 
301
+ - `estimate_rt_ready_date`, `FeatureDisabled`: estimate ready dates from
302
+ remaining time and the focus factor of the teams instead of from story
303
+ points, refused with `FeatureDisabled` unless remaining time estimates
304
+ are enabled.
305
+
320
306
  - `DefaultStoryPoints`, `use_story_points`: what a backlog item that
321
307
  nobody has estimated counts as, and the story points to work any one
322
308
  item with. The estimate uses them, so an unestimated item does not
323
309
  count as free.
324
310
 
311
+ - `RemainingTimeConfig`, `parse_duration`, `format_duration`: whether
312
+ remaining time estimates are also used beside story points (story
313
+ points are recommended), with the focus factor and the guess for
314
+ unestimated items, and a remaining time read from and written as text.
315
+
325
316
  - `estimate_release_dates`, `release_plan_on_estimate`,
326
317
  `adjust_release_content`: estimate and plan release dates, and adjust
327
318
  release content to fit the planned dates.
@@ -359,10 +350,10 @@ For the full set of public names see the API documentation linked above.
359
350
 
360
351
  ## Test summary
361
352
 
362
- - Test result: 2555 passed, 1 deselected in 58s
353
+ - Test result: 2963 passed, 1 deselected in 74s (0:01:14)
363
354
  - No flake8 warnings.
364
355
  - No mypy errors found.
365
356
  - No pylint warnings.
366
357
  - No python layout warnings.
367
- - Built version(s): 1.3
368
- - Build and test using Python 3.14.7
358
+ - Built version(s): 1.5
359
+ - Build and test using Python 3.15.2
@@ -1,3 +1,40 @@
1
+ Metadata-Version: 2.4
2
+ Name: backlogops
3
+ Version: 1.5
4
+ Summary: Library with backlog operations.
5
+ Author: Tom Björkholm
6
+ Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
7
+ License-Expression: MIT
8
+ Project-URL: Homepage, https://github.com/tom-bjorkholm/backlog-ops
9
+ Project-URL: Source code, https://github.com/tom-bjorkholm/backlog-ops
10
+ Project-URL: Documentation, https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/
11
+ Keywords: backlog,release planning,agile,scrum,scheduling,roadmap,project management,product owner,product management
12
+ Classifier: Programming Language :: Python :: 3
13
+ Classifier: Programming Language :: Python :: 3.12
14
+ Classifier: Programming Language :: Python :: 3.13
15
+ Classifier: Programming Language :: Python :: 3.14
16
+ Classifier: Programming Language :: Python :: 3.15
17
+ Classifier: Operating System :: OS Independent
18
+ Classifier: Intended Audience :: Developers
19
+ Classifier: Topic :: Software Development :: Libraries :: Python Modules
20
+ Classifier: Topic :: Office/Business :: Scheduling
21
+ Classifier: Typing :: Typed
22
+ Requires-Python: >=3.12
23
+ Description-Content-Type: text/markdown
24
+ License-File: LICENSE.txt
25
+ Requires-Dist: config-as-json>=1.8
26
+ Requires-Dist: cryptography>=50.0.2
27
+ Requires-Dist: jira[cli,opt]>=3.10.5
28
+ Requires-Dist: tableio>=1.3
29
+ Requires-Dist: tableio-cfg-json>=2.0
30
+ Requires-Dist: wizard-ui-bridge[textual]>=1.5
31
+ Requires-Dist: versionreporter>=0.5
32
+ Requires-Dist: edit-cfg-json>=1.0.0
33
+ Dynamic: author
34
+ Dynamic: license-file
35
+ Dynamic: requires-dist
36
+ Dynamic: requires-python
37
+
1
38
  # backlogops
2
39
 
3
40
  There are 3 related packages for backlog operations:
@@ -41,6 +78,10 @@ The following functionality is available in all 3 packages:
41
78
  - Estimate ready date for the backlog items based on available teams, team
42
79
  velocity, vacation dates, periods with half time work, etc.
43
80
 
81
+ - Alternatively, where remaining time estimates are required, estimate ready
82
+ dates from the remaining time of the backlog items and the focus factor of the
83
+ teams (story points are recommended).
84
+
44
85
  - Configure what a backlog item that nobody has estimated counts as, per backlog
45
86
  item level, so that an unestimated item does not make the estimated dates too
46
87
  optimistic.
@@ -69,6 +110,9 @@ The following functionality is available in all 3 packages:
69
110
 
70
111
  - Rename columns when reading a file and when writing a file.
71
112
 
113
+ - Leave out columns that are empty on every row, when writing a file and when
114
+ showing the backlog in the GUI.
115
+
72
116
  - Map custom status names in input files to backlog item statuses.
73
117
 
74
118
  - Choose how backlog item levels are written: by number, by name, or both, and
@@ -80,8 +124,8 @@ The following functionality is available in all 3 packages:
80
124
 
81
125
  - A wizard to create a backlog-ops configuration file with the workforce, named
82
126
  input and output presets, level names, status name mapping, the guess for
83
- unestimated items, how the graphical user interface shows the data, and the
84
- Jira integration.
127
+ unestimated items, whether remaining time estimates are also used, how the
128
+ graphical user interface shows the data, and the Jira integration.
85
129
 
86
130
  - An editor showing a whole configuration file or a stand-alone preset file at
87
131
  once, folded where it is deep, to change a single value without stepping
@@ -111,6 +155,10 @@ The following functionality is available in all 3 packages:
111
155
  Jira refused or what was skipped, so a value that was not written is visible
112
156
  without reading the whole listing.
113
157
 
158
+ - Show the custom fields of Jira, the fields an issue's edit screen accepts, and
159
+ the raw JSON Jira holds for a field of an issue, to find the correct Jira
160
+ field mapping.
161
+
114
162
  ## The operating model
115
163
 
116
164
  The operating model that most of the functionality is designed for is that the
@@ -119,8 +167,8 @@ are ordered by priority and dependencies to allow the teams to work in the
119
167
  backlog order. Each backlog item and each release may have a planned ready date,
120
168
  that records what has been communicated to the customer. Each backlog item and
121
169
  each release may have an estimated ready date, that is calculated from the
122
- current backlog state, the team velocity, and what we know about the
123
- availability of the team members.
170
+ current backlog state, the team velocity (or, for remaining time estimates, the
171
+ focus factor), and what we know about the availability of the team members.
124
172
 
125
173
  ## The backlog item fields
126
174
 
@@ -155,7 +203,11 @@ the library:
155
203
 
156
204
  - `team` The team responsible for the backlog item. Optional. Must not be empty
157
205
  string. Must be a valid team name. If None the item can be done by any team.
158
- If not None. the item can only be done by the specified team.
206
+ If not None, the item can only be done by the specified team.
207
+
208
+ - `remaining_time` The remaining time of the backlog item, as ideal focused work
209
+ time of one person. Optional. Only used by the alternative remaining time
210
+ estimates; story points are recommended. Must not be negative.
159
211
 
160
212
  - `depends_on_f2s` The list of keys of the backlog items that must have been
161
213
  finished before the current item can start. May be empty.
@@ -195,7 +247,7 @@ pip install --upgrade backlogops
195
247
 
196
248
  For a better understanding of how to use the library, CLI or GUI, see the user
197
249
  documentation:
198
- [Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc//using_backlogops/README.md)
250
+ [Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/using_backlogops/README.md)
199
251
 
200
252
  ## API documentation
201
253
 
@@ -239,7 +291,9 @@ from backlogops import (
239
291
  ### Reading and writing
240
292
 
241
293
  - `read_backlog_releases`, `write_backlog_releases`: read and write a
242
- backlog and its releases from and to a table file.
294
+ backlog and its releases from and to a table file, including the
295
+ remaining time of each item, and leaving out columns that are empty
296
+ on every row when the output preset asks for it.
243
297
 
244
298
  - `read_available_teams`, `write_available_teams`: read and write the
245
299
  available-teams workforce on its own.
@@ -247,9 +301,9 @@ from backlogops import (
247
301
  - `read_backlog_ops_config`, `write_backlog_ops_config`,
248
302
  `get_backlog_ops_config`: read, write, and look up the top-level
249
303
  `BacklogOpsConfig` (workforce, named input and output presets, the
250
- status-name map, the guess for unestimated items, the GUI display
251
- settings, the Jira configuration, and the optional backlog item
252
- levels).
304
+ status-name map, the guess for unestimated items, whether remaining
305
+ time estimates are also used, the GUI display settings, the Jira
306
+ configuration, and the optional backlog item levels).
253
307
 
254
308
  - `read_key_list`, `write_key_list`: read and write a list of keys.
255
309
 
@@ -281,11 +335,21 @@ from backlogops import (
281
335
  - `estimate_ready_date`, `set_plan_from_estimate`: estimate ready dates
282
336
  and set planned dates from the estimate.
283
337
 
338
+ - `estimate_rt_ready_date`, `FeatureDisabled`: estimate ready dates from
339
+ remaining time and the focus factor of the teams instead of from story
340
+ points, refused with `FeatureDisabled` unless remaining time estimates
341
+ are enabled.
342
+
284
343
  - `DefaultStoryPoints`, `use_story_points`: what a backlog item that
285
344
  nobody has estimated counts as, and the story points to work any one
286
345
  item with. The estimate uses them, so an unestimated item does not
287
346
  count as free.
288
347
 
348
+ - `RemainingTimeConfig`, `parse_duration`, `format_duration`: whether
349
+ remaining time estimates are also used beside story points (story
350
+ points are recommended), with the focus factor and the guess for
351
+ unestimated items, and a remaining time read from and written as text.
352
+
289
353
  - `estimate_release_dates`, `release_plan_on_estimate`,
290
354
  `adjust_release_content`: estimate and plan release dates, and adjust
291
355
  release content to fit the planned dates.
@@ -323,10 +387,10 @@ For the full set of public names see the API documentation linked above.
323
387
 
324
388
  ## Test summary
325
389
 
326
- - Test result: 2555 passed, 1 deselected in 58s
390
+ - Test result: 2963 passed, 1 deselected in 74s (0:01:14)
327
391
  - No flake8 warnings.
328
392
  - No mypy errors found.
329
393
  - No pylint warnings.
330
394
  - No python layout warnings.
331
- - Built version(s): 1.3
332
- - Build and test using Python 3.14.7
395
+ - Built version(s): 1.5
396
+ - Build and test using Python 3.15.2
@@ -25,11 +25,15 @@ src/backlogops/config_file_io.py
25
25
  src/backlogops/date_ranges.py
26
26
  src/backlogops/default_story_points.py
27
27
  src/backlogops/demo_backlog.py
28
+ src/backlogops/duration_text.py
28
29
  src/backlogops/estimate_ready_date.py
30
+ src/backlogops/estimate_rt_ready_date.py
31
+ src/backlogops/estimate_wizard.py
29
32
  src/backlogops/format_rules.py
30
33
  src/backlogops/io_config.py
31
34
  src/backlogops/io_preset_wizard.py
32
35
  src/backlogops/jira_connect.py
36
+ src/backlogops/jira_field_json.py
33
37
  src/backlogops/jira_io_config.py
34
38
  src/backlogops/jira_order_releases.py
35
39
  src/backlogops/jira_rank_backlog.py
@@ -47,8 +51,10 @@ src/backlogops/jira_write_fields.py
47
51
  src/backlogops/jira_write_format.py
48
52
  src/backlogops/jira_write_releases.py
49
53
  src/backlogops/jira_write_status.py
54
+ src/backlogops/jira_write_time.py
50
55
  src/backlogops/jira_write_types.py
51
56
  src/backlogops/key_list_io.py
57
+ src/backlogops/level_defaults.py
52
58
  src/backlogops/levels.py
53
59
  src/backlogops/move_keys_first.py
54
60
  src/backlogops/name_list_io.py
@@ -56,9 +62,11 @@ src/backlogops/no_text_io.py
56
62
  src/backlogops/order_by_dependencies.py
57
63
  src/backlogops/person.py
58
64
  src/backlogops/py.typed
65
+ src/backlogops/ready_date_schedule.py
59
66
  src/backlogops/release_backlog_updates.py
60
67
  src/backlogops/release_change_io.py
61
68
  src/backlogops/releases.py
69
+ src/backlogops/remaining_time_config.py
62
70
  src/backlogops/rename_list_io.py
63
71
  src/backlogops/table_create.py
64
72
  src/backlogops/table_rows.py
@@ -0,0 +1,8 @@
1
+ config-as-json>=1.8
2
+ cryptography>=50.0.2
3
+ jira[cli,opt]>=3.10.5
4
+ tableio>=1.3
5
+ tableio-cfg-json>=2.0
6
+ wizard-ui-bridge[textual]>=1.5
7
+ versionreporter>=0.5
8
+ edit-cfg-json>=1.0.0
@@ -20,6 +20,7 @@ classifiers = [
20
20
  "Programming Language :: Python :: 3.12",
21
21
  "Programming Language :: Python :: 3.13",
22
22
  "Programming Language :: Python :: 3.14",
23
+ "Programming Language :: Python :: 3.15",
23
24
  "Operating System :: OS Independent",
24
25
  "Intended Audience :: Developers",
25
26
  "Topic :: Software Development :: Libraries :: Python Modules",
@@ -5,7 +5,7 @@ from setuptools import setup
5
5
 
6
6
  setup(
7
7
  name='backlogops',
8
- version='1.3',
8
+ version='1.5',
9
9
  description='Library with backlog operations.',
10
10
  author='Tom Björkholm',
11
11
  author_email='klausuler_linnet0q@icloud.com',
@@ -14,13 +14,13 @@ setup(
14
14
  package_dir={'backlogops': 'src/backlogops'},
15
15
  package_data={'backlogops': ['src/py.typed']},
16
16
  install_requires=[
17
- 'config-as-json >= 1.7',
18
- 'cryptography >= 50.0.1',
17
+ 'config-as-json >= 1.8',
18
+ 'cryptography >= 50.0.2',
19
19
  'jira[cli,opt] >= 3.10.5',
20
- 'tableio >= 1.1',
21
- 'tableio-cfg-json >= 1.4',
22
- 'wizard-ui-bridge[textual] >= 1.4',
23
- 'versionreporter >= 0.4',
24
- 'edit-cfg-json >= 0.3.0',
20
+ 'tableio >= 1.3',
21
+ 'tableio-cfg-json >= 2.0',
22
+ 'wizard-ui-bridge[textual] >= 1.5',
23
+ 'versionreporter >= 0.5',
24
+ 'edit-cfg-json >= 1.0.0',
25
25
  ]
26
26
  )