Issue Summary

• Pre-10.92 instances (that hadn't API 2.0 feature toggle turned on) has no value (NULL) set in Enable API Token Access field, leading to an "HTTP 500 Internal Server error" when a user – either Super Admin or non-Super Admin – attempts to generate an API token.

Pre-10.92 instances that had API 2.0 feature toggle enabled are not impacted by this bug as the default value for Enable API Token Access field did not exist at the time.

Steps to Reproduce

Pre-requisites

• Instance has been installed pre-10.92 (10.91, 10.90, 10.89, etc)
• API 2.0 feature toggle has never been enabled
• Might be currently running any Jira Align release

1. Log in to Jira Align
2. Ask Support to enable API 2.0 feature toggle
3. Browse to User's Profile page
   Click user's profile picture, then select Edit Profile
4. Click API Token button. The User's API Tokens modal is displayed
5. Click Generate new API Token button

Expected Results

• The API 2.0 Token is generated and the corresponding field is populated in the User's API Tokens modal

Actual Results

• An "HTTP 500 Internal Server error" is thrown

Workaround

1. Ask Support to enable API 2.0 feature toggle
2. As a Super Admin, set Enable API Token Access to some valid value other than NULL (default on pre-10.92)
   1. Click Administration (cog icon)
   2. Select Platform, under SETTINGS section
   3. Click Security tab
   4. Locate Enable API Token Access field then select Yes or No in the corresponding dropdown
   5. Click Save Settings button to commit changes (filling up Enable API Token Access field with some valid data)