1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
|
%global _empty_manifest_terminate_build 0
Name: python-agile-analytics
Version: 0.15.2
Release: 1
Summary: Pulls data from agile systems and analyzes it.
License: MIT License
URL: https://github.com/cmheisel/agile-analytics
Source0: https://mirrors.aliyun.com/pypi/web/packages/90/41/6e0bcd3bae9f0680bed97247754364ba23525d9165b41b288142deb7ff0a/agile-analytics-0.15.2.tar.gz
BuildArch: noarch
%description
# jira-agile-extractor
[](https://travis-ci.org/cmheisel/agile-analytics)
[](https://coveralls.io/github/cmheisel/agile-analytics?branch=master)
[](http://waffle.io/cmheisel/agile-analytics)
Extract data about items from JIRA, output raw data and interesting reports
## Architecture
The agile extractor is composed of several different components. Fetchers gather data, which is fed to one or more analyzer/reporters/writer combos.
### Components
#### Fetchers
Fetchers are responsible for getting raw data about tickets from agile data sources (JIRA, Trello, etc.)
They depend on fetcher specific configuration including things like API end points, credentials and search criteria.
They produce a set of AgileTicket objects with a known interface.
#### Analyzers
Analyzers take in a set of AgileTicket objects and an analysis configuration and return a set of AnalyzedTicket objects that contain the original AgileTicket as well as additional data calculated in light of the analysis context.
For example, a CycleTime analyzer would look for a start_state and an end_state in the configuration, and calculate the days between those and store it as cycle_time on the AnalyzedTicket object.
#### Reporters
Reporters take in a set of AnalyzedTicket objects and a report configuration and return a Report object. It has two standard attributes:
* Table - A representation of the report as a 2 dimensional table, provides column headers, row labels, and values for each row/column combo
* Summary - A key/value store of report specific data
#### Writers
Writers take in a Report and a WriterConfig can write it out a particular source. Examples:
* CSV to standout
* CSV to a file
* Google spreadsheet
* Plotly
### Diagram
```
+-----------> Reporter: Distribution
| title=Cycle Time Distribution
| start_date=1/1/2015
| end_date=3/31/2015
| field=cycle_time
|
+-----------> Reporter: Throughput
| title=Weekly Throughput
| start_date=1/1/2015
| end_date=3/31/2015
| period=weekly
|
|
|
+-----------------> Analyzer: Cycle Time +
| start_state=Backlog
| end_state=Deployed
| issue_types=Story
|
Fetcher | +-----------> Reporter: Throughput
source=JIRA +----------------> Analyzer: Defect + title=Escaped Defects
filter=1111 | defect_types=Bug,Incident start_date=1/1/2015
auth=user,pass | end_date=3/31/2015
|
|
+----------------> Analyzer: Cycle Time +-----------> Reporter: Throughput
start_state=Analysis title=Weekly Analysis Throughput
end_state=Dev start_date=1/1/2015
end_date=3/31/2015
period=weekly
```
%package -n python3-agile-analytics
Summary: Pulls data from agile systems and analyzes it.
Provides: python-agile-analytics
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-agile-analytics
# jira-agile-extractor
[](https://travis-ci.org/cmheisel/agile-analytics)
[](https://coveralls.io/github/cmheisel/agile-analytics?branch=master)
[](http://waffle.io/cmheisel/agile-analytics)
Extract data about items from JIRA, output raw data and interesting reports
## Architecture
The agile extractor is composed of several different components. Fetchers gather data, which is fed to one or more analyzer/reporters/writer combos.
### Components
#### Fetchers
Fetchers are responsible for getting raw data about tickets from agile data sources (JIRA, Trello, etc.)
They depend on fetcher specific configuration including things like API end points, credentials and search criteria.
They produce a set of AgileTicket objects with a known interface.
#### Analyzers
Analyzers take in a set of AgileTicket objects and an analysis configuration and return a set of AnalyzedTicket objects that contain the original AgileTicket as well as additional data calculated in light of the analysis context.
For example, a CycleTime analyzer would look for a start_state and an end_state in the configuration, and calculate the days between those and store it as cycle_time on the AnalyzedTicket object.
#### Reporters
Reporters take in a set of AnalyzedTicket objects and a report configuration and return a Report object. It has two standard attributes:
* Table - A representation of the report as a 2 dimensional table, provides column headers, row labels, and values for each row/column combo
* Summary - A key/value store of report specific data
#### Writers
Writers take in a Report and a WriterConfig can write it out a particular source. Examples:
* CSV to standout
* CSV to a file
* Google spreadsheet
* Plotly
### Diagram
```
+-----------> Reporter: Distribution
| title=Cycle Time Distribution
| start_date=1/1/2015
| end_date=3/31/2015
| field=cycle_time
|
+-----------> Reporter: Throughput
| title=Weekly Throughput
| start_date=1/1/2015
| end_date=3/31/2015
| period=weekly
|
|
|
+-----------------> Analyzer: Cycle Time +
| start_state=Backlog
| end_state=Deployed
| issue_types=Story
|
Fetcher | +-----------> Reporter: Throughput
source=JIRA +----------------> Analyzer: Defect + title=Escaped Defects
filter=1111 | defect_types=Bug,Incident start_date=1/1/2015
auth=user,pass | end_date=3/31/2015
|
|
+----------------> Analyzer: Cycle Time +-----------> Reporter: Throughput
start_state=Analysis title=Weekly Analysis Throughput
end_state=Dev start_date=1/1/2015
end_date=3/31/2015
period=weekly
```
%package help
Summary: Development documents and examples for agile-analytics
Provides: python3-agile-analytics-doc
%description help
# jira-agile-extractor
[](https://travis-ci.org/cmheisel/agile-analytics)
[](https://coveralls.io/github/cmheisel/agile-analytics?branch=master)
[](http://waffle.io/cmheisel/agile-analytics)
Extract data about items from JIRA, output raw data and interesting reports
## Architecture
The agile extractor is composed of several different components. Fetchers gather data, which is fed to one or more analyzer/reporters/writer combos.
### Components
#### Fetchers
Fetchers are responsible for getting raw data about tickets from agile data sources (JIRA, Trello, etc.)
They depend on fetcher specific configuration including things like API end points, credentials and search criteria.
They produce a set of AgileTicket objects with a known interface.
#### Analyzers
Analyzers take in a set of AgileTicket objects and an analysis configuration and return a set of AnalyzedTicket objects that contain the original AgileTicket as well as additional data calculated in light of the analysis context.
For example, a CycleTime analyzer would look for a start_state and an end_state in the configuration, and calculate the days between those and store it as cycle_time on the AnalyzedTicket object.
#### Reporters
Reporters take in a set of AnalyzedTicket objects and a report configuration and return a Report object. It has two standard attributes:
* Table - A representation of the report as a 2 dimensional table, provides column headers, row labels, and values for each row/column combo
* Summary - A key/value store of report specific data
#### Writers
Writers take in a Report and a WriterConfig can write it out a particular source. Examples:
* CSV to standout
* CSV to a file
* Google spreadsheet
* Plotly
### Diagram
```
+-----------> Reporter: Distribution
| title=Cycle Time Distribution
| start_date=1/1/2015
| end_date=3/31/2015
| field=cycle_time
|
+-----------> Reporter: Throughput
| title=Weekly Throughput
| start_date=1/1/2015
| end_date=3/31/2015
| period=weekly
|
|
|
+-----------------> Analyzer: Cycle Time +
| start_state=Backlog
| end_state=Deployed
| issue_types=Story
|
Fetcher | +-----------> Reporter: Throughput
source=JIRA +----------------> Analyzer: Defect + title=Escaped Defects
filter=1111 | defect_types=Bug,Incident start_date=1/1/2015
auth=user,pass | end_date=3/31/2015
|
|
+----------------> Analyzer: Cycle Time +-----------> Reporter: Throughput
start_state=Analysis title=Weekly Analysis Throughput
end_state=Dev start_date=1/1/2015
end_date=3/31/2015
period=weekly
```
%prep
%autosetup -n agile-analytics-0.15.2
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-agile-analytics -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.15.2-1
- Package Spec generated
|
