Versions Compared

Old Version 45

changes.mady.by.user Adam Repaský

Saved on

compared with

New Version 46

changes.mady.by.user Adam Repaský

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

  • Character Limit Discrepancy: Azure allows longer tag names and string attribute values than Jira Assets, causing which causes import errors when tags creating assets with attributes of the "text" type that exceed Jira Assets' 254-character limit. Resources with extended limits attributes that exceed this limit will be skipped during the import.

    For certain Azure resource types with long attributes by default, this error occurred more frequently, so we decided to implement workarounds.

Currently, the affected resources with attributes where we apply these workarounds are:

  • IpConfiguration: Id attribute (v3.15.0):

    • Id: A shortened version of the Azure Id (used for referencing, type "text").

    • Full Id: The complete Azure Id (stored as "textarea", which does not have the 254-character limit but cannot be used for referencing).

Note: If you had any IpConfigurations imported from a version prior to 3.15.0 and import them again, they will be treated as "duplicates" (since the Id attribute is being modified, the system sees it as a new object). To resolve this, we recommend bulk-removing all the existing IpConfigurations and then running the import again.

Troubleshooting

Assets - Azure Integration requires both Jira and Assets to function. Also make sure all the specific permission in your Azure environment was set right.

...