You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I run redash-migrate alerts with a test environment from the hosted redash, the creator of migrated alerts are the account of redash-migrate, not the original creators. In the case below, I created the test account to migrate whose name is redash-admin.
Expected behaviors
The creators have to be the same as those in the original environment.
The text was updated successfully, but these errors were encountered:
yu-iskw
changed the title
The creator of migrated alerts are the account of redash-migrate
The creator of migrated alerts should be the account of redash-migrateOct 21, 2021
yu-iskw
changed the title
The creator of migrated alerts should be the account of redash-migrate
The creator of migrated alerts are the account of redash-migrateOct 21, 2021
What you describe is currently the expected behaviour. The code does not try to retain the original alert creator. We can change this. It was not a priority at first because anyone can edit an alert regardless who created it (not the same for queries / dashboards).
Queries
What you describe is not the expected behaviour. Per this line, we create a user client which creates each query. This way the original creator of a query is retained after migration. If this is not happening for you then we need to see reproduction steps as this is a significant issue.
If you can provide reproduction steps, please open a second issue so we can track and prioritise it correctly.
Issue
I run
redash-migrate alerts
with a test environment from the hosted redash, the creator of migrated alerts are the account ofredash-migrate
, not the original creators. In the case below, I created the test account to migrate whose name isredash-admin
.Expected behaviors
The creators have to be the same as those in the original environment.
The text was updated successfully, but these errors were encountered: