Learn about the app functionalities which can be configured in Settings.
In the Settings section you can customize the basic aspects of your Requests page. The view consist of five tabs:
Before you start, log in as a user with the Jira Administrators global permission.
To start configuring settings available in particular tabs, access Configuration first.
Once you’ve accessed the Configuration view, navigate to Settings.
The Requests availability tab enables you to manage the customer’s access to the Requests page as well as to decide about displaying the total number of requests in filters and on the list with requests.
To learn about the configuration of Access to requests check the Quick guide or follow the below steps.
By default all users can access the Requests page as the toggle next to Restrict access to Requests is disabled.
It’s possible to limit the visibility of requests in two ways. You can either grant access to requests only to selected users or choose which users shouldn’t see Requests page.
To give access to requests only to selected users:
The users, User scopes, and Jira groups which aren’t selected in the Include tab won’t see Requests page.
To restrict access to requests only to selected users:
By default, the users of Requests page can see the total number of requests in filters and on the list with requests.
It’s possible to disable the option for showing the total number of requests with the toggle. Thanks to this possibility you can easily hide requests’ numbers from customers.
Turning off the requests’ counting also automatically boosts loading of your requests. That’s why disabling Show total number of requests is also recommended for the users who experience performance problems while working with Customer Portal.
When the toggle next to Show total number of requests is turned on, the users of the Requests page can see the number of requests which is displayed in filters and on the list with requests.
When the toggle next to Show total number of requests is turned off, the total number of requests isn’t displayed on Requests page.
The Export tab enables you to set the maximum number of exports each customer can make by entering a number from 0 to 1000. Number 1000 is set by default whilst number 0 means that exporting option isn’t available to customers.
Changes are applied instantly.
The exported CSV file contains columns and field values which were visible on the requests screen.
The Banner tab serves for customization. You can change the text of the redirection banner along with the button leading to the app’s Requests page. The banner appears above the native Jira Requests page.
The text of the button can be maximum 24 characters long.
Each time by introducing changes to the already active banner text, click the Update button to save your configuration.
If you want to return the default redirection banner, click Restore default in the upper right corner. Keep in mind that your current banner will be lost.
Your custom banner is visible on the native Requests page.
The Security Level tab allows you to configure the visibility of requests with Issue Security Level.
The Requests page doesn’t have access to issues that have a configured Security Level by default. In order to see those issues, you need to include an atlassian-addons-admin
group to the Security Level that’s used on your issues.
To find out about the configuration, read about adding a group to your Issue Security scheme.
By default, the customer sees up to 1000 requests that have a configured Issue Security Level. If the limit of displayed requests is exceeded, in order to avoid timeouts, the global Jira administrators can decide whether the application should verify Issue Security Level of displayed requests.
The toggle next to Show all requests is by default turned off and it allows the app for checking the Issue Security Level of requests.
To allow the app for the Issue Security Level verification and display requests that have configured Issue Security Level, the toggle next to Show all requests should remain turned off.
To ignore the verification and display every request, regardless of its Issue Security Level, turn on the toggle next to Show all requests.
The Assets API tab enables you to configure your connection with the app. The connection is necessary to use Assets together with My Requests Extension when setting Assets custom field as Criteria.
To access Assets in Jira Service Management it’s required to upgrade to the Premium plan. Learn about upgrading your plan to Premium.
You can establish the connection with the app by using your Atlassian account credentials:
API tokens serve for authentication and they allow you to securely work with the app. The tokens can be generated from your Atlassian account. You can use your generated token by applying the copy and paste options.
To find out how to create and manage API tokens, see Atlassian documentation.
If you have problems with establishing the app connection, you’ll see the Error label under the Connection status section. The connection with the app can’t be established if you’ve introduced wrong credentials or your token’s already expired. Check your credentials and try again.
The introduced email and API token are verified. If your credentials are correct, the connection is established and you can use Assets together with My Requests.
You can terminate the connection with the app by disconnecting the API token.
By terminating your connection with the Assets API you won’t be able to use the My Requests Extension app with Assets.
Your app connection is terminated. You can establish a new connection by providing your API token and email address later.
The Anonymized usage statistics option allows you to have a part in shaping further app development. When the process of gathering numerical, anonymized data related to the user interaction with My Requests Extension is enabled, you can take part in improving the product’s features and your users’ productivity.
To learn more about data usage, read our Privacy policy and End-user license agreement.
It’s possible to manage the data collection settings anytime. Managing the settings won’t influence the app performance.
By default, the toggle next to Enable data collection is turned on and the process of collecting data is enabled.
To disable gathering anonymized statistics, you can turn off the toggle.
If you can’t find the answer you need in our documentation, raise a support request. Include as much information as possible to help our support team resolve your issue faster.