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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.