Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Automatically created custom field

In our Jira instance we ended up with way to much custom fields which I tried to clean up this morning. The question is about a field named "Story Points" (we somehow got two of them but use only one). This field is linked to 1 context and 52 projects. when I remove the field it is automatically recreated. Why is it recreated and how can I stop this?

2 answers

3 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 30, 2023

Hi @Remko Levels,

Jira Sofware does this, indeed. A certain amount of configuration elements are expected to be there as they are part of some of the many built-in templates. The story points field you refer to is one of them, certain issue types (like the Story issue type) are too.

There is no way to stop the behaviour of the automatic re-creation of the field. Most likely you created the other Story points field yourself (e.g. as part of a migration from server). You may want to look into migrating your data from the other field into system field before eliminating the custom field that was added, but depending on the amount of data and existing configuration you may have, that may be quite a bit of work.

As an alternative, you could keep things as they are and make sure that the system field does not appear on any screens you are using. Even though it is not ideal (especially for your admins configuring your instance), your end users won't be hampered in every day use.

Hope this helps! 

Thank you for the reply, that at least explains what is happening. Still weird that this field is not locked as other custom fields are. Luckily for us we might be able to migrate in the upcoming weeks as we are doing a lot of refinement anyway.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events