Include a projects children in an alert rules limitations

[rbt-mm]

#1608

Currently, when creating a limited alert rule you need to select every single version of a project. This does not work well for projects which create new versions regularly.
By automatically including every active child of a project to a notification rule, it is simpler to limit all existing or every future version of a project to a notification rule.

Frontend PR

Signed-off-by: RBickert rbt@mm-software.com

[sonatype-lift]

⚠️ 14 God Classes were detected by Lift in this project. Visit the Lift web console for more details.

[rbt-mm]

Hey @nscuro, I'm not quite sure why this build failed. The workflow runs successfully in our repository and I don't think that I've changed anything which would throw a MojoExecutionException.
Do you know if something is wrong with my changed code or is it just a build fail? And if so, how can I restart the workflows to pass the checks?

[nscuro]

No worries @rbt-mm, it's just GitHub being GitHub again. When trying to download the frontend ZIP, the GitHub API returned a 503, causing the build to fail.

I don't think contributors can manually trigger workflows, but you could always contact us maintainers (as you did), or push an empty commit to trigger another workflow execution.

[nscuro]

Thanks for the PR @rbt-mm!

Overall this looks good to me. But I was wondering whether this should be an option that users can opt-in to / opt-out of? Just because there is a hierarchy, it doesn't necessarily mean I'm interested in all notifications affecting child projects.

[rkg-mm]

Thanks for the PR @rbt-mm!

Overall this looks good to me. But I was wondering whether this should be an option that users can opt-in to / opt-out of? Just because there is a hierarchy, it doesn't necessarily mean I'm interested in all notifications affecting child projects.

Yes that's something I was also thinking about, but for simplicity decided against it for the first attempt. But the question is:

1. Would this be a setting per notification rule, for all projects in that rule? (simple, add a checkbox and an additional field in the rule)
2. Or a setting per project in each notification rule (requires a field in the mapping table, not sure if datanucleus supports that without big changes, and also would have to refactor the project List to show an additional checkbox per project, plus APIs to update etc.)

If you think option 1) is enough we can easily do that, for 2) we would have to figure out how and will take some more time.

[nscuro]

I think option 1 should suffice.