nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filled field disappears after creation

Taryn Lachter_ynlxl2

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.

Accepted answers

Manoj Kumar Gangwar

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.

All comments

Manoj Kumar Gangwar

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.

Trudy P Claspill

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_ynlxl2

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.

Taryn Lachter_ynlxl2

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud