[
https://issues.apache.org/jira/browse/LOG4J2-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916511#comment-17916511
]
Piotr Karwasz commented on LOG4J2-3692:
---------------------------------------
We have a limit on the number of accounts in the JIRA instance, which severely
limits the number of issue reports here, hence the decision. Any advantages
JIRA might have do not really count if users need to go through a long
procedure just to report an issue.
> Log4j moved to GitHub Issues
> ----------------------------
>
> Key: LOG4J2-3692
> URL: https://issues.apache.org/jira/browse/LOG4J2-3692
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Piotr Karwasz
> Priority: Blocker
>
> Apache Log4j moved to [GitHub
> Issues|https://github.com/apache/logging-log4j2/issues].
> We only use JIRA as an archive of old issues. If you submit a new JIRA issue,
> it is unlikely to be addressed.
> See INFRA-26319
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
