Our Jira server instance has captcha enabled for 3 consecutive faulty login attempts.
Since our global password policy requires us to change password every three months it is often so that the password used in ManicTime is forgotten to be changed and thus the captcha mode in Jira is triggered.

ManicTime plugin cant handle captcha and just ignores updating tags not showing login error, but the login attempt has still occured and is logged by Jira triggering captcha mode.

This leads us having to contact support to clear captcha for us and this has a leadtime of several days minimum.
In the meantime all login attempts to Jira and Confluence will require captcha and this is a great hindrance to us.

If we could use PAT instead of Username Password in the Jira Plugin these situations would not happen.

Please look at
https://confluence.atlassian.com/enterprise/using-personal-access-tokens-1026032365.html