All Azure Communication Services for Jira settings can be made on one page, therefore the instructions below show how to find the plugin settings page and describe all available configurations.
Platform administrators always
have the ability to add Azure key
have the ability to modify Azure key
have the ability to enable/disable Azure Meeting feature for a certain projects
have the ability to access the History Log
How to configure Azure Communication Services for Jira?
You can get to the application settings page in 2 options:
1st Option
through the following steps:
Step 1. Click … Tab on the Jira’s main menu. Then choose Administration.
2nd Option
Step 1. Go to Jira Administration tab and select Manage apps section.
[add screenshot
Step 2. On the left side menu panel find “Power BI Connector for Jira” “a” tab and click Plugin settings.
[add screenshot
Azure Communication Services for Jira settings page
Below you will find a description of Azure Communication Services for Jira settings:
1. Reset to defaults.
This action will restore plugin settings to defaults, delete all Data Sources and user permissions.
2. Edit user permissions.
To be able to import data from Jira into Power BI Jira administrator should grant permission to create, edit, watch, and export connectors.
These settings grant users and groups permission.
Select groups - start typing to find and add relevant users group.
Select users - start typing to find and add relevant users.
[add screenshot
Where can I can Azure Key (connection string)?
First of all you will need to create Create Azure Communication Resource, then create a Key:
To create an Azure Communication Services resource, first sign in to the Azure portal. In the upper-left corner of the page, select + Create a resource.
Enter Communication into either the Search the Marketplace input or the search bar at the top of the portal.
Select Communication Services in the results, and then select Create.
You can now configure your Communication Services resource. On the first page in the create process, you'll be asked to specify:
The subscription
The resource group (you can create a new one or choose an existing resource group)
The name of the Communication Services resource
The geography the resource will be associated with
In the next step, you can assign tags to the resource. Tags can be used to organize your Azure resources. See the resource tagging documentation for more information about tags.
Finally, you can review your configuration and Create the resource. Note that the deployment will take a few minutes to complete.
Manage your Communication Services resource
To manage your Communication Services resource, go to the Azure portal, and search for and select Azure Communication Services.
On the Communication Services page, select the name of your resource.
The Overview page for your resource contains options for basic management like browse, stop, start, restart, and delete. You can find more configuration options in the left menu of your resource page.
Access your connection strings and service endpoints
Connection strings allow the Communication Services SDKs to connect and authenticate to Azure. You can access your Communication Services connection strings and service endpoints from the Azure portal or programmatically with Azure Resource Manager APIs.
After navigating to your Communication Services resource, select Keys from the navigation menu and copy the Connection string or Endpoint values for usage by the Communication Services SDKs. Note that you have access to primary and secondary keys. This can be useful in scenarios where you would like to provide temporary access to your Communication Services resources to a third party or staging environment.
Insert Azure Key (connection string).
[add screenshot
3. General Settings
Jira administrators have the ability:
Set a maximum number of tickets(Issues Limit) that can be exported at an instance level.
Set a Fields Threshold - a maximum number of fields that can be exported without warning message.
Save to apply settings
General Settings help to:
stop misuse of the addon
drop the considerable strain on JIRA
improve time to export
4. Custom Fields Map
Select Custom Field defined as Story Points in your system.
