Introducing Activity logs: Enterprise-grade traceability for Elements Copy & Sync

[#1]

Hi Community! 👋

If you sync Jira work items together, you know how it usually goes: it runs quietly in the background, until, for some reason, it eventually breaks. And when that happens, the first person to notice is usually an end user, not you. By the time a broken sync gets reported, data has already drifted, and the impact has spread further than it needed to.

That's the exact problem we're addressing with the release of a new feature: Activity Logs. We rebuilt logging experience for Elements Copy & Sync to give Jira admins full visibility into work item creation, synchronization health, and configuration changes: all from one place.

Why admins need better visibility

Until today, audit log in Elements Copy & Sync only tracked work item creation. Useful, but it leaves two blind spots that matter a lot in real-world Jira Cloud instances:

• No synchronization visibility. When a field, comment or attachment fails to sync between linked work items, nothing is logged. Admins may discover the problem weeks later, once data has drifted.

• No configuration accountability. With multiple admins managing recipes and global settings, there's no trail showing who changed what, or when.

We heard this repeatedly from teams running Elements Copy & Sync at scale, and it's exactly why this experience needed to cover more than just work item creation.

What's new: three tabs, one admin panel

1. Execution Logs (your current logs, improved)

This is our existing logs, but upgraded. It still tracks every work item creation or copy attempt, manual, post-function, Clone & Move, workflow, bulk copy, or REST API, with the recipe used, source work item, and success/error details.

What's new here:

• A new column showing exactly which user triggered each action.

• Improve date & time filters to focus on the time slow that matters.

2. Synchronization Logs 🔒 (Advanced edition)

This is the biggest addition: proactive visibility into sync errors across every linked work item association.

Errors are grouped into expandable lines that group errors that occurred within 24 hours for a given pair (association) of work items. This brings more context and visibility while analyzing (aimed to make it easier, avoid flooding with independent logs). The number of errors is displayed to give an idea of the impact. Details are listed in the expanded view.

3. Configuration Logs

The third tab gives you a full change trail for recipes and global settings: what changed, when, and by whom. Essential if you manage Elements Copy & Sync with a team of admins or need to answer to compliance requirements.

Read more about logs in our documentation page

Standard vs. Advanced edition: who gets what

Execution Logs and Configuration Logs are available to all customers, Standard and Advanced alike, including improved filters and additional information. Synchronization Logs are exclusive to the Advanced edition.

If your instance relies heavily on synchronization recipes across spaces or instances, this is one of the strongest reasons to consider Advanced: sync failures are cheap to catch early and expensive to catch late.

Read more about App editions.

The benefits, in short

Catch problems before your users do: sync errors surface as they happen, not weeks later.

Diagnose without guesswork: know exactly which field, comment or attachment failed, and where.

Know who did what: clear attribution across execution and configuration logs.

Govern with confidence: a full audit trail across execution, sync, and configuration for internal reviews or compliance.

Self-serve investigation: resolve most issues directly from the admin console, without opening a support ticket.

What's next

If you're already using the app, your feedback shapes the roadmap, drop a comment below or reach out through support with what you'd like to see next.

And if you're not using Elements Copy & Sync yet but work item cloning, synchronization, or cross-instance operation is part of your workflow, this is a good moment to take a look. Activity Logs is one more piece of what makes managing automation at scale in Jira Cloud easier, with the visibility to trust what's running, and the tools to act fast when something needs attention.

You can try the app for free for 30 days on the Atlassian Marketplace.