Subscription Module

The Subscription Module was designed to monitor customers' subscriptions and bill usage of Jira Connector accordingly.

Your subscription maintenance begins with the registration of the app when your data (environment, tenant) is received in our Admin portal.

Subscription types:

• Free Trial: free of charge usage for both Production and Sandbox environments, which ends after 2 months of usage. If the Production environment for a particular customer has Standard or Infinite type, then the Sandbox environment is free of charge. 
• Standard: regular subscription for the Production environment 
• Infinite: unlimited usage (for particular cases)

After two months' Free Trial period you will be suggested to switch to the Standard subscription type. The charge date, by default, is the first day of the month.

Environments

Production: We do not limit the usage of Jira Connector according to the companies or users. The subscription works for the whole environment.

Sandbox: Test environments are free for unlimited usage of all functions of the product during the first 2 months after installation on the Sandbox. When the Production subscription has Status Active, the Sandbox subscription for this tenant is Active and free. If the customer has 2 or more Sandbox environments, then if there is Production with the status Active, all Sandboxes will be free.

Your Subscription Information

To view your Subscription details, go to JIRA Connect Setup > Actions > Subscription Information:

>

Actions

• Register App: the ability to register Jira Connector.
• Grant Consent: the ability to manually grant consent to using Jira Connector. The system suggests you do this as part of the standard registration process (see Install and Register the App from the Microsoft AppSource). The manual action is provided for the case when the consent record is absent on the backend side in the registered app for some reason.

The Grant Consent action creates a record that is found on the Azure Active Directory Applications page (AAD Application List (9860, List)).

Also, refer to

https://learn.microsoft.com/en-us/answers/questions/971320/grant-consent-to-this-azure-active-direction-app-i.html

and

https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/configure-user-consent?tabs=azure-portal&pivots=portal 

• Republish Client Secret: the ability to manually republish the Client Secret. You can republish the Client Secret at any time but at least once every three months (before it expires).

Fields

• App Registration Status: Registration status of Jira Connector after downloading. Click Register App to register Jira Connector. Also, refer to Install and Register the App from the Microsoft AppSource.
• Subscription is Active: subscription status. Enabled if the subscription is active, disabled if inactive (blocked).
• Subscription Status Description: text field specifying e.g. the details of the blocked subscription.
• Subscription Expires On: the date the ongoing Free Trial subscription expires (only for Free Trial subscription type).
• Subscription Type: type of subscription (e.g. free_trial, standard)
• Client Secret Expires On: the date the current Client Secret expires. This date is obtained after the first registration and is calculated as "registration date (when the first Client Secret is obtained) + (3 months - 1 day)". On this date, Jira Connector will be blocked and you will be asked to register and republish the Client Secret. Note: 1) Registration of the environment and Client Secret republishing must be done by the user with correspondent access (admin); 2) You can republish the Client Secret ONLY within the account used during the first registration, and within the same tenant ID (Organization ID).
  The Client Secret is valid for "3 months - 1 day" (to avoid recalculation due to different timezones and to ensure work stability). 
  Other cases when republishing the Client Secret is required include updates and other service needs.
• Registered Tenant ID: the unique identification number of the tenant.
• Registered Environment Type: the type of the environment (e.g. Production, Sandbox).
• Registered Environment Name: the name of the environment. Note: you can change the environment name, however, on the backend side, the name used during registration will remain. This is done for identification reasons in support requests.