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; } } }

JIRA Cloud has own uuid field and causing conflicts with our own...

Dylan Marsh

It looks like JIRA cloud has a new default custom field named "uuid". We already have one called "UUID". Now our field is not searchable, it causes a 500 error. If I try to delete the JIRA generated field, it just keeps coming right back (same with renaming). This broke a lot of custom plugins we use, etc.

Does anyone have any idea how to disable the new uuid field for JIRA Mobile Connect?

Accepted answers

Matt Doar_tzgiej

I'd suggest renaming your UUID custom field.

All comments

Matt Doar_tzgiej

I'd suggest renaming your UUID custom field.

Dylan Marsh

I get that is an option but would result in a large amount of work for our team. We have many custom plugins and integrations via the API that all rely on this custom field. Is this absolutely no way to disable the auto-generated one?

Matt Doar_tzgiej

If the custom field is locked, I wouldn't change it. Based on past experience of using the JIRA Agile plugin and the JIRA Service Desk plugin.

Can you disable the Jira Mobile Connect plugin?

Dylan Marsh

We don't have it installed, it seems like the fields are there "just in case".

However, I was able to fix the search issue by disabling the search template on the JIRA uuid field. This way, it still exists, it's just not conflicting with my existing field during searches.