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!


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

Do the number configuration items impact performance?

In the process of migrating Server to Cloud and this was a good point to cleanup unused screens, custom fields, workflows etc. etc.

Q: Will the reduction of these items improve (theoretically) the performance of the new Cloud instance?

Or could I have spend my time wiser? ;-p

Kind Regards,


1 answer

1 accepted

8 votes
Answer accepted

They can, yes, but generally the performance hit is on the back end, and only really caused by items that are active.

Cleaning out inactive workflows, unused screens (not used in a scheme or workflow) and so-on is good for your admins, but they don't affect performance directly.

Fields are different - they can have an effect.  Again it's only when they're "active", and only when Jira needs to do something with them (read or write) but they're active whenever they exist on an issue, no matter whether they are on-screen, shown or hidden by the field configs.  So even if a field is unused, there's some overhead in having them associated with an issue.  It's always good to remove or reduce usage of fields.  Even merging fields is helpful because each individual field can have it's own overhead.  (Imagine the case I found when I started at an old old job - I inherited a Jira that had 40 pairs of start and end dates with slightly different names - that's 80 fields applied on every issue in the system, which is not a great use of the servers resources)

So, no, you have not wasted your time!  Easier admin, and tidier data is always a good thing.

I had a similar situation, I only had 4 start and end date pairs, but a couple of them had the same name as well. Im all for tidy, makes everyones life easier.

Like Mark de Bont _TMC_ likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events