What are logs?
Elements Copy & Sync lets you automate many tasks across your Jira Cloud instance, from presetting values in fields to creating issues during workflow post-functions. As these operations run, Copy & Sync keeps a detailed record of what happened, who triggered it, and whether it succeeded.
The built-in logging system gives Jira administrators full visibility into work items creations, sync activity between linked issues, and configuration changes — all from the Copy & Sync administration panel, organized into three categories:
|
Log category |
Purpose |
|---|---|
|
Execution Logs |
Track all issue creation and copy attempts performed by the app. |
|
Synchronization Logs |
Surface synchronization errors and warnings so administrators can proactively address sync issues before end users are impacted. |
|
Configuration Logs |
Provide a full change trail for recipes, global settings, and configuration modifications for governance and traceability. |
Each log category comes with its own set of filters to help you find relevant entries quickly. Log data can also be exported for further analysis (see Settings → Export configuration)."
Execution Logs
Execution logs record every issue creation attempt performed by Copy & Sync during the last 90 days, whether triggered manually, via workflow post-functions, bulk operations, or the REST API. They allow administrators to verify that automated issue creation is operating as expected and to quickly diagnose failures.
Available information
Each row in the execution logs table provides information on an issue creation attempt. For each attempt, the following columns are available:
|
Column |
Description |
|---|---|
|
Date |
The date and time of the issue creation attempt. |
|
Level |
The result of the issue creation attempt: Info means the issue was successfully created Error means an error occurred that prevented the issue creation |
|
Recipe |
The name of the recipe that was used during the issue creation. |
|
Trigger |
The way the recipe was triggered : Manual means the recipe was triggered manually Post-function means the recipe was triggered during a workflow post-function Clone & Move means the recipe was triggered with a Clone & Move recipe Workflow means the recipe was triggered when the source issue status was updated, and that a workfow synchronization was launched LINK means that a synchronization was established between two issues based on a Synchronization recipe UNLINK means that a synchronization was removed BULK COPY means the recipe was triggered during a Bulk copy REST API means the recipe was triggered by a call to the REST API |
|
Triggered by |
The Jira user at the origin of the issue creation attempt. The user shown depends on the trigger type:
The column shows the user's current Jira display name. Deactivated accounts are shown with an In some cases no user name can be shown:
|
|
Source |
The key of the issue from which the recipe was triggered. |
|
Information |
Either a confirmation message in case of success, or an error message indicating the reason for the error during the post-function. There are two kinds of errors: problems in the recipe configuration, or Jira configuration errors (which are marked with a tag). |
Error messages
The possible configuration errors returned during a workflow post-function are:
|
Message |
Explanation |
|---|---|
|
Recipe ignored : source conditions are not satisfied |
Your recipe specifies a "Project", an "Issue Type", a "Status", or a JQL filter in its "Source" tab, which are not the same as the ones of the source issue during the workflow transition where the recipe is being called. |
|
Missing project in recipe target |
Your recipe does not specify any "Project" in its "Target" tab. |
|
Missing issue type in recipe target |
Your recipe does not specify any "Issue type" in its "Target" tab. |
|
Inconsistent issue type in recipe target |
In its "Target" tab, your recipe specifies an "Issue type" which is not available in the "Project". |
|
Too many issue types in recipe target |
Your recipe specifies more than one "Issue type" in its "Target" tab. |
|
Too many projects in recipe target |
Your recipe specifies more than one "Project" in its "Target" tab. |
|
Maximum number of recipe execution reached |
A given recipe can only be called a limited number of times per minute, please wait before trying to copy again if this message is displayed. The limit is:
This limit is per recipe, and doesn’t affect the other features of the app (manual execution, automation for jira, etc.) Example: You need to import 200 issues into a project, and this will trigger a C&S recipe via a post-function. You can't import all these issues at the same time because, due to this limitation, you can only execute a recipe less than 20 times every 30 seconds. You must therefore perform several imports, of a maximum of 18 issues, which will result in 12 successive imports spread over 12*30 = 6 minutes. |
|
Jira response |
An error returned by Jira. For example, when a mandatory field is missing from the issue you're trying to create. |
Synchronization Logs
Synchronization log monitoring is an Advanced edition feature. To explore what's included in each plan, visit our App editions page.
Synchronization logs give administrators full visibility into ongoing sync operations between linked issues, surfacing errors and anomalies as they occur, before they cascade into broken workflows or user-facing impact. Administrators can act immediately adjusting configuration directly or escalating to the Elements Support team for deeper investigation.
Available information
Each row in the synchronization logs table represents a failed sync event - covering fields, comments, and attachments. For a given pair of linked work items, sync errors occurring within a 24-hour window are grouped into a single row: new errors are appended as they occur (visible in the expanded view), and the row's timestamp updates with each new event. The following columns are available:
|
Column |
Description |
|---|---|
|
Date |
The date of the most recent synchronization error recorded for this association. Because errors for the same association are grouped per day, this is updated to the latest failure within the 24-hour window. |
|
Recipe |
The name of the synchronization recipe that governs the association between the two work items. Displays "Unknown recipe" if the recipe has since been deleted. |
|
Source |
The source work item of the synchronization, shown as its Jira issue key and linking to the issue. Falls back to the internal issue ID if the key can no longer be resolved. |
|
Link type |
The type of relationship between the source and target work items: the name of the Jira issue link type (for example relates to, blocks), or Copy for associations created by a copy recipe that have no Jira issue link. |
|
Target |
The target work item of the synchronization, shown as its Jira issue key and linking to the issue. Falls back to the internal issue ID if the key can no longer be resolved. |
|
Number of errors |
The total number of synchronization errors for this association within the grouping window, the sum of unsynchronized fields, comments, and attachments. |
|
Details in unfolded view |
Expanding the row reveals a per-item breakdown of every failed synchronization, grouped into Fields, Comments, and Attachments. Each entry shows the subject (the field name, comment, or attachment filename), the date, and a message explaining why it could not be synchronized. |
Error messages
In the expanded view, each failed item is listed under its category - Fields, Comments, or Attachments - with its subject and an error message explaining why the sync could not be completed. Message wording varies depending on whether the error originated in Jira or in the sync engine itself. The table below describes each category and provides representative error examples to help with diagnosis.
|
Category |
What it indicates |
Example messages |
|---|---|---|
|
Fields |
A field mapped by the recipe could not be written to the target work item. The subject is the name of the source field. |
|
|
Comments |
A comment could not be copied to the target work item. The subject is the source comment. |
|
|
Attachments |
An attachment change could not be applied to the target work item (for example, an attachment deletion that could not be propagated). The subject is the attachment filename. |
|
Configuration Logs
Configuration logs provide a complete change trail of all modifications made to Copy & Sync's configuration. Every change to recipes or global settings is recorded and retained for 90 days, giving administrators full traceability for governance, compliance, and troubleshooting. In environments with multiple Jira administrators or where compliance requires change tracking, configuration logs answer critical questions: who made the change, when it happened and what was changed.
Available information
Each row in the log represents one save event (all field changes saved together in a single action share the same date, author and target). The main table shows the following columns:
|
Column |
Description |
|---|---|
|
Date |
The date and time the change was saved (stored in UTC). Filterable by a start/end date range. |
|
Change type |
The kind of configuration object the change applies to: Recipe, Settings or Connection. Displayed as a lozenge and filterable. (Recipe changes are recorded currently; Settings and Connection are supported by the same model.) |
|
Recipe |
The recipe the change was made on, shown as a clickable link to that recipe. Displays "Unknown recipe" if the recipe no longer exists, or a dash for non-recipe change types (Settings / Connections). Filterable by recipe. |
|
Author |
The Jira user who made the change, shown with their name and avatar. Displays "Unknown author" when the user cannot be resolved. Filterable by author. |
|
Changes |
The number of individual field-level modifications made in that save event (deduplicated so it matches the rows shown in the expanded detail). |
Change details (expandable row)
|
Column |
Description |
|---|---|
|
Field |
The human-readable name of the configuration field that changed (e.g. Name, Description, Status, Source projects, Target work item types, Status mapping). |
|
Type |
The kind of modification: Added, Removed or Modified. |
|
Old value |
The field's value before the change. Shows a dash for additions. |
|
New value |
The field's value after the change. Shows a dash for removals. |
Note: values are resolved into readable form wherever possible (users show as name + avatar, statuses / issue types / projects show as names rather than raw ids, and workflow status mappings are labeled by workflow).