How can i get a user reference attribute to synchronize from an incoming mapping via email address

JSM Development JSM Cloud
,
1

The schema-and-mapping does not include the schema entries for reference types (ie: User). The process i followed was:

  1. Create the Schema named Users in the Assets web UI
    1. Assets → Schemas → Create schema
    2. Only the left nav: Create a blank schema
      1. Fill out the form:
        1. Schema name: Users
        2. Click Create schema
    3. On the schema page, Click Add object type
      1. Fill out the form:
        1. Name: User
        2. Icon: User
        3. Click Create
    4. Click the Attributes button to switch to Attributes view
      1. Fill out the empty new line at the bottom of the attributes list
        1. Name: Atlassian User
        2. Type: User
        3. Click Add
  2. Click the … for the schema and choose Schema settings
  3. Open the Import tab

    1. Click the Create Import button

      1. Choose External Import
        1. Set Name to my-import
        2. Click Create Import

    2. Click the … button for my-import, choose Generate new token

      1. Save in file my-import.token

    3. Get info with:

      curl \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header "Authorization: Bearer $(cat ./my-import.token)" \
  --silent https://api.atlassian.com/jsm/assets/v1/imports/info

    4. Using the mapping link, change the /mapping endpoint to /schema-and-mapping

      curl \
  --silent \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header "Authorization: Bearer $(cat ./my-import.token)" \
  "$(
    curl \
      --header 'Accept: application/json' \
      --header 'Content-Type: application/json' \
      --header "Authorization: Bearer $(cat ./my-import.token)" \
      --silent \
      https://api.atlassian.com/jsm/assets/v1/imports/info \
      | jq -r '.links.mapping' \
      | sed 's/mapping$/schema-and-mapping/')" \
  | jq

      notice that the schema supplied does not include the Atlassian User field:

      {
  "schema": {
    "objectSchema": {
      "name": "UsersToo",
      "description": "",
      "objectTypes": [
        {
          "externalId": "cmdb::externalId/706cfcf4-0e8a-439e-ba3b-dfe3873553bf",
          "name": "User",
          "description": "",
          "inheritance": false,
          "attributes": [
            {
              "externalId": "cmdb::externalId/c1153fa3-35ae-4be4-9588-373b5f6d5aec",
              "name": "Key",
              "description": "",
              "type": "text",
              "label": false,
              "minimumCardinality": 1,
              "maximumCardinality": 1,
              "unique": false
            },
            {
              "externalId": "cmdb::externalId/a9234e28-f7d9-4c77-b128-55f095fd95bb",
              "name": "Name",
              "description": "The name of the object",
              "type": "text",
              "label": true,
              "minimumCardinality": 1,
              "maximumCardinality": 1,
              "unique": false
            }
          ]
        }
      ]
    },
    "iconSchema": {
      "icons": []
    }
  },
  "mapping": {
    "objectTypeMappings": []
  }
}

How can i get the user reference field to synchronize from an incoming mapping via email address if it does not show up in the schema section?

@VishAnkolekar , per our conversation, this is the explicit use case.

I found this community forum post from last year asking a similar question whose answer refers to this knowledge base suggesting after-the-fact Automation, but that seems like a last resort I’d like to avoid having to do…

2

It turns out, there are two related feature requests:

Both of these are 5 years old, so it seems unlikely either will be addressed. The current guidance I was given from Atlassian support was:

We do have an open feature request for this functionality: [Add support to User type attributes on External/Discovery Import | JSDCLOUD-10732|https://jira.atlassian.com/browse/JSDCLOUD-10732]. We encourage you to watch and vote on this suggestion to receive updates and help show interest from the community.

As of now, we are not able to provide an estimated time, as the feature requests will be handled by our Development team.

Please, note that all of the feature requests are implemented following our Feature Request Policy.

In the meantime, the current workaround is to:

  1. Perform your Discovery or External import as usual.
  2. After the import, update the Jira account attribute values for the relevant objects in Assets, using a different method (such as a manual update or a separate script).