Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-12773

After importing or migrating Assets custom fields values to another site Jira will show an error for all Assets custom fields on Issue view

XMLWordPrintable

    • 479
    • 34

    • 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.

    • Hide

      Hello Team 👋,

      I wanted to provide a quick update on this issue. At the moment, Assets does not officially support cloud-to-cloud or sandbox migrations, so we're reclassifying this as a feature request rather than a bug. The good new is that we do have an Assets data portability project in progress, though we don't have an estimated timeline to share just yet. We’ll use this ticket to keep you informed as we make progress, and we may reach out with questions as we design the solution.

      We sincerely apologise for any inconvenience this has caused and appreciate your ongoing feedback and support.

      Thank you,
      Mohamed Hassan | Product Manager, JSM Assets

      Show
      Hello Team 👋, I wanted to provide a quick update on this issue. At the moment, Assets does not officially support cloud-to-cloud or sandbox migrations, so we're reclassifying this as a feature request rather than a bug. The good new is that we do have an Assets data portability project in progress, though we don't have an estimated timeline to share just yet. We’ll use this ticket to keep you informed as we make progress, and we may reach out with questions as we design the solution. We sincerely apologise for any inconvenience this has caused and appreciate your ongoing feedback and support. Thank you, Mohamed Hassan | Product Manager, JSM Assets

      Issue Summary

      After migration or importing Assets custom field(s) value(s) to another site all Assets custom fields on issue view show an error "This field needs to be configured with an object schema” for all Assets custom fields.

      The error happens as the Asset custom field value is using workspace id of another site.

      Steps to Reproduce

      1. Migrate or import Issues with Assets custom fields from one site to another(applicable for prod to sandbox too)
      2. Update one of the Assets custom fields to object from current site
      3. Check that all Assets custom fields have an error

      Expected Results

      The error will be shown only for Assets custom fields which have incorrect workspace id in value.

      Actual Results

      The error is shown for all Assets custom fields if at least one Asset custom field has incorrect workspace id, even if field is not added to the Issue screen.

      Workaround

      Bulk update the Assets custom field to use objects from the current schema. Make sure to update all asset custom fields that were added to the issue view. Even if one field still uses the production workspace ID, all asset fields in the issue will be broken.

        1. Screenshot 2023-06-19 at 16.12.27.png
          Screenshot 2023-06-19 at 16.12.27.png
          42 kB

              90325da67d46 Mohamed Hassan
              207d30156835 Ivan Chapistrak
              Votes:
              51 Vote for this issue
              Watchers:
              43 Start watching this issue

                Created:
                Updated: