Skip to content

feat(aci): add more action nodes #91607

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

Merged
merged 4 commits into from
May 15, 2025
Merged

feat(aci): add more action nodes #91607

merged 4 commits into from
May 15, 2025

Conversation

ameliahsu
Copy link
Member

@ameliahsu ameliahsu commented May 14, 2025

adding more action nodes (azure devops, email, github, github enterprise, jira, jira server, opsgenie, pagerduty, slack)

preview here
Screenshot 2025-05-13 at 5 28 18 PM

next to-dos:

  • still need to refactor the ticketing action modal for the ticketing action nodes to be complete (coming in a future PR)
  • plugin action
  • webhook action
  • sentry app actions

@ameliahsu ameliahsu requested a review from a team as a code owner May 14, 2025 00:25
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label May 14, 2025
@ameliahsu ameliahsu force-pushed the mia/aci/action-nodes-2 branch from 9dd40b7 to a0504d5 Compare May 14, 2025 01:05
Comment on lines +30 to +32
useEffect(() => {
fetchOrgMembers(api, organization.slug);
}, [api, organization]);
Copy link
Member Author

@ameliahsu ameliahsu May 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we need this for the SelectMembers component in the email action to properly load

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case, is there any way to move this to the email action component itself? This feels out of place when scanning this file, especially without a comment.

Copy link
Member Author

@ameliahsu ameliahsu May 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I originally had this in the email action component, but then I realized that this would be called for each instance of the component vs. having this at the top-level within the automation builder, where it would only get called once. We will also need the org members data for one of the data condition nodes (screenshot below). Let me know if you still think it should be within the component!

Screenshot 2025-05-15 at 10 01 07 AM

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still think it should be moved down to the component! Ideally this fetch call should be deduplicated by taking advantage of React Query, but that probably needs to be done in a separate PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now I'd just add an inline comment explaining why this is here

Copy link
Member

@natemoo-re natemoo-re left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few things to take another pass at, but overall looks really clean. Nice work! 👍

Comment on lines +30 to +32
useEffect(() => {
fetchOrgMembers(api, organization.slug);
}, [api, organization]);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In that case, is there any way to move this to the email action component itself? This feels out of place when scanning this file, especially without a comment.

@ameliahsu ameliahsu enabled auto-merge (squash) May 15, 2025 20:10
@ameliahsu ameliahsu merged commit 9c272df into master May 15, 2025
42 checks passed
@ameliahsu ameliahsu deleted the mia/aci/action-nodes-2 branch May 15, 2025 20:18
andrewshie-sentry pushed a commit that referenced this pull request May 15, 2025
adding more action nodes (azure devops, email, github, github
enterprise, jira, jira server, opsgenie, pagerduty, slack)

preview
[here](https://sentry-73eqbmn2e.sentry.dev/issues/automations/new/settings)
<img width="1147" alt="Screenshot 2025-05-13 at 5 28 18 PM"
src="https://github.com/user-attachments/assets/e9d8c573-b02f-400a-9194-80514c9975d9"
/>

### next to-dos:
- still need to refactor the ticketing action modal for the ticketing
action nodes to be complete (coming in a future PR)
- plugin action
- webhook action
- sentry app actions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants