Scenario 3.3.1+ Release Notes
Scenario 3.3.3
Enable SSO Enterprise Features
Scenario 3.3.3 allows you to Enable Enterprise Features using SSO Login Type with qTest These configurations are applied to the qTest Scenario add-on.
Scenario 3.3.2
April 16, 2020
Jira Rate Limiting
When the Scenario server is being rate limited (HTTP 429), an error message will display: "qTest Scenario server is being rate limited by Jira, please try again later or contact your Jira administrator."
Scenario and OAuth Improvements
We have updated the process to configure Scenario to work with OAuth to make it easier for the user. With this update:
-
No need to go to Manager to generate and copy access token
-
No need to input the access token to the "password" input
-
When clicking "Save configurations", the user will be redirected to Jira authorization page. There Jira will ask if user want to allow access from Scenario.
-
After clicking "Allow", the user will be redirected to the Plug-in Configuration page and see the successful configuration message.
To view the updated process, please go to Configure qTest Scenario with OAuth.
Scenario 3.3.1-1
March 31, 2020
Ticket # | Component |
Description |
---|---|---|
N/A | Jira Cloud | Jira Cloud was failing to load the Scenario add on. This has been fixed. |
Scenario 3.3.1
February 17, 2020
Enhancements
OAuth Authentication
qTest Scenario now supports OAuth integration with Jira Server and Jira Data Center. For more information on how to configure qTest Scenario with OAuth, please refer to Configure qTest Scenario with OAuth.
NGINX Configuration
qTest Scenario now supports configuration with NGINX as a reverse proxy. For more information on configuring Scenario to work with NGINX, please refer to Configure qTest-Scenario with Nginx