Audit logs
What are audit logs?
Elements Copy & Sync lets you automate many tasks linked to issue creation on your Jira Cloud instance, from presetting values in fields to creating issues during workflow post-functions.
In order to offer Jira admins a better view of these automated tasks, the "Audit logs" page of the Copy & Sync administration lists all the issue creations attempted by the add-on during the last 30 days.
Available information
Each row in the audit logs table provides information on an issue creation attempt by Copy & Sync. For each attempt, here is what can be found:
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 |
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 JIRA RESPONSE 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.) Exemple: 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. |
