This app introduces a new Request Explorer for customers/clients that use your Jira Service Desk Cloud. The Request Explorer features a dynamical table, with extra fields, criteria and sorting. CSV export is possible as well. Besides the table, you can let fields be displayed on requests as well.
Use Apps section in Jira Service Desk Cloud, or Atlassian Marketplace.
When installed and licensed, your request explorer shows up on https://atlassiansitename.requestexplorer.com. The explorer is accessible from the right top menu in Service Desk (Portals area).
So, to start:
- Go to your service desk site (Url ends with /servicedesk).
- Click the top right menu, and then hit Ultimate Request Explorer. The page will now show the Request Explorer (on the domain https://atlassiansitename.requestexplorer.com) .
In the right side, you have the administration bar/menu (this only shows for Jira Admins), where you can choose Settings as well as Documentation (which links to here).
In settings you find 3 tabs. Common options, fields and criteria:
Common options lets you enable csv exporting, request view fields, and the option that lets users decide for themselves which fields to be displayed (and re-order them as well). You can also set the max number of requests that will show up in the list (otherwise pagination will take over).
In Fields is where you add extra fields to the list. A large number of different fields are supported.
In Criteria Fields you define which extra criteria you need.
Most of Jira fields are supported.
If you find something is missing, dont hesitate to contact us, and we will attempt to make it work.
Note that if you add a user field as a criteria, you actually permit the customer to search for user names in your Jira.
In general, if you add a criteria, the selection box will search your Jira for applicable values.
Fields visibility and scope (scope is only for fields, not criteria)
All fields, except Reference (aka. issue key), can be restricted by visibility and scope. Visibility is by groups, organisations or users. It means, that for a value for a field to show up, the user must be part of one of the entities defined in the visibility for that field. E.g. part of a group, org. or be a user. The check is by "OR". Leaving visibility empty, means all users can see the field value (yet, it stils requires view on the issue/requests).
For Scope, it's the same. The user must be able to view a Service desk defined in the scope for the field. If scope is empty, the field is viewable over all requests in all service desks.
Values for fields are as they are in Jira. Namely, rendered to display. The description (if chosen) is rendered as HTML. Images uploaded and shown in descriptions cannot be shown to users that does not have "Browse projects" permission in Jira. E.g. non-Jira created users.
This app has some restrictions on usage, but we are working on it.
- The app does not support security levels on issues.
- The user locale retrieved from Jira is not consistent or empty. So we cannot determine the user locale just right.
- Unfortunately we cannot retrieve i18n strings from Jira through the API, so only english language is supported right now.