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

« Previous Version 10 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 and higher, a dark feature flag allows reverting this behavior: com.atlassian.jira.send.email.notifications.to.user.without.application.access.enabled

image-20241022-104425.png

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.allowcookies = false

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

1.3 - 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.
image-20241021-154620.png

1.4 - Login Gadget on System Dashboard Displays Incorrect Message When No Seats Are Available

Using the Standard Login Page: https://<base_url>/login.jsp, the VIP.LEAN Floating Licenses app displays the following message when a free seat is not available:

image-20241022-103901.png

This message cannot be displayed if users log in using the dashboard gadget: https://<base_url>/secure/Dashboard.jspa. This is a limitation imposed by Atlassian.

image-20241021-162303.png

2 - Questions and Answers

Q: Will the VIP.LEAN Floating Licenses app affect Jira's performance?

A: No, the app does not impact Jira's overall performance. It is only involved briefly during the login process, and this interaction is very quick. The rest of the Jira experience remains unaffected.

Q: Can I monitor the usage of licenses in the VIP.LEAN Floating Licenses app?

A: A: Currently, no monitoring feature is implemented to avoid adding complexity to the code. However, Jira provides a standard feature called the Audit Log, which tracks all users added and removed from the active user group. You can export these logs as a CSV file and create your own report:

image-20241022-104914.png

Q: Is the user's account deactivated when they are not active or logged in?

A: No, the account remains part of the virtual user group, but without application access.

Q: What are the functionality restrictions for users who are not currently active (not logged in)?

A: When a user is not using Jira, there are no restrictions. Upon logging in, the user may already have a floating license. If not, they can either obtain a new one or, in rare cases, might not get a free seat. In this case, a message will inform the user of the waiting time before they can try again. This worst-case scenario only occurs if the ratio between available seats and virtual users is too large, or if the active users are occupying seats for extended periods. There are no restrictions in the logged-out status, and email notifications continue to work.

Q: Can issue filter subscriptions be sent to users without an active Jira license?

A: Based on customer feedback, we are not aware of any restrictions preventing issue filter subscriptions from being sent to users without an active license.


Q: Is it possible to @mention/tag and notify users via email if they don't have an active license?

A: Yes, based on our own tests with Jira 9.x, it is possible to @mention/tag and notify users via email even if they do not have an active license.

3 - Guidelines

3.1 - Upload App Button is missing

Please refer to this Page:

https://confluence.atlassian.com/jirakb/how-to-re-enable-plugin-upload-in-jira-data-center-1364557898.html

3.1 - How to remove the App and fall Back to normal Mode

- Remove the the App from File System (Plug-Ins Folder: e.g. /var/atlassian_shared/plugins/installed-plugins)

- Restart the Nodes.

  • No labels