• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Data Center
    • 0
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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:

      1. slack channel alerts will be sent
      2. automation webhooks will be sent

      It would be better to block these in data restoration.

      Steps to Reproduce

      1. install Jira Data Center for Slack DC
      2. set up channel and automations to post to channel
      3. migrate data to another instance via backup/restore XML

      Expected Results

      1. the restored instance should be prevented from communicating with Slack as the source instance did

      Actual Results

      1. the restored instance creates Slack posts just like the original instance did

            [JSWSERVER-25909] Jira Data Center for Slack DC migration support

            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            Eduard M made changes -
            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
            SET Analytics Bot made changes -
            UIS Original: 4 New: 0
            Eduard M made changes -
            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
            Eduard M made changes -
            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
            Eduard M made changes -
            Labels New: slack
            Eduard M made changes -
            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 ]
            Eduard M made changes -
            Link Original: This issue is cloned from JSWSERVER-25459 [ JSWSERVER-25459 ]

              Unassigned Unassigned
              emarghidan Eduard M
              Votes:
              7 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: