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

Fixed the number of results in triggered alerts. #1895

Merged
merged 5 commits into from
Jan 13, 2023

Conversation

jhelmold
Copy link
Member

@jhelmold jhelmold commented Dec 30, 2022

Fixed the number of results in triggered alerts.

What:
Now the number of results for automatically triggered alerts and manually triggered alerts are the same.

In addition now the selected report (not always the latest report) is used when manually triggering an alert.

Why:
This is a bug-fix. Addresses T4-420 and T4-411.

How did you test it:

Checklist:

  • Tests
  • PR merge commit message adjusted

Now the number of results for automatically triggered alerts and
manually triggered alerts are the same.
@jhelmold jhelmold requested a review from a team as a code owner December 30, 2022 12:44
@jhelmold jhelmold added the backport-to-stable This pull request will be backported to the stable branch label Dec 30, 2022
Now the selected report is used for the manually triggered alert.
Previously only the latest report (not the selected one) was used
for the alert.
src/manage_sql.c Outdated Show resolved Hide resolved
@y0urself y0urself enabled auto-merge (squash) January 12, 2023 22:17
@y0urself
Copy link
Member

y0urself commented Jan 12, 2023

@jhelmold you should enable Auto-merge (squash) when you are done with your PR and use a proper conventional commit message for this. Thank you. :)
(I have done it this time.)

@y0urself y0urself merged commit ea67ea3 into greenbone:main Jan 13, 2023
mergify bot pushed a commit that referenced this pull request Jan 13, 2023
* Fixed the number of results in triggered alerts.

Now the number of results for automatically triggered alerts and
manually triggered alerts are the same.

* Fixed small memory bug.

* Use selected report for manually triggered alert.

Now the selected report is used for the manually triggered alert.
Previously only the latest report (not the selected one) was used
for the alert.

* Refactoring of the first solution.

* Added the header comment for the function "init_alert_get_data".

(cherry picked from commit ea67ea3)
y0urself pushed a commit that referenced this pull request Jan 13, 2023
* Fixed the number of results in triggered alerts.

Now the number of results for automatically triggered alerts and
manually triggered alerts are the same.

* Fixed small memory bug.

* Use selected report for manually triggered alert.

Now the selected report is used for the manually triggered alert.
Previously only the latest report (not the selected one) was used
for the alert.

* Refactoring of the first solution.

* Added the header comment for the function "init_alert_get_data".

(cherry picked from commit ea67ea3)

Co-authored-by: Johannes Helmold <83279292+jhelmold@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-to-stable This pull request will be backported to the stable branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants