After you get the IdP attributes mapped to Jira Custom fields, you can have them displayed in Jira issues or JSM requests for the respective reporter or assignee. This will give more power to teams to access user's information, in order to escalate and approve issues faster. And since the information are mapped using custom fields, ir means they are part of the issues and can also be used to create JQL queries and filters and used in gadgets displayed in Jira Dashboards.
Click here to learn how to add Custom Fields to Jira Issues.
MindPro Sync allows users to do more than displaying IdP attributes in Jira issues or JSM requests, it also gives users options to enhance the power of the information displayed, with exclusive features that will speed up ticket resolution.
From the "Field Mapping" screen, click on the "Display Options" button. The following menu will be displayed:
Please, note that the options displayed may vary according to the screen (Global or Project-Specific) and project type (Software or Service Management)
Display Attributes from (Reporter/Assignee)
Selects the context for the ticket resolution. You can choose to show the previously mapped attributes for the issue Reporter or Assignee, adding flexibility to different types of process. The data from the Reporter or Assignee will be displayed in the right panel inside the issue detail screen:
Allow project specific settings (visible in global configurations only)
Allows to set field mapping and display options by project. When enabled, the system will allow each project to set its own configuration. You can have different fields mapped for each project, if needed. If this option is not enabled, all projects will use the global configurations.
IMPORTANT Only field mapping and display options can be set by project. The IdP connection is still global. It means all projects will use the same IdP connection.
Display user hierarchy in issue details
Retrieves the user hierarchy tree from the selected IdP to allow users to see the approval structure inside Jira issues, following the selected context (Reporter or Assignee). By default, it shows the current reporter/assignee plus 2 upper hierarchy levels (3 levels at total). When this option is selected, the system will show a "Reporter/Assignee Hierarchy" link where the user can access the information, as below. When the user clicks on the link, a panel will be open in the right side of the issue detail screen with the hierarchy that comes from the selected IdP. Pass the mouse over the user name to see additional information:
Display Attributes in JSM Portal (for JSM projects only)
Allows customers to see the attributes inside the requests via Jira Service Management portal, following the selected context (Reporter or Assignee). This option is only available in the global configuration or for Jira Service Management projects.
Display user hierarchy in JSM portal (for JSM projects only)
Retrieves the user hierarchy tree from the selected IdP to allow users to see the approval structure in JSM portal requests, following the selected context (Reporter or Assignee). By default, it shows the current reporter/assignee plus 2 upper hierarchy levels (3 levels at total). This option is only available in the global configurations or for Jira Service Management projects. It also requires the the previous option (display attributes in JSM portal) is selected.
Auto assign approver from hierarchy (for JSM projects only)
For Jira Service Management projects, when this option is selected, the system will automatically set the person from the upper level on the idP hierarchy retrieved as the issue approver, following the selected context (Reporter or Assignee). This option helps to make the ticket resolution agile and faster since the approver will be set in real time when the ticket is created.
Please, note that, in case you change the reporter/assignee of a related issue, the system will add a new approver to the "approvers" field, according to the hierarchy level. However, the approver added before the change will remain on the field.
IMPORTANT In order to have the automatic assignment working, it is important to make sure the users in both hierarchy levels have the correct e-mails set in both IdP solution and Jira.