Feature/175 jira mining #243
Open
+1,793
−187
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ature/175-jira-mining
…erentiate between the return types of requests for issues and comments. Various different fixes
…ments of the issue and save the result in the db.
…nt information out of an issue.
…ed a bug in processing comments of issue that caused to not retrieve all comments.
…rt where issues are indexed, to lower number of api calls
indexing for Jira work
…rsisted and changed fields to persist of merge request.
…nged the value used in the "expired" field.
…and improved method to persist the description of an issue correctly.
…d the expired field in the versions.
… code synchronisation.
…a and added logs for debugging.
…od in new Promise and using then block in request method.
… Problem with executing the outer Promise.all().then block too early still exists
…issue from one application type (e.g only Gitlab, only Github).
…ct since they were not unique when multiple projects/VCS are used. Introduced unique identifiers for VCS.
…include the email to find best match for stakeholder.
… for persisted versions.
…lity to fetch information of "Team" fields if it is used
…o an issue. This information can be used as something like the assignees field in Gitlab/Github
… a team assigned to an issue.
…ort JQL expressions for fetching issues.
…hich can reduce the number of REST API requests if team member objects are already available.
…ed to persist only id of milestone/version instead of concatting project id with version id since version id is unique in whole instance.
…ince this is not covered by the updated field for an issue. Restructured code to execute only necessary requests and improved readability.
…xer to persist value when commits information linked to an issue have been last updated.
…d for testing purposes.
… various code improvements.
…populated to add support for Jira sites that are accessible with no auth.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR as a result of implementation for issue #175 Jira Mining.