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

Modification on object types in Assets might cause columns in Confluence assets macro defined on that schema to disappear

XMLWordPrintable

      Issue Summary

      Modification on an Assets object type e.g.

      • New object type created or deleted
      • `Object schema user` role assigned for a particular object type in Assets

      if that object type has columns that  are selected in the Confluence assets macro (like common columns such as Label , Created , Updated  and Key ) would cause those columns in LoL table to disappear.

      Steps to Reproduce

      1. Create a Confluence page and add assets macro. 
      2. Select schema and define AQL
      3. Select Created column along other desired columns
      4. Publics the page
      5. Go to Assets and add another object type
      6. Refresh the Confluence page

      Expected Results

      The table to show results as before

      Actual Results

      The Created column won't show in the list.

      Workaround

      The JSM agent to update assets macro on the page and reselect the column.

            [JSDCLOUD-13978] Modification on object types in Assets might cause columns in Confluence assets macro defined on that schema to disappear

            Richard Wang added a comment -

            Hi Everyone,

            This is Richard from the Assets team. We have some positive news regarding a solution. We are currently rolling out a fix for this issue.

            However, as part of this fix, when editing an existing table (that is a table created before this fix was introduced), this will result in needing to re-select columns. To be specific, when pressing the edit button on the Assets Macro in Confluence Edit Mode on an existing table prior to this rollout, columns will need to be re-selected only once. After the table is saved to the page again, there will be no need to re-select columns and functionality should be as normal. Note, this only occurs when editing. Existing tables will still be able to be read as normal.

            Thank you for your understanding.

            Best,

            Richard

            Richard Wang added a comment - Hi Everyone, This is Richard from the Assets team. We have some positive news regarding a solution. We are currently rolling out a fix for this issue. However, as part of this fix, when editing an existing table (that is a table created before this fix was introduced), this will result in needing to re-select columns. To be specific, when pressing the edit button on the Assets Macro in Confluence Edit Mode on an existing table prior to this rollout, columns will need to be re-selected only once. After the table is saved to the page again, there will be no need to re-select columns and functionality should be as normal. Note, this only occurs when editing. Existing tables will still be able to be read as normal. Thank you for your understanding. Best, Richard

              Unassigned Unassigned
              b38c9731e6db mtalebi
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: