Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bulk script editor is applied across the instance instead of limited to the organization #1640

Open
ninabaldwin opened this issue Jul 19, 2023 · 0 comments · May be fixed by #1654
Open

Bulk script editor is applied across the instance instead of limited to the organization #1640

ninabaldwin opened this issue Jul 19, 2023 · 0 comments · May be fixed by #1654
Assignees
Labels
additions: strategic 📊 Request for a strategic feature, or one with multiple requests from clients platform: node 🔅 Related to Node backend problem: bug 🦠 Something isn't working

Comments

@ninabaldwin
Copy link

Describe the bug
Previously the bulk script editor would apply only to messages within an organization. We received a report that it is now being applied to messages across the entire instance. This can be problematic as administrators in one organization can make changes to other organizations without their knowledge.

We need to revert the behavior back to applying only to messages within that organization.

To Reproduce
Steps to reproduce the behavior:

From within an instance that has multiple organizations, find a phrase that occurs in a text message script in both organizations.

  1. Go to "Bulk Script Editor"
  2. In replace text, type the phrase you found
  3. Type in text that it will be replaced with
  4. Click find and replace
  5. Review scripts with the phrase to confirm that it was changed in different organizations.

Expected behavior
Only phrases within that organization are updated. Other organizations should have no change.

@ajohn25 ajohn25 added problem: bug 🦠 Something isn't working platform: node 🔅 Related to Node backend additions: strategic 📊 Request for a strategic feature, or one with multiple requests from clients labels Jul 25, 2023
@ajohn25 ajohn25 assigned ajohn25 and unassigned ajohn25 Aug 4, 2023
@ajohn25 ajohn25 linked a pull request Aug 4, 2023 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
additions: strategic 📊 Request for a strategic feature, or one with multiple requests from clients platform: node 🔅 Related to Node backend problem: bug 🦠 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants