Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Thomas Lu February 12, 2023

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 unsupported-field.png

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

The location where a required field was automatically generated showed unsupported-field1.png 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

2 answers

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 12, 2023

Hi Thomas - Welcome to the Atlassian Community!

You mentioned that both projects were JWM projects. But are they both the same type? Are they both Team-managed or Company-managed projects? Or are they one of each? 

Thomas Lu February 15, 2023

Hi John - Thanks for responding.

Both of the JWM projects were created using the "New employee onboarding" template.

They're both Team-managed projects which are currently set to "Open" project access.

It doesn't make sense why custom form fields work on one but not the other, given that they were created within minutes of each other based on the same template and following the same actions.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2023

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. 

Thomas Lu February 15, 2023

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

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

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

  1. Dragged a People picker field type into the context field area
  2. Renamed the People picker "Departing employee"
  3. 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
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2023

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

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

0 votes
Jens Schumacher - Released_so
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 12, 2023

Hi @Thomas Lu , 

It will be quite difficult for anyone in the community to answer your question without knowing more details about the projects. This might be a better question for Atlassian's support team who will be able to look with you into the instance if required. 

Cheers,
Jens

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events