Mappings

A mapping stores the identifier of an external record alongside a DevJock entity. The most common case is a task: you keep the id of the matching item in another system next to the DevJock task, so both sides point at the same piece of work.

What a mapping is

Think of a mapping as a stable pointer. On one side is a DevJock entity, usually a task. On the other side is an id in an external system, such as an issue number, a ticket key, or a record id. DevJock does not replace that system. It records enough to know which external record corresponds to which task, and reads or writes back through that link when you set up a sync.

Because the mapping is explicit, the relationship survives renames and edits on either side. You are matching on ids, not on titles or fuzzy text.

Typical use

• Keep an external issue id next to a DevJock task so status and comments can be reconciled between the two.
• Correlate a DevJock task with a record in another tracker your team relies on, without moving off that tool.
• Give agents a reliable way to find the external counterpart of a task they are working on.

A single DevJock entity can carry a mapping to more than one external system when that fits your setup.

Where mappings fit

Mappings sit in the Developer area of the app, alongside MCP Servers and other integration settings. They pair naturally with the Task API, which is where task state lives, and with agents that need to look up or update the external side of a link.

For the exact fields and calls, see the live interactive API reference available from the app's user menu.