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

Forwarding no longer possible for email and web articles #3855

Closed
MrGeneration opened this issue Nov 16, 2021 · 1 comment
Closed

Forwarding no longer possible for email and web articles #3855

MrGeneration opened this issue Nov 16, 2021 · 1 comment

Comments

@MrGeneration
Copy link
Member

MrGeneration commented Nov 16, 2021

Infos:

  • Used Zammad version: stable / 5.0.2
  • Installation method (source, package, ..): any
  • Operating system: any
  • Database + version: any
  • Elasticsearch version: any
  • Browser + version: any
  • Possible regression of: Email address not shown inside forwarded email #3824
  • Ticket: #1095880, #1096003

Expected behavior:

If you have a communication article with email buttons (reply / forward), you can forward the articles content without issues.

Actual behavior:

Web and email articles currently don't allow you to forward the mail in question - no error is shown.
Developer console shows this:

image

Strange enough: It does work for phone articles. :-)

Customer uses API to create the tickets. It does not matter if the from attribute is provided in article context.
If you add to attribute the issue is gone instantly. This thus only affects articles that have been created via API. from and to fields are not mandatory and thus should usualy™ not break forwarding processes:

{
   "title": "Magic",
   "group": "Sales",
   "priority_id": 2,
   "state_id": 1,
   "owner": "",
   "customer_id": 6,
   "article": {
      "subject": "Magic",
      "type": "web",
      "body": "XYZ,
      "content_type": "text/html"
   }
}

Steps to reproduce the behavior:

  • create web and email articles
  • try to forward it

Yes I'm sure this is a bug and no feature request or a general question.

@martini
Copy link
Collaborator

martini commented Nov 17, 2021

You can reproduce it with the following article created via rails console:

Ticket::Article.create!(
      ticket_id: 1,
      subject: "Magic",
      type: Ticket::Article::Type.find_by(name: "web"),
      sender: Ticket::Article::Sender.find_by(name: "Customer"),
      body: "XYZ",
      content_type: "text/html",
      created_by_id: 1,
      updated_by_id: 1,
)

Then go to http://localhost:3000/#ticket/zoom/1 and try to forward the last created article.

@martini martini added this to the 5.0.3 milestone Nov 17, 2021
@mantas mantas added this to To do in OLD Workflow via automation Nov 17, 2021
@mantas mantas moved this from To do to Done in OLD Workflow Nov 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
OLD Workflow
  
Done
Development

No branches or pull requests

3 participants