(Unknown User (jleroux) ): Anybody should be allowed to create issues (see point 3 below).

(Unknown User (mbrohl) ): yes, but not anyone can provide patches afaik. They must file an ICLA first and then get specific permissions.

(Unknown User (jleroux) ): No, ICLA are only for committers . This is not to be confused with our policy where ICLAs are required to get write access to our wiki. It was a time where there was a check box in Jira. It has been removed, because when someone submit a patch (either on Jira or by any other way) s/he implicitely renounce to her right on the code giving the right to the ASF.

Then comes SPAM and how to handle it. Here are 2 answers:
https://help.github.com/en/github/building-a-strong-community/reporting-abuse-or-spam
https://github.com/marketplace/actions/mark-as-spam

(Unknown User (jleroux) ): Same than point 1. It's open, like in GH you can also have SPAM in Jira once you have created an account...

(Unknown User (mbrohl) ) we have fine grained permissions set in Jira, the answer does not refer to that.

(Unknown User (jleroux) ): what does it add? What do we need to control?

(Unknown User (mbrohl) ): Please have a look at the current Users/Roles/Permission settings. There are permissions which only administrators/PMC/committers have (e.g. deleting issues, attachments, editing comments etc.). Please check yourself.

(Unknown User (jleroux) ) We can ask Infra to offer the "Issues" feature (a top button) in our GH mirrors. You can then report in GH as you would to in Jira. It mostly offers the same possibilities than Jira.

(Unknown User (jleroux) ) See related Jacopo's answer in my comment below

(Unknown User (mbrohl) ) this is not answered as long as the process is clear. How is it used in practice?

(Unknown User (jleroux) ) Beside Jacopo's answer, why do we want that? What is the purpose?

(Unknown User (mbrohl) ) Checking what Jira's are open for a specific release, collecting release notes (what issues were solved in the release)

(Unknown User (jleroux) ): I think that this should not stop us in our choice. I have created a comment to move a conversation with Michael in. Else please simply look at  Searching on GitHub documentation.

(Unknown User (jleroux) ): Do we really need that as a requirement?  I know we are a peculiar TLP at the ASF. But I would be interested to have some fedback from other TLPs wich have resigned using Jira and are only using GH. Not speaking about all the succesful not ASF projects which are using GH and are more successul than us :/ I'm not even sure that decision makers are aware of such dashboards and fancy Jira stuff or use them in their decisions...

(Unknown User (mbrohl) ) This is a personal opinion and not an answer to the question.

(Unknown User (pierresmits)) Whether or not the project is an odd duck compared to other projects under the umbrella of the ASF is hardly a relevant question. 
The project needs to keep in mind that such one-page information (provided by the project, based on filters like mentioned under Q5) is key when decision makers (the potential adopters) review the product. Without the decision makers choosing to implement OFBiz (or continue to use the project), this project becomes irrelevant.

(Unknown User (jleroux) ): yes,  Also, as explained on top in this help page, there is a labels feature in the right bar, you can't miss it.