Zammad Addons New

What it is: An addon designed for IT and software support teams. Core functionality: Links Zammad tickets to Jira issues or GitHub PRs. New Capabilities in 2025:

The old Exchange integration was functional but clunky. New addons make it seamless.

A typical Zammad addon requires a specific definition file to appear in the UI and be registered in the system.

Create a file inside your engine structure, typically at: app/assets/javascripts/app/lib/app_post/_my_new_feature.coffee (or JS)

Or define it within the Zammad core hooks. The critical part is the App.Controller definition.

Example basic structure for a Zammad UI Addon: zammad addons new

// In app/assets/javascripts/apps/my_new_feature/my_new_feature.js
import App from 'zammad/app';
var MyNewFeature = App.Controller.extend(
init: function() 
// Your code here
console.log("My New Feature Addon Loaded!");
);
export default MyNewFeature;

Released: April 2026

Engineering teams live in Jira/Linear. Support teams live in Zammad. They used to yell across the hallway. Now, they sync.

This is where Zammad stops being a "ticket tracker" and starts being a business intelligence tool.

Released: March 2026

Forget copy-pasting into ChatGPT. This new community addon integrates a local LLM (like Llama 3 or Mistral) directly into the Zammad ticket mask.

Compatibility: Works with Zammad 6.1+.

Caveat: Requires your own OpenAI API key or a local GPU server.

The development roadmaps from major vendors hint at these releases: What it is: An addon designed for IT

1. The Pricing Model hurts SMBs

2. Documentation is still "Community Grade"

3. No "Premium Sandbox"

4. Reporting is powerful but ugly