We have a project that tracks a large number of sub-components (7000~ approximately). We loaded the components and found out that jira really doesn't enjoy this type of behavior. The editor becomes incredibly slow for the project. Any good ideas as to a work around or a configuration that we can throw at jira to make it perform a little better?
Hi!
Is it possible to reduce the number of components for your project?
Cheers,
Gonchik Tsymzhitov
Believe me I asked and attempted to pose the option of breaking it down into multiple projects or custom fields. Unfortunately not. The project is setup to manage a fairly large and complex legacy system that requires ongoing support. The thinking though is that with other auto lookup fields like the tagging field seems to work fine with large volumes. For whatever reason the component field seems to bring a project to it's knees.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.