...
| Expand | ||
|---|---|---|
| ||
No. When a chart with User Impersonation is saved, a unique hash is generated specifically for that chart configuration. This unique hash means that there can be no changes made to the chart unless the user trying to edit the chart has the correct permissions. If a user without the correct User Impersonation permissions tries to edit a chart, this is the message they will see:  If they click “Remove User Impersonation” then the chart will revert to the default setting of no impersonation and load the data as the current user. ⠀ |
| Expand | ||
|---|---|---|
| ||
No. When the data source for a Custom Jira Chart is a Simple Search gadget then User Impersonation is disabled. This is because the Simple Search gadget allows for arbitrary JQL to be run which would bypass the security restrictions we have built for User Impersonation, allowing any user viewing the chart to write any JQL query. This is something we are looking to improve in future but for now, this feature is disabled. ⠀ |
| Expand | ||
|---|---|---|
| ||
No. A chart created with User Impersonation will only have User Impersonation enabled for the specific Confluence page on which it was created. This is because of the unique hash that is associated with the chart is related to the Confluence page ID. Therefore, if the page ID changes because the chart is copied to a new page, then the unique hash will no longer match what is stored in the database and the chart will revert to the default setting of no impersonation and load the data as the current user. This means that, if you copy the chart to a new page it will keep all the configuration (JQL, colors, title, etc.) but it will switch back to the default setting of no impersonation and load the data as the current user. ⠀ |
...