My Jenkins uses GitHub OAuth security realm and GitHub Committer Authorization Strategy. It has separate admin user (a bot account), and user accounts, including my own.

My Github account is the owner of the organization that I'm using for authorization and for Github Organization task.

I experience the following behavior:

• Under my own login I can't create Github Organization task, I have "Access Denied. user is missing the Task/ExtendedRead permission" error (even that I have extended-read-permission plugin).
• Admin user can create Github Organization task, but under my own account I still can't configure it

I believe that this is not right, and I propose to change behavior to the following:

IF Github authorization is used AND current user is an owner of organization configured for authorization THEN give the user rights to create and/or configure Github Organization task for that specific organization.