#392

When a ticket is created via the wrench from a part row in newgo, two technical files are attached to the ticket automatically. The goal — to reduce back-and-forth and give support a full picture of the part from the very first message.

SVG sketch of the part

A preview of the part from the project — the same graphic you see on the cutting map. Extracted from the part-row thumbnail (NewGo renders it as an inline data-URI image). The SVG content is the part outline with operations, edges and dimension labels.

On the support side this file is shown right in the message thread as a thumbnail (220×140); a click opens an enlarged lightbox. No need to «open the project to look» — everything is visible at once.

The server-side filename: part-N-svg.txt (to pass the extension whitelist). When sent by email, the attachment is automatically renamed to part-N.svg, so it opens as an image in the email client.

JSON dump of the part's parameters

A complete machine-readable snapshot of the selected part from the current project: sizes, material, edges on all four sides, operations (grooves, millings, holes, postforming templates), item link.

On the support side the JSON attachment is displayed as a [preview] button; a click expands a JSON tree — support sees the exact part parameters without opening the project or asking for clarifications.

Filename: part-N.json.

When attachments are not added

  • The ticket is created from the support page — there is no part link, nothing to attach.
  • The ticket is created from the wrench in the project header (context «order», not «part») — also no specific part link.
  • If the SVG thumbnail could not be extracted from the DOM (e.g., the thumbnail had not finished rendering) — the ticket is still created, without the SVG. The JSON is attempted independently.

Size and limits

  • The SVG is trimmed to 1 MB — for ordinary parts there is plenty of headroom.
  • Email has an overall attachment size limit (10 MB). If SVG/JSON exceed it, they won't be included in the email, but they will remain inside the ticket on .
  • Allowed attachment extensions (in general, not just these two) are constrained by a server whitelist — a defense against potentially dangerous file types.

Manual attachments

Besides the automatic SVG+JSON, you can attach your own files — in any ticket reply on the page via the composer. Same whitelist and limits.

Related topics