Skip to end of banner
Go to start of banner

Custom fields values are not being populated upon Jira issue creation

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

\uD83E\uDD14 Problem

When a new issue is created in Jira, the custom field values are not automatically populated by our application. However, this problem does not occur when updating existing Jira issues.

🧐 Cause

We receive notifications from Atlassian whenever an issue is created or updated, and we promptly act on these notifications to set the custom field values in the issues. A possible cause that the custom fields are not being updated only when you create an issue it can be that we are not getting informed by your instance when an issue is created. A cause of it can be that the workflow transition that is responsible for issue create is firing and Issue Create event is not in the post functions of this transition as shown in the screenshot.

Our application relies on receiving events from Atlassian whenever an issue is created or updated. We then promptly update the custom field values based on these events. The cause of the custom fields not being updated upon issue creation could be that our application is not receiving the necessary event from your Jira instance when an issue is created.

\uD83C\uDF31 Solution

To address this issue, please follow the steps below:

  1. Check the workflow transition responsible for issue creation.

  2. Ensure that the Issue Create event is included in the post functions of this transition.

If the Issue Create event is not present in the post functions, it needs to be added. This will ensure that our application receives the necessary event when an issue is created and can populate the custom field values accordingly.

If you have followed these steps and the issue persists, please contact us by raising a support request.

  • No labels