Updating product license does not provide a confirmation dialog leading to possible mistakes that can turn the Jira instance into read-only mode impacting all users

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Highest
    • 10.2.0
    • Affects Version/s: 7.13.18, 8.5.19, 8.13.27, 8.20.14, 8.20.25, 9.4.9, 9.10.1
    • Component/s: Licensing
    • None
    • 7.13
    • 1
    • Severity 2 - Major
    • 1

      Issue Summary

      When a destructive action is triggered from a user interface, it's good practice to have a confirmation dialog before committing such a change.

      Applying a new license on Jira may fall into that category, specially when changing the license seats.
      If, by mistake, a license with less seats is applied, it may turn the instance into read-only mode, immediately impacting the end-users.

      It would be great if Jira had a dialog confirming the changes on the license and asking the administrator to confirm this type of change.
      This would help minimize mistakes.

      Steps to Reproduce

      1. Install a vanilla instance of Jira Data Center.
      2. Apply a license with 5 seats.
      3. Create 5 users with application access, filling all license seats.
      4. Apply a new license with 1 seat.

      Expected Results

      Before applying the license, Jira shows a confirmation dialog showing the differences between the current and new license.
      If the new license has less seats available, the message warns the administrator of possible consequences, such as turning the instance into read-only.

      Actual Results

      No confirmation dialog is shown and the license is applied immediately, making the instance read-only and impacting all users.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

              Assignee:
              Daniel Rauf
              Reporter:
              Marcos Vinicius
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: