Are there any limits on number of work items a plan can contain ?
3 answers
Within WebSphere the default limit is 10000. This limitation may fail loading large plans, for example, if you are within hierarchical views and have a lot of links. I have plans with up to 15000+ workitems loaded on the link phase.
(I do not want to discuss about use cases of large plans and how long this takes. This is an issue of limited functionality in Plan filters. Today you can only filter by owner team and iteration).
How to increase the number of parameters in http header in WebSphere:
Start Websphere Console of CCM profile "Servers / Server Types / WebSphere application servers" "Web Container Settings / Web Container" "Custom properties" "New…"
com.ibm.ws.webcontainer.maxParamPerRequest = 20000
"OK"
"Save"
Restart WAS service
---
as mentioned by Guido, you'd need to consider the time it's going to take to display a plan with 2000+ work-items. Adding to this that you could also question how practical it would be for a human being to face such amount of work-items for day-to-day work.
I'd advise you to have a read at this enlightening post.
If you click on the enclosed (PDF) Jazz Performance Guide link, you'll find a "Showing Plans" section which gives good insight of both what the technical aspects are and also some recommendations for having plans not taking too much time to display.
Regards,
Stéphane
Comments
@Anuradha: to precise things.
1) what you've heard initially was true for RTC 2.0. See https://jazz.net/library/content/articles/rtc/2.0/enterprise-configuration/sizing-guide/index.html
2) Guido's answer confirms that RTC 4.0 version level removed such limitation.
Actually, RTC-2.0.0.1 would suffice as per Geoff's precise answer in the following post: https://jazz.net/forum/questions/55417/plan-contains-more-than-2048-workitems
Hope this clarifies things.
Regards,
Stéphane
That's not true. We have larger plans up to 5000 workitems. We use them not for daily work, because they need some time to load, but for Release Planning and Reporting we need them because of the aggregated progress bars etc..
Problem you may get are Browser, network and client-power (memory/CPU) depending.
Don't try to use such a plan with Internet Explorer 8 or older. IE9 and 10 are working. Best is FF10ESR or Chrome. This is because of the heavly usage of Javascript (AJAX) technology. IE 8 is very slow for this.
If you are in a network with latency to the server of more than 120ms you may also have a problem. There is a dashboard widget to test your network connectivity end to end to the applicationserver.