Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Filled field disappears after creation

Taryn Lachter
Contributor
January 2, 2025

I have a custom field called "Stakeholder" that is required in two projects and on four screens. It WAS working until I had to create a new stakeholder field because we needed it to be a multi-user select. Now, the new Stakeholder field won't hold an assignee. 

From the Create screen, I add myself as the assignee. Once I go to the issue, my name is gone and I have to re-add there. 

I copied all of the settings from the old field to the new field so I'm not sure what's missing. 

2 answers

1 accepted

1 vote
Answer accepted
Manoj Gangwar
Community Champion
January 2, 2025

Hi @Taryn Lachter,

It could be due to some automation or post functions that are triggering after issue creation. Please check the issue history if it is showing changes in the field values.

Also, check if components are used in that ticket and the default component assignee set.

Taryn Lachter
Contributor
January 2, 2025

Oh well this fixed it. I found a half-finished automation that was keeping it from completing the task. 

Like • 2 people like this
0 votes
Trudy Claspill
Community Champion
January 2, 2025

Hello @Taryn Lachter 

How are you updating the new Stakeholder field? Is that done manually, through Automation, or through workflow post functions?

When you created the new field did you give it the exact same name as the original field?

Does the original field still exist, or did you delete the field entirely from your Jira instance?

Is this in a Company Managed project or a Team Managed project?

Taryn Lachter
Contributor
January 2, 2025

I only have the one stakeholder field now. I created the new one, labeled it "stakeholder new" so that i could still see the configuration on the old one to copy it. Then I deleted the old one and renamed the new one to just "stakeholder."

The field is filled in manually sometimes. The only time its filled in by automation is when its based on Organization but those tickets are only created through the portal which is an entirely different scenario.

In this situation, an internal team member was going through Jira itself using the Create function. They filled in their name, then went to the issue and it was gone. But Organizations are not used in this case.

This is a company managed project.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian community, loom ai, atlassian loom ai, loom, atlassian ai, record recaps of meetings, meeting recaps, loom recaps, share meeting recaps,

Loom’s guide to great meetings 📹

Join us to learn how your team can stay fully engaged in meetings without worrying about writing everything down. Dive into Loom's newest feature, Loom AI for meetings, which automatically takes notes and tracks action items.

Register today!
AUG Leaders

Atlassian Community Events