Skip to content

RTECO-255 - Handled aggregate condition correctly#101

Merged
naveenku-jfrog merged 5 commits intojfrog:mainfrom
naveenku-jfrog:fix/RTECO-255-Issues-aggregated-to-other-build-numbers
Jul 18, 2025
Merged

RTECO-255 - Handled aggregate condition correctly#101
naveenku-jfrog merged 5 commits intojfrog:mainfrom
naveenku-jfrog:fix/RTECO-255-Issues-aggregated-to-other-build-numbers

Conversation

@naveenku-jfrog
Copy link
Collaborator

@naveenku-jfrog naveenku-jfrog commented Jul 10, 2025

Problem Statement: When using the build-add-git command within a Project, the issues from a previous build number are also added to the subsequent build, even when they are not relevant to it.

Solution:
Found the bug where we were just fetching build info from artifactory without specifying project name even we specify clearly the project name in command. This was a bug due to which previous build version affected issues were added to the current build affected issue irrespective of the aggregate field value.

Depends On Other PRs: No

Demo Video Link: https://drive.google.com/file/d/12sXeNUpNgrxben8bAgTrEJuDROdqM-I9/view?usp=drive_link

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • All static analysis checks passed.
  • Appropriate label is added to auto generate release notes.
  • I used gofmt for formatting the code before submitting the pull request.
  • PR description is clear and concise, and it includes the proposed solution/fix.

@naveenku-jfrog naveenku-jfrog added the bug Something isn't working label Jul 10, 2025
@naveenku-jfrog naveenku-jfrog merged commit d27ca25 into jfrog:main Jul 18, 2025
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants