Feature/175 jira mining #243

…de v20)

…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.

…instead of page.

…rt where issues are indexed, to lower number of api calls

… an issue

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

…D and changed to compare merge requests by last update date. Fixed eslint errors.

…ut all issues, merge requests, and versions being persisted and thus logging a wrong number of persisted/omitted issues.

…ional requests are needed to have information about all comments.

…ocessed. Using promise all to perform requests and operations concurrent.

… private.

…ged value of version expired field

…when description and comments are returned as plain strings by Rest API and fixed some wrongly used fields when persisting.

…e is empty.

…n issue, no value would be saved in DB and extracted code that creates the version object (to persist) into a separate method.

…itional to an array containing the users mentioned in the comment and made email and token in config optional.

…pent on issue and comments when submitting spent time.

…ynamically created methods.

…its of worklogs and added in issues search parameter to expand changelog.

…ation when time spent or time estimate on issue has been changed and changed assignee displayname key in object to name to provide functionality to retrieve value with existing frontend implementation.

…n were found linked in an issue.

… to not persist some fields at all.

…ccording to notes objects used in the project.

… object from Gitlab/Github.

…ce commit information linked to an issue is needed for the mentioned object persisted within an issue and changed various field keys and values.

…nts to types.

…o type mismatch between string and number type.

…lopment information.

…led pullrequest/commit information.

… version returns description as string.

…ons, removed some comments.

…cessChangelog method to return only 1 changelog item even if more items existed.

…hat's called.

…needed data already in correct format.

…a could not be fetched.

… in minutes instead of seconds and fixed a typo that led a regex to not match when time was subtracted.

…t versions that led to always include every milestone when defining a Sprint in the frontend.

…xed timeSpent and timeSpentSeconds field to contain correct values.

…les from snake case to camelCase.

…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.

…method.

…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.

Feature/175 jira mining #243

Are you sure you want to change the base?

Feature/175 jira mining #243

Commits on Nov 11, 2023

Commits on Nov 15, 2023

Commits on Nov 19, 2023

Commits on Nov 22, 2023

Commits on Nov 24, 2023

Commits on Dec 5, 2023

Commits on Dec 7, 2023

Commits on Jan 3, 2024

Commits on Jan 5, 2024

Commits on Jan 6, 2024

Commits on Jan 17, 2024

Commits on Jan 19, 2024

Commits on Jan 24, 2024

Commits on Jan 26, 2024

Commits on Jan 27, 2024

Commits on Jan 28, 2024

Commits on Feb 3, 2024

Commits on Feb 4, 2024

Commits on Feb 5, 2024

Commits on Feb 7, 2024

Commits on Feb 12, 2024

Commits on Feb 14, 2024

Commits on Feb 17, 2024

Commits on Feb 18, 2024

Commits on Feb 21, 2024

Commits on Feb 23, 2024

Commits on Feb 25, 2024

Commits on Apr 13, 2024

Commits on Apr 21, 2024

Commits on Apr 24, 2024

Commits on Apr 26, 2024

Commits on Apr 27, 2024

Commits on May 6, 2024

Commits on May 8, 2024

Commits on Jun 7, 2024

Commits on Jun 8, 2024