Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-72012

Usabilla integration with JIRA allow using normal password instead of API token

      Summary

      User successfully authenticates using a normal password instead of API token when integrate Usabilla to JIRA. Other users only able to authenticate with API Token (which is the expected behavior)

      Environment

      Cloud

      Steps to Reproduce

      1. Integrate Usabilla with JIRA using https://support.usabilla.com/hc/en-us/articles/208744805-Integration-with-Jira documentation.
      2. Insert the JIRA username and password (normal password)

      Expected Results

      JIRA should fail the authentication.

      Actual Results

      User successfully authenticate.

      Notes

      (Optional - If Necessary)

      Workaround

      Change the password to API token.

          Form Name

            [JRACLOUD-72012] Usabilla integration with JIRA allow using normal password instead of API token

            Megha added a comment -
            Atlassian Update - October 26, 2020

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Megha added a comment - Atlassian Update - October 26, 2020 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              sraj4@atlassian.com ProductGeek (Inactive)
              nroslan Atiqah Roslan
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: