This module integrates an existing Jira installation in your Icinga Web 2
frontend.
Hassle-free deep integration with Atlassian Jira. Depending on your needs, this
module is able to:
* create JIRA Issues for Problems detected by Icinga
* create only one issue per problem
* acknowledge Icinga Problems once a JIRA issue has been created
* manually create Host- or Service-related JIRA issues
* shows a Host/Service-related JIRA Issue History
And there is more. Use custom templates to trigger JIRA Workflows according
your very own needs. This way you can automatically fill JIRA custom fields
based on monitored system properties. This feature is mostly being used to
assign monitored objects to their related CIs or to trigger dedicated
customer-related workflows.
net-mgmt/icingaweb2*: Fix more breakage
Fix more ports broken by 2a12b7cab556 and f95fbf3e2406 that don't have
a direct dependency on net-mgmt/icinga-php-library or
net-mgmt/icinga-php-thirdparty.
Mark them all IGNORE_WITH_PHP=81
This should fix poudriere bulk -a.
*/*: Unbreak with php84
These ports were initially marked to IGNORE with php84 as their runtime
dependencies were BROKEN. As all of the runtime dependencies has been
fixed for ther requirements unmark these ports. Although these ports
build perfectly with php84 but there might still be runtime issues with
these ports with php84. The maintainers are requested to do some runtime
checks for these ports.
Approved by: portmgr (blanket)
*/*: Mark IGNORE_WITH_PHP=84
These ports are currently not compatible with php84 and is only a limited
set of ports. There might be more ports which has runtime issues. Please
check if your ports are compatible with php84 and if not pleae mark them
IGNORE_WITH_PHP=84
Approved by: portmgr (blanket)
net-mgmt/icingaweb2: Update to 2.11.4
Changelog:
-Add/Edit dashlet not possible
-Custom library path + custom library, without slash in its name, results in
exception
-Reflected XSS vulnerability in User Backends config page
Sponsored by: Netzkommune GmbH
