Improve retrieval of JIRA issues #334
Assignees
Comments
copernico
pushed a commit
that referenced
this issue
Nov 3, 2022
- Implemented twin commits, closes #147 - Using basemodel again (pydantic) - Fixed the logger, improved log aesthetics and readability - github and jira issues are collected using their respective APIs (GITHUB token required via .env file) - Better word extraction and filtering based on tests conducted on the small dataset. - Report handlers now create nested folders - updated to python 3.10 - skip GitHub when fetching references - refactored git and raw_commit modules: all commit IDs, timestamp, parent, message and changed files are collected with a single call to git executable - refactored logging - Fixes: #339 #341 #334 #331 #326 #336
|
Closed by #342 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While the retrieval of JSON is forbidden by most (all?) Apache projects, the XML format seems available.
Example:
https://issues.apache.org/jira/si/jira.issueviews:issue-xml/ZOOKEEPER-4557/ZOOKEEPER-4557.xml
Interesting: one can restrict the fields contained in the XML response, by appending
field=key&field=summary&field=.....Maybe this may make it simpler to also reason about "related" (e.g. duplicate) issues.
The text was updated successfully, but these errors were encountered: