Find answers to questions regarding configuration
At the moment, Approvals page is not available, but we are planning on supporting it in later versions.
Each time a search is performed, a corresponding JQL query is sent to Jira in the browser’s console (the Network tab) where you can preview the exact query.
Unfortunately, due to technical limitations, there is no possibility to redirect from the standard requests page to the app’s page. We also cannot change the link under the native “Requests” button. At the moment, the only solution is to display a banner with dedicated button, linking to the app’s requests page.
Logo or a custom text visible on the Requests page comes from your Help Center look and feel settings. If you make any change in those settings, it will be automatically applied and visible on the app’s Requests page.
Yes, you can use Assets as Filtering criteria, once you connect to Assets API. This allows you to filter data based on asset attributes like location, type, or department.
However, this feature is currently not available for the users of custom domain. If you’re using a custom domain, filtering requests using Assets objects custom fields is disabled due to current technical limitations.
For the Approvers field to be recognized as a valid criterion for filtering by the My Requests Extension app, it must first be indexed by Jira’s search engine. This requires the field to have Searcher template configured in Jira.
To set the necessary Jira configuration and enjoy filtering with the Approvers field on Requests page, follow the below steps:
Once the required Jira configuration is set, you can go to the My Requests Extension settings and access Fields configuration to enable the Approvers field as Filtering criteria. It’s also possible to define the scope of user search by adjusting the field’s Settings.