Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-657

Support more attributes for user-provisioning

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      As per the user-provisioning documentation the feature currently supports the sync of:

      • Display name
      • Email address
      • Organization
      • Job title
      • Timezone
      • Department
      • Preferred language

      But it's not possible to sync additional attributes (e.g. Based in, Employee ID).

      Suggested Solution

      Add support for additional attributes from the identity provider that may be added in the future.

            [ACCESS-657] Support more attributes for user-provisioning

            Andrew T made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 856988 ]
            Andrew T made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 856732 ]

            Stefaan Vandaele added a comment -

            Please add "Based in" for mapping with Azure AD / SCIM provisioning.

            Stefaan Vandaele added a comment - Please add "Based in" for mapping with Azure AD / SCIM provisioning.

            Eduardo Oliveira - Mindpro Apps added a comment -

            Hi everyone,

             

            We noticed that this improvement wasn't delivered for a while and I am happy to share with you one more solution that may help you to achieve this goal (or complementary need of your company) - MindPro Sync, a new Marketplace app, where you can integrate OKTA, Azure AD, or OneLogin with Jira and JSM. 

            With this integration, you can:

            • Connect JIRA and JSM with your favorite Identity Provider (OKTA, Azure, or OneLogin);
            • Select and map user attributes to be displayed in Jira issues or JSM requests (and portal), making ticket resolution faster;
            • Use user attributes information from read-only custom fields to create JQL queries, filters, dashboards or to connect with other apps;
            • Choose to display data for the issue Reporter or Assignee;
            • Show user reporting hierarchy in Issues and JSM requests to facilitate escalation and approvals;
            • Automatically assign approvers based on user hierarchy.

             

            Available on Atlassian Marketplace for 30-days free: MindPro Sync

            Check the app documentation: https://mindpro.atlassian.net/wiki/spaces/MAP/pages/1700298761/Mindpro+Sync 

            Learn more at: mindproapps.com

             

            Eduardo, 

            MindPro - Atlassian Marketplace Partner

            Eduardo Oliveira - Mindpro Apps added a comment - Hi everyone,   We noticed that this improvement wasn't delivered for a while and I am happy to share with you one more solution that may help you to achieve this goal (or complementary need of your company) -  MindPro Sync , a new Marketplace app, where you can integrate OKTA, Azure AD, or OneLogin with Jira and JSM.  With this integration, you can: Connect JIRA and JSM with your favorite Identity Provider (OKTA, Azure, or OneLogin); Select and map user attributes to be displayed in Jira issues or JSM requests (and portal), making ticket resolution faster; Use user attributes information from read-only custom fields to create JQL queries, filters, dashboards or to connect with other apps; Choose to display data for the issue Reporter or Assignee; Show user reporting hierarchy in Issues and JSM requests to facilitate escalation and approvals; Automatically assign approvers based on user hierarchy.   Available on Atlassian Marketplace for 30-days free:  MindPro Sync Check the app documentation:  https://mindpro.atlassian.net/wiki/spaces/MAP/pages/1700298761/Mindpro+Sync   Learn more at:  mindproapps.com   Eduardo,  MindPro - Atlassian Marketplace Partner
            Kat N made changes -
            Link Original: This issue followed by ACCESS-822 [ ACCESS-822 ]
            Kat N made changes -
            Link Original: This issue is duplicated by ACCESS-766 [ ACCESS-766 ]
            Kat N made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Kat N made changes -
            Link New: This issue duplicates ACCESS-822 [ ACCESS-822 ]

            Kat N added a comment -

            Thanks everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate. Please vote, watch and comment on ACCESS-822 going forward.

            Kat N added a comment - Thanks everyone for watching and commenting on this ticket. As part of an initiative to better consolidate customer feedback, we are closing this ticket as a duplicate. Please vote, watch and comment on ACCESS-822 going forward.
            Roman P made changes -
            Link New: This issue is related to ID-7724 [ ID-7724 ]

              vsvidersky Vlad Svidersky
              akasper André K. (Inactive)
              Votes:
              47 Vote for this issue
              Watchers:
              67 Start watching this issue

                Created:
                Updated:
                Resolved: