Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Software version 8.20 includes Team locked custom field

We are in the process of upgrading Jira server (software) to version 8.20

After doing the upgrade in a dev environment, we've noticed that there is a new custom field automatically created "Team" and this field is locked

This causes a problem for us as we already have a custom field called Team.

Is there anyway to remove/delete this custom field? what is its purpose?


2 answers

2 accepted

1 vote
Answer accepted

There is no way to remove this custom field, it's necessary for the functioning of some of the advanced apps.  You'll need to either migrate your existing field over into it, or rename your existing field to something to distinguish it from Team.

The problem is that the other field called Team is from the "Tempo" plugin  and it is also locked.

If it is necessary for the functioning of some of the advanced apps, why not to make it a system field instead of custom?

The two fields work differently. 

Tempo doesn't get to tell Atlassian how to implement fields in their Advanced Roadmaps, and Atlassian doesn't tell Tempo what to do in their apps.

I do understand they are talking to each other about it, with the move to be dropping Tempo Teams and Tempo using the Atlassian one instead, but I've no idea where they are with it.

0 votes
Answer accepted

Hi, @Improvement Engine Support

As far as we (Tempo) knows, there are no known incompatibilities with the Atlassian and Tempo Team Fields. Theirs is a separate/different field from ours.

It's likely there's something else going on with your settings that's causing the behavior you are seeing.

Please contact the Tempo on-prem support team directly so they can help you diagnose the underlying issue.


Sorry Dave, I was very unclear.  The fields are not incompatible, they just are for slightly different things.

Like Dave Rosenlund _Tempo_ likes this

No need to be sorry, @Nic Brough _Adaptavist_   Probably a poor choice of words on my part.

Just wanted to be sure things were as clear as possible for @Improvement Engine Support and that they knew they could contact Tempo for help.

They are clear thank you both.

It is not a real issue, more like an unexpected one, as the (Jira) field did not exist in the previous version. 

Like Dave Rosenlund _Tempo_ likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,868 views 37 49
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you