Field Data Lost After Issue Creation in Jira

Question

In a Jira project, when creating a new issue, all required fields (including custom ones) are filled correctly. However, after submitting the issue, some of those fields disappear or are left empty.
This means users have to manually re-enter the missing information.
If they don’t, the data is permanently lost.
This is a critical bug that could cause serious data loss, and it needs to be fixed as soon as possible.
The user is also requesting confirmation on whether this might be due to user error or misconfiguration.

abelalia87 · Answer

Hi,

Maybe workflow? Post function? Or in the workflow creation transition? I had a problem with a work item getting assigned to a different user, it was from the workflow.

Marc -Devoteam- · Answer

Hi @Sarah Ham(MVSK)

Check the issue layout section, and make sure to check all custom fields in the admin to make sure there are no duplicate fields.

Workflow post-functions on the create action?

3rd party apps involved?

Did you do these checks.

On an issue, can you open the automation section in the right hand details and press the refresh icon, are there automations ran on the issue?

If you want you can upload a video and members of the community can review.

Be aware that here in community, most of us are Atlassian users like yourself and we don't have access to your environment.

You can always reach out to Atlassian Support

Sarah Ham(MVSK) · Answer

Hi Walter,

Thanks for your response. However, I’d like to clarify that this is not a case of different fields between the Create and View/Edit screens.

As I mentioned, the issue occurs even when all required fields (including custom ones) are correctly filled out during creation. But after submission, these fields — even mandatory ones — are completely missing from the issue.

Nothing shows in the history tab, and there’s no automation or rule removing them.

We’ve confirmed this behavior repeatedly, and it’s affecting a project with over 2,000 issues and a hierarchy depth of 5.

Also, since the data is entered before the issue is actually created — and then disappears at the moment of creation — it likely never reaches the backend, which could explain why it doesn’t even appear in the history logs.

If helpful, I can provide a video showing the issue — from filling in the fields to their disappearance.

This issue started suddenly in the past few days. Could this be a recent regression?

May I kindly ask for a deeper look into this?

Thanks.