Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

1- Known Limitations

1.1 - E-Mail Notifications

From Jira 8.19 onwards, users must have proper licenses and application access to receive email notifications. If users are removed from the access group, they won’t get notifications, even if they're involved in an issue (e.g., assignee or reporter), regardless of the notification scheme.

In Jira 8.20.6, a dark feature flag allows reverting this behavior: com.atlassian.jira.send.email.notifications.to.user.without.application.access.enabled

1.2 - Remember Me/My Login

According to Atlassian documentation, when you select "Remember my login" during login, Jira saves a cookie that automatically logs you in when you reopen the browser. However, this cookie is removed when you log out, requiring you to log in again.

Hint

You can configure Jira to disable the "Remember me" feature by modifying the jira-config.properties file.

  1. Navigate to your Jira installation directory.

  2. Locate the jira-config.properties file (create it if it doesn't exist in the JIRA_HOME directory).

  3. Add the following property to disable the "Remember me" functionality:

    jira.option.allow.remember.me = false

  4. Save the file and restart Jira for the changes to take effect.

1.2 - Login Requires CAPTCHA

Sometimes, due to revoked cookies and other scenarios, users may encounter the CAPTCHA screen when VIP.LEAN Floating Licenses tries to log them in. To prevent this issue, you can take the following steps:

  • Disable CAPTCHA entirely by setting the "Maximum Authentication Attempts Allowed" to blank.

  • Increase the "Maximum Authentication Attempts Allowed" to reduce the likelihood of triggering CAPTCHA.

These settings can be adjusted in System > General Configuration. Leaving the field blank disables CAPTCHA altogether.

  • No labels