• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Assets - Import
    • None
    • 224
    • 136
    • 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.

      Update 14th October 2022:

      Hello everyone, 

      Thanks for your continued interest and feedback. Please let me assure you that we hear you loud and clear, and understand integrations are an integral part of the value proposition of Assets (f.k.a. Insight). We are currently doubling down on improving both reliability and scalability across the product which forms the foundation of opening ourselves up to third parties. Simultaneously, we’re working on making our import APIs available for Marketplace connectors, and are also collaborating closely with partners such as Device 42 in order to offer multiple avenues to ingest data in the future. 

      In the meantime - for those of you considering custom integrations, please refer to our API documentation on https://developer.atlassian.com/cloud/insight/imports/introduction// For those willing to share more about individual use cases to help us gain a more holistic understanding of the problem space, please feel free to book in for our office hours via this link - we’d love to hear more! 

      Thank you again,

      Doro Linneweber | Product Manager | Jira Service Management

       

      Problem

      Currently there is no way in cloud version to sync user information in JSM Assets, something similar to what is mentioned in LDAP import in Server/DC.

      Suggested Solution

      Just like Server/DC version, LDAP import should be available for Cloud

      Why This Is Important

      • Feature parity between Server/DC and Cloud as mentioned in here
      • Better integration with AD and other external databases

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JSDCLOUD-10486] LDAP integration with Assets

            Just my 2 cent, but would there be anyone out there that would consider to open the firewall and expose the corporate Active Directory / LDAP to the public internet?

            Tim Eddelbüttel added a comment - Just my 2 cent, but would there be anyone out there that would consider to open the firewall and expose the corporate Active Directory / LDAP to the public internet?

            03057810014

            ismaeelmuhmmad84 added a comment - 03057810014

            Smile 

             

             

            ismaeelmuhmmad84 added a comment - Smile     

            +1

            Artem Bessonov added a comment - +1

            Why does this have to be an "app" or "plugin"?  Assets is right there off the top level menu.  This should just be something that is part of configuration, create a new schema, select Entra ID, filter by type, etc, and go.

            Heath Wallis added a comment - Why does this have to be an "app" or "plugin"?  Assets is right there off the top level menu.  This should just be something that is part of configuration, create a new schema, select Entra ID, filter by type, etc, and go.

            Hey fellow watchers,

            There seems to be progress made on the below FR ticket. It integrates AAD / Entra into Assets / Insight:
            JSDCLOUD-10502 - Azure Integration for JSM Assets

            Atlassian Labs marketplace addon is here:
            JSM Assets - Microsoft Entra ID (Azure AD) Integration

            I don't know why it's not linked to this ticket...

            David Meredith added a comment - Hey fellow watchers, There seems to be progress made on the below FR ticket. It integrates AAD / Entra into Assets / Insight: JSDCLOUD-10502 - Azure Integration for JSM Assets Atlassian Labs marketplace addon is here: JSM Assets - Microsoft Entra ID (Azure AD) Integration I don't know why it's not linked to this ticket...

            any videos of workaround?)

            Алишер Кадамов added a comment - any videos of workaround?)

            +1 

            Nathan Mackenzie added a comment - +1 

            Hello @Dorothea Linneweber,

            you asked for some customer needs and I think I have one strong one we are dealing with at almost every second customer:

            Organization Structure

            1. Used mainly for approvals on portal (or even inside Jira itself) - with automation it is easy to check who is manager of current person and set him automatically as an Approver (classic use cases like "I need new phone" etc.).
            2. Using object graphs to visualize whole org structure (would be nice if it would be embeddable in the future).
            3. Secondary user info -> phone numbers, roles, departments, teams.. whatever info you wish to have. (Jira is currently missing some of these data in user profiles and even if some data is there, users can hide it and also it can't easily be used to search with it - e.g. give me all tickets from people from certain department past month).
            4. Phone number itself is a big deal for support teams that needs a quick contact to reporters (thats usually a deal in bigger organizations doing full time internal support for whole organization).

            It would be lovely to have options to import from most known systems - AD, AAD, Okta, Google, ... basically supporting LDAP and SCIM protocols for that would be sufficient (at least I think) to have the ability to import from most currently used IDM/IDP systems. We are currently at dead end having some customers on server/DC who want to migrate to cloud and are using such functionalities there.

            František Špaček [MoroSystems] added a comment - Hello @Dorothea Linneweber, you asked for some customer needs and I think I have one strong one we are dealing with at almost every second customer: Organization Structure Used mainly for approvals on portal (or even inside Jira itself) - with automation it is easy to check who is manager of current person and set him automatically as an Approver (classic use cases like "I need new phone" etc.). Using object graphs to visualize whole org structure (would be nice if it would be embeddable in the future). Secondary user info -> phone numbers, roles, departments, teams.. whatever info you wish to have. (Jira is currently missing some of these data in user profiles and even if some data is there, users can hide it and also it can't easily be used to search with it - e.g. give me all tickets from people from certain department past month). Phone number itself is a big deal for support teams that needs a quick contact to reporters (thats usually a deal in bigger organizations doing full time internal support for whole organization). It would be lovely to have options to import from most known systems - AD, AAD, Okta, Google, ... basically supporting LDAP and SCIM protocols for that would be sufficient (at least I think) to have the ability to import from most currently used IDM/IDP systems. We are currently at dead end having some customers on server/DC who want to migrate to cloud and are using such functionalities there.

            Hi Ariel,

            Could you please share the workaround here?

            Atlassian access gives name and email address and I want to understand how you are able to extract other user attributes and store in Assets.

             

            Muhammad Fahad added a comment - Hi Ariel, Could you please share the workaround here? Atlassian access gives name and email address and I want to understand how you are able to extract other user attributes and store in Assets.  

              8f5df932eda6 Dorothea Linneweber
              cf3a9e2a2246 Diptajeet Datta
              Votes:
              332 Vote for this issue
              Watchers:
              177 Start watching this issue

                Created:
                Updated: