Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jira Mining #175

Open
uberroot4 opened this issue Nov 2, 2023 · 1 comment
Open

Jira Mining #175

uberroot4 opened this issue Nov 2, 2023 · 1 comment
Assignees
Labels
addition bsc enhancement New feature or request

Comments

@uberroot4
Copy link
Member

No description provided.

@uberroot4 uberroot4 added enhancement New feature or request addition bsc labels Nov 2, 2023
@uberroot4 uberroot4 assigned uberroot4 and martan001 and unassigned uberroot4 Nov 2, 2023
martan001 added a commit that referenced this issue Jan 24, 2024
…ut all issues, merge requests, and versions being persisted and thus logging a wrong number of persisted/omitted issues.
martan001 added a commit that referenced this issue Jan 27, 2024
…ional requests are needed to have information about all comments.
martan001 added a commit that referenced this issue Jan 27, 2024
…ocessed. Using promise all to perform requests and operations concurrent.
martan001 added a commit that referenced this issue Jan 27, 2024
martan001 added a commit that referenced this issue Jan 27, 2024
…when description and comments are returned as plain strings by Rest API and fixed some wrongly used fields when persisting.
martan001 added a commit that referenced this issue Jan 28, 2024
…n issue, no value would be saved in DB and extracted code that creates the version object (to persist) into a separate method.
martan001 added a commit that referenced this issue Feb 4, 2024
…itional to an array containing the users mentioned in the comment and made email and token in config optional.
martan001 added a commit that referenced this issue Feb 4, 2024
…pent on issue and comments when submitting spent time.
martan001 added a commit that referenced this issue Feb 4, 2024
martan001 added a commit that referenced this issue Feb 4, 2024
…its of worklogs and added in issues search parameter to expand changelog.
martan001 added a commit that referenced this issue Feb 4, 2024
…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.
martan001 added a commit that referenced this issue Feb 4, 2024
martan001 added a commit that referenced this issue Feb 4, 2024
martan001 added a commit that referenced this issue Feb 7, 2024
martan001 added a commit that referenced this issue Feb 7, 2024
…ccording to notes objects used in the project.
martan001 added a commit that referenced this issue Feb 7, 2024
martan001 added a commit that referenced this issue Feb 7, 2024
…ce commit information linked to an issue is needed for the mentioned object persisted within an issue and changed various field keys and values.
martan001 added a commit that referenced this issue Feb 21, 2024
martan001 added a commit that referenced this issue Feb 21, 2024
martan001 added a commit that referenced this issue Feb 21, 2024
…issue from one application type (e.g only Gitlab, only Github).
martan001 added a commit that referenced this issue Feb 21, 2024
martan001 added a commit that referenced this issue Feb 24, 2024
…ct since they were not unique when multiple projects/VCS are used. Introduced unique identifiers for VCS.
martan001 added a commit that referenced this issue Feb 24, 2024
…include the email to find best match for stakeholder.
martan001 added a commit that referenced this issue Feb 26, 2024
martan001 added a commit that referenced this issue Apr 13, 2024
…lity to fetch information of "Team" fields if it is used
martan001 added a commit that referenced this issue Apr 13, 2024
…o an issue. This information can be used as something like the assignees field in Gitlab/Github
martan001 added a commit that referenced this issue Apr 13, 2024
martan001 added a commit that referenced this issue Apr 24, 2024
martan001 added a commit that referenced this issue Apr 24, 2024
martan001 added a commit that referenced this issue Apr 27, 2024
…hich can reduce the number of REST API requests if team member objects are already available.
martan001 added a commit that referenced this issue May 6, 2024
…ed to persist only id of milestone/version instead of concatting project id with version id since version id is unique in whole instance.
martan001 added a commit that referenced this issue May 9, 2024
…ince this is not covered by the updated field for an issue. Restructured code to execute only necessary requests and improved readability.
martan001 added a commit that referenced this issue May 9, 2024
…xer to persist value when commits information linked to an issue have been last updated.
@martan001
Copy link
Collaborator

Currently working:

  • mining issues (from multiple projects if using the jql parameter in the config
    • with related commits
    • connection between and issues and commits is created using the commit hash
  • mining merge request related to issues
  • mining milestones
  • most visualizations that utilize issue information work

Not working / experienced problems:

  • mining milestones from multiple projects in one run
  • amount of information provided by merge requests fetched by JiraITSIndexer is not great (REST API does not provide information like the title, etc ...)
  • “Sprints” visualization does not work with more than 3,000 issues (having the same creation date)
  • binding between user objects fetched from Jira and mapping them to stakeholder objects from git
  • build information linked to a Jira issues is not utilized
    • info: this information is already part of the REST response of the summary of development information linked to an issue
  • milestones in Jira do not have a required start and end date. This leads that when selecting a Sprint in e.g., the “Sprints” visualizations that the dates are shown as “undefined”.

martan001 added a commit that referenced this issue Jun 7, 2024
martan001 added a commit that referenced this issue Jun 7, 2024
martan001 added a commit that referenced this issue Jun 8, 2024
martan001 added a commit that referenced this issue Jun 8, 2024
…populated to add support for Jira sites that are accessible with no auth.
martan001 added a commit that referenced this issue Jun 8, 2024
martan001 added a commit that referenced this issue Jun 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition bsc enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants