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

Team-managed fields arrive on the Fields Page: Rollout details & what’s coming soon

Carol Low

Hi Jira admins, it’s Carol here again 👋

I’m happy to announce that we are bringing team-managed fields into the Fields page.

What’s coming now

Starting in early November, team-managed fields will be available on the main Fields page, allowing you to manage them alongside company-managed fields. We’re also introducing a new “Can be used in” filter for quick access to team-managed fields.

Centralizing all fields on one page simplifies auditing and standardization, streamlines field governance, reduces duplication, and enables admins to quickly spot inconsistencies or gaps.

You may notice that the description formatting is strange for JPD fields - they are in rich-text but don’t display as such in the Fields page - we recommend editing these in JPD for now

What’s coming soon

Edit options for select field types with a single context (for both team and company-managed fields)
Trash Team-managed fields (instead of permanent delete)

Thanks again for all your feedback and continued partnership - leave a comment and let us know how you liked it.

Comments

Sebastian Wigge

Great improvement! Also having those team managed field in the site optimizer is a big help. Looking forward to the remaining field changes.

Steve Rhodes

Hi Carol! As long as I can get a company-managed field only option in the filter this looks great. I don't always want to see JPD or Teams fields.

Eugene Victorov_5k6xf2

Spaces?.. Have projects be renamed to Spaces in Jira? 🤔
Or, can these fields be used in Wiki spaces?

The idea is great for better governance, thank you - probably, there will be a single place to eliminate duplicate fields now!

But spaces...

Samuel Barden

Awesome update @Carol Low

Having team-managed fields on the Fields page will definitely make things easier to manage.

Excited for the "Can be used in" filter and the upcoming features like trashing team-managed fields, it's super useful.

Thanks for the heads-up on the JPD formatting too! Keep it up! 👍

Patrick Miller

Excellent. Keep up the great work!

Carol Low

@Steve Rhodes - Yes this is the "All spaces" option in the dropdown, as only company-managed fields can be used in all spaces. We call them company-managed field colloquially but we want to be clear about what it means (where it can be used).

@Eugene Victorov - Projects are being renamed to Spaces. It's still rolling out so your instance may not reflect it yet.

Josh

@Carol Low thanks for keeping the great enhancements coming! This will be incredibly helpful.

__ Jimi Wikman

I am not sure about this change because Team managed fields are only relevant in a team managed setting. Since these projects are not used or handled the same way as normal fields, why would I want to see them in administrative setting as the Fields view is?

As an administrator I am never touching fields in team managed projects as they are by definition managed by the teams themselves.

What value is this adding for me as a site or org admin? It only seems to add more clutter to an already cluttered view?

Josh

@__ Jimi Wikman

Team managed fields are only relevant in a team managed setting

If only your statement were true in practice... :-(

The challenge that we run into all too often is that a TMP custom field has the same name as a company-managed custom field. This causes issues with automation as well as user/admin confusion when using filters, building automation rules, etc.

We need the central visibility so we can work to address the tech debt that TMPs bring to the organization...

__ Jimi Wikman

@Josh I was not aware that this could cause problems since the fields are locked to a single space and it would not make any sense to have automation running on both team managed and company managed spaces at the same time, but if you actually can do this then I see your point.

Personally I would rather have a prefix to team managed fields, or even not show them at all for filters or automation if the scope is not limited to a single team managed space. That way they ARE limited to the confinement of that team managed space and can't cause issues outside.

But, that is just me and to be honest I would rather they removed that entirely as I really don't like team managed spaces

Dusty Brossart

Very nice improvement! Anything to help with administration is appreciated.

Welcome!

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