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

feat(Zammad Node): Add reply_to and sender fields to article on ticket creation #9911

Merged
merged 1 commit into from
Jul 3, 2024

Conversation

envy
Copy link
Contributor

@envy envy commented Jul 2, 2024

Summary

Add two new fields to Zammad articles during Zammad ticket creation:

grafik

The new sender field allows setting which side has created the article, which always defaulted to Agent previously.
The new reply_to field allows setting a email address for replies that is different from the email address of the user that created the article. This is needed when using a single account to create tickets and articles as otherwise that accounts email address is used for replies.

Related Linear tickets, Github issues, and Community forum posts

This PR addresses the FR part of #9807 but not the bug reported in the ticket.

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

Copy link
Member

@Joffcom Joffcom left a comment

Choose a reason for hiding this comment

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

Mostly looks good, Did you also run the linter?

@n8n-assistant n8n-assistant bot added community Authored by a community member node/improvement New feature or request in linear Issue or PR has been created in Linear for internal review labels Jul 2, 2024
@CLAassistant
Copy link

CLAassistant commented Jul 2, 2024

CLA assistant check
All committers have signed the CLA.

@envy
Copy link
Contributor Author

envy commented Jul 2, 2024

Mostly looks good, Did you also run the linter?

I followed the steps from CONTRIBUTING.md which dos not say anything about linting. I did use VSCode with the ESLint plugin and it does not complain with my changes. I have now also run pnpm lint which did complain in the langchain node which I did not touch. So I guess my answer is maybe yes? :D

Copy link
Member

@Joffcom Joffcom left a comment

Choose a reason for hiding this comment

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

This looks good, Thanks for doing this.

@Joffcom Joffcom merged commit 957b2d6 into n8n-io:master Jul 3, 2024
8 of 9 checks passed
@github-actions github-actions bot mentioned this pull request Jul 3, 2024
@janober
Copy link
Member

janober commented Jul 3, 2024

Got released with n8n@1.49.0

adrian-martinez-onestic pushed a commit to onesdata/n8n-fork that referenced this pull request Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Authored by a community member in linear Issue or PR has been created in Linear for internal review node/improvement New feature or request Released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants