You need to have an AWS account to use Meetings for Jira with Amazon Chime.
The plugin uses access keys to connect to your AWS account.
Use your AWS account ID or account alias, your IAM user name, and your password to sign in to the IAM console
In the navigation bar on the upper right, choose your user name, and then choose My Security Credentials.
3. Expand the Access keys (access key ID and secret access key) section.
4. Do any of the following:
To create an access key, choose Create New Access Key. If this feature is disabled, then you must delete one of the existing keys before you can create a new one. A warning explains that you have only this one opportunity to view or download the secret access key. To copy the key to paste it somewhere else for safekeeping, choose Show Access Key. To save the access key ID and secret access key to a
.csvfile to a secure location on your computer, choose Download Key File.To disable an active access key, choose to Make Inactive.
To reenable an inactive access key, choose to Make Active.
To delete your access key, choose Delete. AWS recommends that before you do this, you first deactivate the key and test that it’s no longer in use. When you use the AWS Management Console, you must deactivate your key before deleting it.
5. To configure Meetings for Jira with Amazon Chime plugin follow the next steps: Apps → Meetings for Jira with Amazon Chime → Settings.
Whether you haven’t configured it yet, the warning banner will up.
To configure the settings click the Configure button, fill Access key id and Secret access key fields, and press the Save button.
Note, that you can view your keys by pressing Show security keys checkbox if it’s needed, but by default, these fields are encrypted for security purposes.
As you pass the configuration, the warning button will change to the approving one. But steel you have the possibility to create new access keys if necessary by pushing the Change button.
Selection of projects for which a meeting can be scheduled
To enable/disable a scheduling meeting opportunity in Meetings for Jira with Amazon Chime plugin, go to the Apps menu → Meetings for Jira with Amazon Chime page → Projects tab.
As you get the Projects Settings page, you can view all your team’s projects, their types and available actions on them. In the Actions column, you can Enable(1) or Disable(2) a scheduling meeting opportunity for each project if you think that it is too early to create meetings for some of them, or there are other reasons not to do this, just disable this option where it is necessary, thou users will not face confusion about the projects under discussion.
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
As not all users have permissions to export Jira data, Jira Cloud Administrators can grant necessary permissions to work with Oracle Analytics Connector for Jira Cloud for specific users or groups. The instructions below demonstrate how to grant these permissions, allowing users to create, edit, watch, and export connectors.
Administrators have the permissions to work with the connector by default.
General Settings
Permissions
Being signed in to your Jira Cloud instance, select Apps, and then select Oracle Analytics Connector for Jira.
On the left-side menu, select Administration, and then select Edit.
In the Users field, enter the username you want to grant permissions to.
| Info |
|---|
You can select as many individual users as you need to. |
In the Groups field, select the groups you want to grant permissions to.
| Info |
|---|
You can select as many groups as you need to. |
Select Save.
| Info |
|---|
Here you can also view who has permission to work with Oracle Analytics Connector for Jira, edit, and revoke all permissions. |
Access Token Expiry
This feature allows admins to decide in how many days access tokens are to expire.
Being signed in to your Jira Cloud instance, select Apps, and then select Oracle Analytics Connector for Jira.
On the left-side menu, select Administration, and then select General settings.
| Info |
|---|
The access token expiry date is applied to all users. The default value is 365 days. |
If the administrator sets an expiry date of 10 days, this setting will affect all valid access tokens with expiry date later than 10 days from now, as well as tokens with no expiry date. All tokens with less than 10 days remaining won’t be affected.
If, later today, the administrator sets an expiry date of 20 days, no access tokens will be affected, because they were already set to 10 days.
If the administrator turns off the expiry setting, no existing tokens will be affected.
Data Sources History
Being signed in to your Jira Cloud instance, select Apps, and then select Oracle Analytics Connector for Jira.
Select Administration, and then select Data sources history.
| Info |
|---|
The tab displays all changes performed to the data sources by all users, including creating, editing the fields or filters, sharing, changing owner, and more. |
| Info |
|---|
You can also apply search by date. |
Access Tokens History
Being signed in to your Jira Cloud instance, select Apps, and then select Oracle Analytics Connector for Jira.
On the left-side menu, select Administration, and then select Access tokens history.
| Info |
|---|
Currently, this tab only reflects changes to the token expiration date. |
| Info |
|---|
You can also apply search by date. |
IP Whitelisting
Below are the current IP addresses used by the Oracle Analytics Connector for Jira application. We recommend whitelisting them only if you are experienced with the process and confident in managing it effectively.
| Code Block |
|---|
35.95.196.117
52.37.205.107 |