-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
1
-
Issue Summary
In Jira Data Center, when migrating data from an instance to another via backup/restore XML, the Slack integration functionalities will be duplicated on the new instance:
- slack channel alerts will be sent
- automation webhooks will be sent
It would be better to block these in data restoration.
Steps to Reproduce
- install Jira Data Center for Slack DC
- set up channel and automations to post to channel
- migrate data to another instance via backup/restore XML
Expected Results
- the restored instance should be prevented from communicating with Slack as the source instance did
Actual Results
- the restored instance creates Slack posts just like the original instance did
[JSWSERVER-25909] Jira Data Center for Slack DC migration support
Support reference count | Original: 2 | New: 1 |
UIS | Original: 1 | New: 0 |
UIS | Original: 0 | New: 1 |
Description |
Original:
h3. Issue Summary
In Jira Data Center, when migrating data from an instance to another via backup/restore XML, the Slack integration functionalities will be duplicated on the new instance: # slack channel alerts will be sent # automation webhooks will be sent It would be better to block these in data restoration. h3. Steps to Reproduce # install Jira Data Center for Slack DC # set up channel and automations to post to channel # migrate data to another instance via backup/restore XML h3. Expected Results # the restored instance should not communicate with Slack as the source instance did h3. Actual Results # the restored instance creates Slack posts just like the original instance did |
New:
h3. Issue Summary
In Jira Data Center, when migrating data from an instance to another via backup/restore XML, the Slack integration functionalities will be duplicated on the new instance: # slack channel alerts will be sent # automation webhooks will be sent It would be better to block these in data restoration. h3. Steps to Reproduce # install Jira Data Center for Slack DC # set up channel and automations to post to channel # migrate data to another instance via backup/restore XML h3. Expected Results # the restored instance should be prevented from communicating with Slack as the source instance did h3. Actual Results # the restored instance creates Slack posts just like the original instance did |
UIS | Original: 4 | New: 0 |
Description |
Original:
h3. Issue Summary
In Jira Data Center, when migrating data from an instance to another via backup/restore XML, the Slack integration functionalities will be duplicated on the new instance: # slack channel alerts will be sent # automation webhooks will be sent It would be better to block these in data restoration. h3. Steps to Reproduce # install h3. Expected Results h3. Actual Results |
New:
h3. Issue Summary
In Jira Data Center, when migrating data from an instance to another via backup/restore XML, the Slack integration functionalities will be duplicated on the new instance: # slack channel alerts will be sent # automation webhooks will be sent It would be better to block these in data restoration. h3. Steps to Reproduce # install Jira Data Center for Slack DC # set up channel and automations to post to channel # migrate data to another instance via backup/restore XML h3. Expected Results # the restored instance should not communicate with Slack as the source instance did h3. Actual Results # the restored instance creates Slack posts just like the original instance did |
Description |
Original:
h3. Issue Summary
In Jira Data Center, when h3. Steps to Reproduce h3. Expected Results h3. Actual Results |
New:
h3. Issue Summary
In Jira Data Center, when migrating data from an instance to another via backup/restore XML, the Slack integration functionalities will be duplicated on the new instance: # slack channel alerts will be sent # automation webhooks will be sent It would be better to block these in data restoration. h3. Steps to Reproduce # install h3. Expected Results h3. Actual Results |
Labels | New: slack |
Affects Version/s | Original: 9.12.0 [ 105808 ] | |
Affects Version/s | Original: 9.4.0 [ 102404 ] | |
Workflow | Original: JAC Bug Workflow v3 [ 4450619 ] | New: JAC Suggestion Workflow 3 [ 4450620 ] |
Issue Type | Original: Bug [ 1 ] | New: Suggestion [ 10000 ] |
Priority | Original: Low [ 4 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Interest [ 11772 ] |
Link | Original: This issue is cloned from JSWSERVER-25459 [ JSWSERVER-25459 ] |