backlogops-gui 1.2__tar.gz → 1.4__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.
- {backlogops_gui-1.2 → backlogops_gui-1.4}/PKG-INFO +67 -16
- {backlogops_gui-1.2 → backlogops_gui-1.4}/README_pypi.md +62 -11
- {backlogops_gui-1.2 → backlogops_gui-1.4}/backlogops_gui.egg-info/PKG-INFO +67 -16
- backlogops_gui-1.4/backlogops_gui.egg-info/requires.txt +6 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/setup.py +5 -5
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/application.py +22 -12
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/backlog_actions.py +68 -12
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/backlog_io.py +7 -3
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/backlog_window.py +95 -51
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/format_dialogs.py +1 -1
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_dialogs.py +1 -1
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_rank.py +12 -10
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_update.py +13 -4
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_write.py +5 -1
- backlogops_gui-1.4/src/backlogops_gui/report_windows.py +85 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/table_view.py +45 -11
- backlogops_gui-1.2/backlogops_gui.egg-info/requires.txt +0 -6
- backlogops_gui-1.2/src/backlogops_gui/report_windows.py +0 -61
- {backlogops_gui-1.2 → backlogops_gui-1.4}/LICENSE.txt +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/backlogops_gui.egg-info/SOURCES.txt +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/backlogops_gui.egg-info/dependency_links.txt +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/backlogops_gui.egg-info/entry_points.txt +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/backlogops_gui.egg-info/top_level.txt +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/pyproject.toml +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/setup.cfg +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/__init__.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/__main__.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/_migrate_warn.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/backlog_dialogs.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/blog_version_reporter.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/choice_dialogs.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/config_edit.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/file_choosers.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_actions.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_base.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_order.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_read.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/jira_rename.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/key_list_box.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/log_buffer.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/modal_dialog.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/py.typed +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/python_version.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/tcltk_version.py +0 -0
- {backlogops_gui-1.2 → backlogops_gui-1.4}/src/backlogops_gui/token_dialog.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: backlogops-gui
|
|
3
|
-
Version: 1.
|
|
3
|
+
Version: 1.4
|
|
4
4
|
Summary: Graphical user interface for backlog operations.
|
|
5
5
|
Author: Tom Björkholm
|
|
6
6
|
Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
|
|
@@ -21,11 +21,11 @@ Classifier: Typing :: Typed
|
|
|
21
21
|
Requires-Python: >=3.12
|
|
22
22
|
Description-Content-Type: text/markdown
|
|
23
23
|
License-File: LICENSE.txt
|
|
24
|
-
Requires-Dist: backlogops>=1.
|
|
24
|
+
Requires-Dist: backlogops>=1.4
|
|
25
25
|
Requires-Dist: argcomplete>=3.7.2
|
|
26
|
-
Requires-Dist: wizard-ui-bridge>=1.
|
|
27
|
-
Requires-Dist: wizard-tk-bridge>=1.
|
|
28
|
-
Requires-Dist: edit-cfg-json-tk>=0.
|
|
26
|
+
Requires-Dist: wizard-ui-bridge>=1.4
|
|
27
|
+
Requires-Dist: wizard-tk-bridge>=1.4
|
|
28
|
+
Requires-Dist: edit-cfg-json-tk>=0.4.0
|
|
29
29
|
Requires-Dist: versionreporter>=0.4
|
|
30
30
|
Dynamic: author
|
|
31
31
|
Dynamic: license-file
|
|
@@ -75,6 +75,14 @@ The following functionality is available in all 3 packages:
|
|
|
75
75
|
- Estimate ready date for the backlog items based on available teams, team
|
|
76
76
|
velocity, vacation dates, periods with half time work, etc.
|
|
77
77
|
|
|
78
|
+
- Alternatively, where remaining time estimates are required, estimate ready
|
|
79
|
+
dates from the remaining time of the backlog items and the focus factor of the
|
|
80
|
+
teams (story points are recommended).
|
|
81
|
+
|
|
82
|
+
- Configure what a backlog item that nobody has estimated counts as, per backlog
|
|
83
|
+
item level, so that an unestimated item does not make the estimated dates too
|
|
84
|
+
optimistic.
|
|
85
|
+
|
|
78
86
|
- Extract backlog keys at given backlog item levels.
|
|
79
87
|
|
|
80
88
|
- Reorder the backlog so that the dependencies are satisfied.
|
|
@@ -99,6 +107,9 @@ The following functionality is available in all 3 packages:
|
|
|
99
107
|
|
|
100
108
|
- Rename columns when reading a file and when writing a file.
|
|
101
109
|
|
|
110
|
+
- Leave out columns that are empty on every row, when writing a file and when
|
|
111
|
+
showing the backlog in the GUI.
|
|
112
|
+
|
|
102
113
|
- Map custom status names in input files to backlog item statuses.
|
|
103
114
|
|
|
104
115
|
- Choose how backlog item levels are written: by number, by name, or both, and
|
|
@@ -109,7 +120,16 @@ The following functionality is available in all 3 packages:
|
|
|
109
120
|
- Migrate an older configuration or preset file to the current file format.
|
|
110
121
|
|
|
111
122
|
- A wizard to create a backlog-ops configuration file with the workforce, named
|
|
112
|
-
input and output presets, level names,
|
|
123
|
+
input and output presets, level names, status name mapping, the guess for
|
|
124
|
+
unestimated items, whether remaining time estimates are also used, how the
|
|
125
|
+
graphical user interface shows the data, and the Jira integration.
|
|
126
|
+
|
|
127
|
+
- An editor showing a whole configuration file or a stand-alone preset file at
|
|
128
|
+
once, folded where it is deep, to change a single value without stepping
|
|
129
|
+
through the wizard.
|
|
130
|
+
|
|
131
|
+
- Encrypt the Jira API token to a pass-phrase-protected file, so that no
|
|
132
|
+
configuration file holds the token in clear text.
|
|
113
133
|
|
|
114
134
|
- Read a backlog and releases from Jira into a backlog and release table.
|
|
115
135
|
|
|
@@ -128,6 +148,14 @@ The following functionality is available in all 3 packages:
|
|
|
128
148
|
- Move backlog items to a chosen anchor in the Jira rank order, following a key
|
|
129
149
|
list.
|
|
130
150
|
|
|
151
|
+
- Report what a Jira operation did not do. Every Jira result opens with what
|
|
152
|
+
Jira refused or what was skipped, so a value that was not written is visible
|
|
153
|
+
without reading the whole listing.
|
|
154
|
+
|
|
155
|
+
- Show the custom fields of Jira, the fields an issue's edit screen accepts, and
|
|
156
|
+
the raw JSON Jira holds for a field of an issue, to find the correct Jira
|
|
157
|
+
field mapping.
|
|
158
|
+
|
|
131
159
|
## The operating model
|
|
132
160
|
|
|
133
161
|
The operating model that most of the functionality is designed for is that the
|
|
@@ -136,8 +164,8 @@ are ordered by priority and dependencies to allow the teams to work in the
|
|
|
136
164
|
backlog order. Each backlog item and each release may have a planned ready date,
|
|
137
165
|
that records what has been communicated to the customer. Each backlog item and
|
|
138
166
|
each release may have an estimated ready date, that is calculated from the
|
|
139
|
-
current backlog state, the team velocity,
|
|
140
|
-
availability of the team members.
|
|
167
|
+
current backlog state, the team velocity (or, for remaining time estimates, the
|
|
168
|
+
focus factor), and what we know about the availability of the team members.
|
|
141
169
|
|
|
142
170
|
## The backlog item fields
|
|
143
171
|
|
|
@@ -152,7 +180,10 @@ the library:
|
|
|
152
180
|
|
|
153
181
|
- `title` The title of the backlog item. Required.
|
|
154
182
|
|
|
155
|
-
- `story_points` The story points of the backlog item.
|
|
183
|
+
- `story_points` The story points of the backlog item. Optional. An item with no
|
|
184
|
+
story points is one that nobody has estimated yet, and what such an item is
|
|
185
|
+
worked with when a completion date is estimated is configured. May be a
|
|
186
|
+
fraction, such as 0.5.
|
|
156
187
|
|
|
157
188
|
- `status` The status of the backlog item. Required.
|
|
158
189
|
|
|
@@ -169,7 +200,11 @@ the library:
|
|
|
169
200
|
|
|
170
201
|
- `team` The team responsible for the backlog item. Optional. Must not be empty
|
|
171
202
|
string. Must be a valid team name. If None the item can be done by any team.
|
|
172
|
-
If not None
|
|
203
|
+
If not None, the item can only be done by the specified team.
|
|
204
|
+
|
|
205
|
+
- `remaining_time` The remaining time of the backlog item, as ideal focused work
|
|
206
|
+
time of one person. Optional. Only used by the alternative remaining time
|
|
207
|
+
estimates; story points are recommended. Must not be negative.
|
|
173
208
|
|
|
174
209
|
- `depends_on_f2s` The list of keys of the backlog items that must have been
|
|
175
210
|
finished before the current item can start. May be empty.
|
|
@@ -209,7 +244,7 @@ pip install --upgrade backlogops-gui
|
|
|
209
244
|
|
|
210
245
|
For a better understanding of how to use the library, CLI or GUI, see the user
|
|
211
246
|
documentation:
|
|
212
|
-
[Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc
|
|
247
|
+
[Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/using_backlogops/README.md)
|
|
213
248
|
|
|
214
249
|
## API documentation
|
|
215
250
|
|
|
@@ -253,9 +288,11 @@ python -m backlogops_gui
|
|
|
253
288
|
python -m backlogops_gui -c config_file.cfg
|
|
254
289
|
````
|
|
255
290
|
|
|
256
|
-
At first startup you do not have any configuration file yet,
|
|
257
|
-
|
|
258
|
-
wizard.
|
|
291
|
+
At first startup you do not have any configuration file yet, so the
|
|
292
|
+
application shows a *No configuration* dialog offering to run the
|
|
293
|
+
configuration wizard, load an existing configuration file, or exit.
|
|
294
|
+
Cancelling the wizard or the file chooser returns to that dialog, so
|
|
295
|
+
the application starts only once a configuration is in place.
|
|
259
296
|
|
|
260
297
|
## Main window
|
|
261
298
|
|
|
@@ -323,6 +360,17 @@ is in the menus.
|
|
|
323
360
|
The backlog window shows 2 read-only tables: one with the backlog and
|
|
324
361
|
one with the list of releases. You will want to use the menus.
|
|
325
362
|
|
|
363
|
+
At the top of the window an information region records where the data
|
|
364
|
+
came from and when it was read, marks the window once you change the
|
|
365
|
+
backlog, and offers a **Read again** button that re-reads the same
|
|
366
|
+
source (the same file, or the same Jira preset and filter) in place. A
|
|
367
|
+
re-read with unsaved changes asks for confirmation first.
|
|
368
|
+
|
|
369
|
+
Each Jira action answers in a copy-pasteable pop-up that leads with what
|
|
370
|
+
did not happen: what Jira refused, then what was skipped, and last what
|
|
371
|
+
succeeded. When something was refused the pop-up title is marked
|
|
372
|
+
*NOT ALL SUCCEEDED*, so it is visible even behind another window.
|
|
373
|
+
|
|
326
374
|
- Backlog
|
|
327
375
|
|
|
328
376
|
- Order by keys...
|
|
@@ -333,6 +381,9 @@ one with the list of releases. You will want to use the menus.
|
|
|
333
381
|
|
|
334
382
|
- Estimate ready date...
|
|
335
383
|
|
|
384
|
+
- Estimate ready date from remaining time... (greyed out unless
|
|
385
|
+
remaining time estimates are enabled in the configuration)
|
|
386
|
+
|
|
336
387
|
- Set planned date from estimated
|
|
337
388
|
|
|
338
389
|
- Adjust release content...
|
|
@@ -365,10 +416,10 @@ one with the list of releases. You will want to use the menus.
|
|
|
365
416
|
|
|
366
417
|
## Test summary
|
|
367
418
|
|
|
368
|
-
- Test result:
|
|
419
|
+
- Test result: 2902 passed, 1 deselected in 68s (0:01:08)
|
|
369
420
|
- No flake8 warnings.
|
|
370
421
|
- No mypy errors found.
|
|
371
422
|
- No pylint warnings.
|
|
372
423
|
- No python layout warnings.
|
|
373
|
-
- Built version(s): 1.
|
|
424
|
+
- Built version(s): 1.4
|
|
374
425
|
- Build and test using Python 3.14.7
|
|
@@ -41,6 +41,14 @@ The following functionality is available in all 3 packages:
|
|
|
41
41
|
- Estimate ready date for the backlog items based on available teams, team
|
|
42
42
|
velocity, vacation dates, periods with half time work, etc.
|
|
43
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
|
+
|
|
48
|
+
- Configure what a backlog item that nobody has estimated counts as, per backlog
|
|
49
|
+
item level, so that an unestimated item does not make the estimated dates too
|
|
50
|
+
optimistic.
|
|
51
|
+
|
|
44
52
|
- Extract backlog keys at given backlog item levels.
|
|
45
53
|
|
|
46
54
|
- Reorder the backlog so that the dependencies are satisfied.
|
|
@@ -65,6 +73,9 @@ The following functionality is available in all 3 packages:
|
|
|
65
73
|
|
|
66
74
|
- Rename columns when reading a file and when writing a file.
|
|
67
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
|
+
|
|
68
79
|
- Map custom status names in input files to backlog item statuses.
|
|
69
80
|
|
|
70
81
|
- Choose how backlog item levels are written: by number, by name, or both, and
|
|
@@ -75,7 +86,16 @@ The following functionality is available in all 3 packages:
|
|
|
75
86
|
- Migrate an older configuration or preset file to the current file format.
|
|
76
87
|
|
|
77
88
|
- A wizard to create a backlog-ops configuration file with the workforce, named
|
|
78
|
-
input and output presets, level names,
|
|
89
|
+
input and output presets, level names, status name mapping, the guess for
|
|
90
|
+
unestimated items, whether remaining time estimates are also used, how the
|
|
91
|
+
graphical user interface shows the data, and the Jira integration.
|
|
92
|
+
|
|
93
|
+
- An editor showing a whole configuration file or a stand-alone preset file at
|
|
94
|
+
once, folded where it is deep, to change a single value without stepping
|
|
95
|
+
through the wizard.
|
|
96
|
+
|
|
97
|
+
- Encrypt the Jira API token to a pass-phrase-protected file, so that no
|
|
98
|
+
configuration file holds the token in clear text.
|
|
79
99
|
|
|
80
100
|
- Read a backlog and releases from Jira into a backlog and release table.
|
|
81
101
|
|
|
@@ -94,6 +114,14 @@ The following functionality is available in all 3 packages:
|
|
|
94
114
|
- Move backlog items to a chosen anchor in the Jira rank order, following a key
|
|
95
115
|
list.
|
|
96
116
|
|
|
117
|
+
- Report what a Jira operation did not do. Every Jira result opens with what
|
|
118
|
+
Jira refused or what was skipped, so a value that was not written is visible
|
|
119
|
+
without reading the whole listing.
|
|
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
|
+
|
|
97
125
|
## The operating model
|
|
98
126
|
|
|
99
127
|
The operating model that most of the functionality is designed for is that the
|
|
@@ -102,8 +130,8 @@ are ordered by priority and dependencies to allow the teams to work in the
|
|
|
102
130
|
backlog order. Each backlog item and each release may have a planned ready date,
|
|
103
131
|
that records what has been communicated to the customer. Each backlog item and
|
|
104
132
|
each release may have an estimated ready date, that is calculated from the
|
|
105
|
-
current backlog state, the team velocity,
|
|
106
|
-
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.
|
|
107
135
|
|
|
108
136
|
## The backlog item fields
|
|
109
137
|
|
|
@@ -118,7 +146,10 @@ the library:
|
|
|
118
146
|
|
|
119
147
|
- `title` The title of the backlog item. Required.
|
|
120
148
|
|
|
121
|
-
- `story_points` The story points of the backlog item.
|
|
149
|
+
- `story_points` The story points of the backlog item. Optional. An item with no
|
|
150
|
+
story points is one that nobody has estimated yet, and what such an item is
|
|
151
|
+
worked with when a completion date is estimated is configured. May be a
|
|
152
|
+
fraction, such as 0.5.
|
|
122
153
|
|
|
123
154
|
- `status` The status of the backlog item. Required.
|
|
124
155
|
|
|
@@ -135,7 +166,11 @@ the library:
|
|
|
135
166
|
|
|
136
167
|
- `team` The team responsible for the backlog item. Optional. Must not be empty
|
|
137
168
|
string. Must be a valid team name. If None the item can be done by any team.
|
|
138
|
-
If not None
|
|
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.
|
|
139
174
|
|
|
140
175
|
- `depends_on_f2s` The list of keys of the backlog items that must have been
|
|
141
176
|
finished before the current item can start. May be empty.
|
|
@@ -175,7 +210,7 @@ pip install --upgrade backlogops-gui
|
|
|
175
210
|
|
|
176
211
|
For a better understanding of how to use the library, CLI or GUI, see the user
|
|
177
212
|
documentation:
|
|
178
|
-
[Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc
|
|
213
|
+
[Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/using_backlogops/README.md)
|
|
179
214
|
|
|
180
215
|
## API documentation
|
|
181
216
|
|
|
@@ -219,9 +254,11 @@ python -m backlogops_gui
|
|
|
219
254
|
python -m backlogops_gui -c config_file.cfg
|
|
220
255
|
````
|
|
221
256
|
|
|
222
|
-
At first startup you do not have any configuration file yet,
|
|
223
|
-
|
|
224
|
-
wizard.
|
|
257
|
+
At first startup you do not have any configuration file yet, so the
|
|
258
|
+
application shows a *No configuration* dialog offering to run the
|
|
259
|
+
configuration wizard, load an existing configuration file, or exit.
|
|
260
|
+
Cancelling the wizard or the file chooser returns to that dialog, so
|
|
261
|
+
the application starts only once a configuration is in place.
|
|
225
262
|
|
|
226
263
|
## Main window
|
|
227
264
|
|
|
@@ -289,6 +326,17 @@ is in the menus.
|
|
|
289
326
|
The backlog window shows 2 read-only tables: one with the backlog and
|
|
290
327
|
one with the list of releases. You will want to use the menus.
|
|
291
328
|
|
|
329
|
+
At the top of the window an information region records where the data
|
|
330
|
+
came from and when it was read, marks the window once you change the
|
|
331
|
+
backlog, and offers a **Read again** button that re-reads the same
|
|
332
|
+
source (the same file, or the same Jira preset and filter) in place. A
|
|
333
|
+
re-read with unsaved changes asks for confirmation first.
|
|
334
|
+
|
|
335
|
+
Each Jira action answers in a copy-pasteable pop-up that leads with what
|
|
336
|
+
did not happen: what Jira refused, then what was skipped, and last what
|
|
337
|
+
succeeded. When something was refused the pop-up title is marked
|
|
338
|
+
*NOT ALL SUCCEEDED*, so it is visible even behind another window.
|
|
339
|
+
|
|
292
340
|
- Backlog
|
|
293
341
|
|
|
294
342
|
- Order by keys...
|
|
@@ -299,6 +347,9 @@ one with the list of releases. You will want to use the menus.
|
|
|
299
347
|
|
|
300
348
|
- Estimate ready date...
|
|
301
349
|
|
|
350
|
+
- Estimate ready date from remaining time... (greyed out unless
|
|
351
|
+
remaining time estimates are enabled in the configuration)
|
|
352
|
+
|
|
302
353
|
- Set planned date from estimated
|
|
303
354
|
|
|
304
355
|
- Adjust release content...
|
|
@@ -331,10 +382,10 @@ one with the list of releases. You will want to use the menus.
|
|
|
331
382
|
|
|
332
383
|
## Test summary
|
|
333
384
|
|
|
334
|
-
- Test result:
|
|
385
|
+
- Test result: 2902 passed, 1 deselected in 68s (0:01:08)
|
|
335
386
|
- No flake8 warnings.
|
|
336
387
|
- No mypy errors found.
|
|
337
388
|
- No pylint warnings.
|
|
338
389
|
- No python layout warnings.
|
|
339
|
-
- Built version(s): 1.
|
|
390
|
+
- Built version(s): 1.4
|
|
340
391
|
- Build and test using Python 3.14.7
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.4
|
|
2
2
|
Name: backlogops-gui
|
|
3
|
-
Version: 1.
|
|
3
|
+
Version: 1.4
|
|
4
4
|
Summary: Graphical user interface for backlog operations.
|
|
5
5
|
Author: Tom Björkholm
|
|
6
6
|
Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
|
|
@@ -21,11 +21,11 @@ Classifier: Typing :: Typed
|
|
|
21
21
|
Requires-Python: >=3.12
|
|
22
22
|
Description-Content-Type: text/markdown
|
|
23
23
|
License-File: LICENSE.txt
|
|
24
|
-
Requires-Dist: backlogops>=1.
|
|
24
|
+
Requires-Dist: backlogops>=1.4
|
|
25
25
|
Requires-Dist: argcomplete>=3.7.2
|
|
26
|
-
Requires-Dist: wizard-ui-bridge>=1.
|
|
27
|
-
Requires-Dist: wizard-tk-bridge>=1.
|
|
28
|
-
Requires-Dist: edit-cfg-json-tk>=0.
|
|
26
|
+
Requires-Dist: wizard-ui-bridge>=1.4
|
|
27
|
+
Requires-Dist: wizard-tk-bridge>=1.4
|
|
28
|
+
Requires-Dist: edit-cfg-json-tk>=0.4.0
|
|
29
29
|
Requires-Dist: versionreporter>=0.4
|
|
30
30
|
Dynamic: author
|
|
31
31
|
Dynamic: license-file
|
|
@@ -75,6 +75,14 @@ The following functionality is available in all 3 packages:
|
|
|
75
75
|
- Estimate ready date for the backlog items based on available teams, team
|
|
76
76
|
velocity, vacation dates, periods with half time work, etc.
|
|
77
77
|
|
|
78
|
+
- Alternatively, where remaining time estimates are required, estimate ready
|
|
79
|
+
dates from the remaining time of the backlog items and the focus factor of the
|
|
80
|
+
teams (story points are recommended).
|
|
81
|
+
|
|
82
|
+
- Configure what a backlog item that nobody has estimated counts as, per backlog
|
|
83
|
+
item level, so that an unestimated item does not make the estimated dates too
|
|
84
|
+
optimistic.
|
|
85
|
+
|
|
78
86
|
- Extract backlog keys at given backlog item levels.
|
|
79
87
|
|
|
80
88
|
- Reorder the backlog so that the dependencies are satisfied.
|
|
@@ -99,6 +107,9 @@ The following functionality is available in all 3 packages:
|
|
|
99
107
|
|
|
100
108
|
- Rename columns when reading a file and when writing a file.
|
|
101
109
|
|
|
110
|
+
- Leave out columns that are empty on every row, when writing a file and when
|
|
111
|
+
showing the backlog in the GUI.
|
|
112
|
+
|
|
102
113
|
- Map custom status names in input files to backlog item statuses.
|
|
103
114
|
|
|
104
115
|
- Choose how backlog item levels are written: by number, by name, or both, and
|
|
@@ -109,7 +120,16 @@ The following functionality is available in all 3 packages:
|
|
|
109
120
|
- Migrate an older configuration or preset file to the current file format.
|
|
110
121
|
|
|
111
122
|
- A wizard to create a backlog-ops configuration file with the workforce, named
|
|
112
|
-
input and output presets, level names,
|
|
123
|
+
input and output presets, level names, status name mapping, the guess for
|
|
124
|
+
unestimated items, whether remaining time estimates are also used, how the
|
|
125
|
+
graphical user interface shows the data, and the Jira integration.
|
|
126
|
+
|
|
127
|
+
- An editor showing a whole configuration file or a stand-alone preset file at
|
|
128
|
+
once, folded where it is deep, to change a single value without stepping
|
|
129
|
+
through the wizard.
|
|
130
|
+
|
|
131
|
+
- Encrypt the Jira API token to a pass-phrase-protected file, so that no
|
|
132
|
+
configuration file holds the token in clear text.
|
|
113
133
|
|
|
114
134
|
- Read a backlog and releases from Jira into a backlog and release table.
|
|
115
135
|
|
|
@@ -128,6 +148,14 @@ The following functionality is available in all 3 packages:
|
|
|
128
148
|
- Move backlog items to a chosen anchor in the Jira rank order, following a key
|
|
129
149
|
list.
|
|
130
150
|
|
|
151
|
+
- Report what a Jira operation did not do. Every Jira result opens with what
|
|
152
|
+
Jira refused or what was skipped, so a value that was not written is visible
|
|
153
|
+
without reading the whole listing.
|
|
154
|
+
|
|
155
|
+
- Show the custom fields of Jira, the fields an issue's edit screen accepts, and
|
|
156
|
+
the raw JSON Jira holds for a field of an issue, to find the correct Jira
|
|
157
|
+
field mapping.
|
|
158
|
+
|
|
131
159
|
## The operating model
|
|
132
160
|
|
|
133
161
|
The operating model that most of the functionality is designed for is that the
|
|
@@ -136,8 +164,8 @@ are ordered by priority and dependencies to allow the teams to work in the
|
|
|
136
164
|
backlog order. Each backlog item and each release may have a planned ready date,
|
|
137
165
|
that records what has been communicated to the customer. Each backlog item and
|
|
138
166
|
each release may have an estimated ready date, that is calculated from the
|
|
139
|
-
current backlog state, the team velocity,
|
|
140
|
-
availability of the team members.
|
|
167
|
+
current backlog state, the team velocity (or, for remaining time estimates, the
|
|
168
|
+
focus factor), and what we know about the availability of the team members.
|
|
141
169
|
|
|
142
170
|
## The backlog item fields
|
|
143
171
|
|
|
@@ -152,7 +180,10 @@ the library:
|
|
|
152
180
|
|
|
153
181
|
- `title` The title of the backlog item. Required.
|
|
154
182
|
|
|
155
|
-
- `story_points` The story points of the backlog item.
|
|
183
|
+
- `story_points` The story points of the backlog item. Optional. An item with no
|
|
184
|
+
story points is one that nobody has estimated yet, and what such an item is
|
|
185
|
+
worked with when a completion date is estimated is configured. May be a
|
|
186
|
+
fraction, such as 0.5.
|
|
156
187
|
|
|
157
188
|
- `status` The status of the backlog item. Required.
|
|
158
189
|
|
|
@@ -169,7 +200,11 @@ the library:
|
|
|
169
200
|
|
|
170
201
|
- `team` The team responsible for the backlog item. Optional. Must not be empty
|
|
171
202
|
string. Must be a valid team name. If None the item can be done by any team.
|
|
172
|
-
If not None
|
|
203
|
+
If not None, the item can only be done by the specified team.
|
|
204
|
+
|
|
205
|
+
- `remaining_time` The remaining time of the backlog item, as ideal focused work
|
|
206
|
+
time of one person. Optional. Only used by the alternative remaining time
|
|
207
|
+
estimates; story points are recommended. Must not be negative.
|
|
173
208
|
|
|
174
209
|
- `depends_on_f2s` The list of keys of the backlog items that must have been
|
|
175
210
|
finished before the current item can start. May be empty.
|
|
@@ -209,7 +244,7 @@ pip install --upgrade backlogops-gui
|
|
|
209
244
|
|
|
210
245
|
For a better understanding of how to use the library, CLI or GUI, see the user
|
|
211
246
|
documentation:
|
|
212
|
-
[Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc
|
|
247
|
+
[Using backlogops](https://github.com/tom-bjorkholm/backlog-ops/blob/master/doc/using_backlogops/README.md)
|
|
213
248
|
|
|
214
249
|
## API documentation
|
|
215
250
|
|
|
@@ -253,9 +288,11 @@ python -m backlogops_gui
|
|
|
253
288
|
python -m backlogops_gui -c config_file.cfg
|
|
254
289
|
````
|
|
255
290
|
|
|
256
|
-
At first startup you do not have any configuration file yet,
|
|
257
|
-
|
|
258
|
-
wizard.
|
|
291
|
+
At first startup you do not have any configuration file yet, so the
|
|
292
|
+
application shows a *No configuration* dialog offering to run the
|
|
293
|
+
configuration wizard, load an existing configuration file, or exit.
|
|
294
|
+
Cancelling the wizard or the file chooser returns to that dialog, so
|
|
295
|
+
the application starts only once a configuration is in place.
|
|
259
296
|
|
|
260
297
|
## Main window
|
|
261
298
|
|
|
@@ -323,6 +360,17 @@ is in the menus.
|
|
|
323
360
|
The backlog window shows 2 read-only tables: one with the backlog and
|
|
324
361
|
one with the list of releases. You will want to use the menus.
|
|
325
362
|
|
|
363
|
+
At the top of the window an information region records where the data
|
|
364
|
+
came from and when it was read, marks the window once you change the
|
|
365
|
+
backlog, and offers a **Read again** button that re-reads the same
|
|
366
|
+
source (the same file, or the same Jira preset and filter) in place. A
|
|
367
|
+
re-read with unsaved changes asks for confirmation first.
|
|
368
|
+
|
|
369
|
+
Each Jira action answers in a copy-pasteable pop-up that leads with what
|
|
370
|
+
did not happen: what Jira refused, then what was skipped, and last what
|
|
371
|
+
succeeded. When something was refused the pop-up title is marked
|
|
372
|
+
*NOT ALL SUCCEEDED*, so it is visible even behind another window.
|
|
373
|
+
|
|
326
374
|
- Backlog
|
|
327
375
|
|
|
328
376
|
- Order by keys...
|
|
@@ -333,6 +381,9 @@ one with the list of releases. You will want to use the menus.
|
|
|
333
381
|
|
|
334
382
|
- Estimate ready date...
|
|
335
383
|
|
|
384
|
+
- Estimate ready date from remaining time... (greyed out unless
|
|
385
|
+
remaining time estimates are enabled in the configuration)
|
|
386
|
+
|
|
336
387
|
- Set planned date from estimated
|
|
337
388
|
|
|
338
389
|
- Adjust release content...
|
|
@@ -365,10 +416,10 @@ one with the list of releases. You will want to use the menus.
|
|
|
365
416
|
|
|
366
417
|
## Test summary
|
|
367
418
|
|
|
368
|
-
- Test result:
|
|
419
|
+
- Test result: 2902 passed, 1 deselected in 68s (0:01:08)
|
|
369
420
|
- No flake8 warnings.
|
|
370
421
|
- No mypy errors found.
|
|
371
422
|
- No pylint warnings.
|
|
372
423
|
- No python layout warnings.
|
|
373
|
-
- Built version(s): 1.
|
|
424
|
+
- Built version(s): 1.4
|
|
374
425
|
- Build and test using Python 3.14.7
|
|
@@ -5,7 +5,7 @@ from setuptools import setup
|
|
|
5
5
|
|
|
6
6
|
setup(
|
|
7
7
|
name='backlogops-gui',
|
|
8
|
-
version='1.
|
|
8
|
+
version='1.4',
|
|
9
9
|
description='Graphical user interface for backlog operations.',
|
|
10
10
|
author='Tom Björkholm',
|
|
11
11
|
author_email='klausuler_linnet0q@icloud.com',
|
|
@@ -19,11 +19,11 @@ setup(
|
|
|
19
19
|
]
|
|
20
20
|
},
|
|
21
21
|
install_requires=[
|
|
22
|
-
'backlogops >= 1.
|
|
22
|
+
'backlogops >= 1.4',
|
|
23
23
|
'argcomplete >= 3.7.2',
|
|
24
|
-
'wizard-ui-bridge >= 1.
|
|
25
|
-
'wizard-tk-bridge >= 1.
|
|
26
|
-
'edit-cfg-json-tk >= 0.
|
|
24
|
+
'wizard-ui-bridge >= 1.4',
|
|
25
|
+
'wizard-tk-bridge >= 1.4',
|
|
26
|
+
'edit-cfg-json-tk >= 0.4.0',
|
|
27
27
|
'versionreporter >= 0.4'
|
|
28
28
|
]
|
|
29
29
|
)
|
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
|
|
4
4
|
The application opens a main window whose menu reads a backlog from a file
|
|
5
5
|
or from Jira, loads or replaces the active configuration from a file, runs
|
|
6
|
-
the
|
|
6
|
+
the backlog-ops configuration wizard, edits a configuration or a stand-alone
|
|
7
7
|
preset file in the folding editor of
|
|
8
8
|
:mod:`backlogops_gui.config_edit`, creates a stand-alone input or output
|
|
9
9
|
preset file, migrates a stand-alone preset file to the current format,
|
|
@@ -17,14 +17,13 @@ modified, and offers a "Read again" button that re-reads the same source.
|
|
|
17
17
|
On macOS the menu bar sits at the top of the display rather than in
|
|
18
18
|
the window, so the main window body shows a short description, the current
|
|
19
19
|
configuration status, and a log of the most recent diagnostic messages, to
|
|
20
|
-
make clear that the application is running. The
|
|
21
|
-
taken from the file given with ``-c`` or from the configured locations;
|
|
20
|
+
make clear that the application is running. The backlog-ops configuration
|
|
21
|
+
is taken from the file given with ``-c`` or from the configured locations;
|
|
22
22
|
when no configuration is found a startup dialog offers to run the wizard,
|
|
23
23
|
load a configuration file, or exit. Cancelling the wizard or a dialog
|
|
24
24
|
returns to that choice, so the application ends only when the user exits.
|
|
25
25
|
The Jira menu actions of a backlog window are delegated to the collaborator
|
|
26
|
-
objects in :mod:`backlogops_gui.
|
|
27
|
-
and :mod:`backlogops_gui.jira_update`.
|
|
26
|
+
objects grouped in :mod:`backlogops_gui.jira_actions`.
|
|
28
27
|
"""
|
|
29
28
|
|
|
30
29
|
# PYTHON_ARGCOMPLETE_OK
|
|
@@ -44,8 +43,10 @@ from config_as_json.file_extension import fix_file_extension
|
|
|
44
43
|
from wizard_tk_bridge import WizardUiBridgeTk
|
|
45
44
|
from backlogops import (
|
|
46
45
|
AvailableTeams, BacklogOpsConfig, BacklogReleases, CONFIG_EXTENSION,
|
|
47
|
-
|
|
48
|
-
|
|
46
|
+
DefaultStoryPoints,
|
|
47
|
+
GuiDisplayConfig, InputFormatConfig, Levels, OutputFormatConfig,
|
|
48
|
+
RemainingTimeConfig, Status, get_demo_backlog, get_backlog_ops_config,
|
|
49
|
+
backlog_ops_wizard,
|
|
49
50
|
preset_wizard, read_backlog_ops_config, read_io_preset, safe_write_config,
|
|
50
51
|
encrypt_token_file, encrypt_token_to_file)
|
|
51
52
|
from backlogops_gui.backlog_io import read_backlog
|
|
@@ -74,8 +75,8 @@ LOG_REFRESH_MS = 800
|
|
|
74
75
|
HEADING_FONT = ('TkDefaultFont', 14, 'bold')
|
|
75
76
|
INSTRUCTIONS = (
|
|
76
77
|
'Use the menus to read a backlog from a file or from Jira, load a '
|
|
77
|
-
'configuration file, run the
|
|
78
|
-
'preset file, create a stand-alone input or output preset file, '
|
|
78
|
+
'configuration file, run the configuration wizard, edit a configuration '
|
|
79
|
+
'or a preset file, create a stand-alone input or output preset file, '
|
|
79
80
|
'migrate a preset file to the current format, write the current '
|
|
80
81
|
'configuration to a file, or create a demonstration backlog. Each '
|
|
81
82
|
'backlog opens in its own window. On macOS the menu bar is at the top '
|
|
@@ -198,12 +199,20 @@ class BacklogApp:
|
|
|
198
199
|
"""Return the configured backlog item levels, or None when absent."""
|
|
199
200
|
return self.config.get_levels() if self.config else None
|
|
200
201
|
|
|
202
|
+
def def_points(self) -> Optional[DefaultStoryPoints]:
|
|
203
|
+
"""Return what an unestimated item is worked with, or None."""
|
|
204
|
+
return self.config.default_story_points if self.config else None
|
|
205
|
+
|
|
206
|
+
def rt_config(self) -> Optional[RemainingTimeConfig]:
|
|
207
|
+
"""Return the remaining time configuration, or None when absent."""
|
|
208
|
+
return self.config.remaining_time if self.config else None
|
|
209
|
+
|
|
201
210
|
def status_map(self) -> Optional[dict[str, Status]]:
|
|
202
211
|
"""Return the library-wide status input map, or None when absent."""
|
|
203
212
|
return self.config.get_status_input_map() if self.config else None
|
|
204
213
|
|
|
205
214
|
def gui_display(self) -> GuiDisplayConfig:
|
|
206
|
-
"""Return the GUI display configuration (
|
|
215
|
+
"""Return the GUI display configuration (levels, omission, maps)."""
|
|
207
216
|
if self.config is None:
|
|
208
217
|
return GuiDisplayConfig()
|
|
209
218
|
return self.config.gui_display
|
|
@@ -614,8 +623,9 @@ class BacklogApp:
|
|
|
614
623
|
rename_releases=self.jira.renamer.rename_action())
|
|
615
624
|
BacklogWindow(self.root, data, title, self.out_presets,
|
|
616
625
|
self.available_teams, self.log, self.levels,
|
|
617
|
-
self.gui_display, warning, handlers,
|
|
618
|
-
|
|
626
|
+
self.gui_display, warning, handlers,
|
|
627
|
+
def_points=self.def_points, rt_config=self.rt_config,
|
|
628
|
+
source=source, reload=reload)
|
|
619
629
|
|
|
620
630
|
def report_versions(self) -> None:
|
|
621
631
|
"""Report version information into the log on a worker thread.
|