JWM project contains unsupported required fields; similar project can use them

Question

I have created two Jira Work Management projects to track the progress and automate our onboardings and offboardings. Although we could have technically operated out of a single project with different issues for onboarding and offboarding respectively, we opted to separate them because:

* Onboardings were meant to be more public, so that the new hire's team can track, comment on, and advance the issue along its workflow.
* Offboardings were meant to be confidential and for HR and IT's eyes only

These projects are mostly identical in the required information they collect, and the only differences were their statuses and the automation rules that were triggered by them.

In one of these projects, I was able to add custom fields such as a Dropdown, People picker, etc. to the issue type by dragging and dropping from the right-pane in the corresponding settings page. Whether designated as required or not, I was able to add them to the form and have them appear in the preview.

In the other project, adding the same fields in the same way resulted in the forms page  showing

while fields that were unrequired were unavailable to be used in the form.

The location where a required field was automatically generated showed  and attempting to preview the form indicated that it was unavailable.

I'm unsure about why the behavior between the two projects' issues' fields are so inconsistent, but I would appreciate any help to get these fields working on my second project.

The fields I am encountering this issue on are

* People
* Date
* Dropdown
* Checkbox

The problematic field types above are working in my first project, but not the second.

Thanks in advance.

Thomas

John Funk · Answer

I would submit a support ticket to Atlassian and let them sort it out.

https://support.atlassian.com/contact/#/

Thomas Lu · Answer

In both of these projects, I have created custom fields which are supposed to be independent of each other.

For example, I went into the first project's Issue type and

* Dragged a People picker field type into the context field area
* Renamed the People picker "New hire's manager"
* Designated the field as a required field type

Then, I went into the second project's Issue type and

* Dragged a People picker field type into the context field area
* Renamed the People picker "Departing employee"
* Designated the field as a required field type

In the first project, the "New hire's manager" field was visible in the project form.

In the second project, the "Departing employee" field was reportedly unsupported.

I don't know what happened, but doing the same thing in either project now results in the same problem, although the custom fields I previously added to the first project are still working.

John Funk · Answer

Just remember that Team-managed projects are completely independent of each other. And custom fields are now another animal with Team-managed. You can create a custom field directly in the project and it can only be used by the project. Then recently Atlassian rolled out the ability to use shared custom fields with Team-managed projects. But there are specific rules to that. One is that the Context for the custom field must include the project in the context. So in your case, both projects need to be in the Context for the shared custom field.

So it's either that problem, or one project is using an internal custom field and the other project is using a shared custom field, or both are using their own custom fields which are not shared.