We are considering upgrading our server version to an interim build (patch) to fix a high-priority issue. It is presently resource-intensive to arrive at a precise list of all defects addressed within that build, as well as any prior builds back to our present server version- since builds are cumulative. I would like the 'Interim Build' information to be searchable and sortable so that it is easy to assess the impacts and risk for a given upgrade. I would also like this information to be easily accessible from the SMax Community similar to the 'Mobile Releases' page.
This becomes very important in order to assess the business risk for an interim build upgrade and is also extremely helpful in targeting key areas for QA and business user testing in sandbox(es). We believe that if we can isolate the specific functionality affected, we can save valuable testing time and speed up the rate at which we upgrade.
For the patch we are assessing, we reviewed and analyzed (40) SMax cases to determine whether there was potential risk or necessary testing for a certain platform functionality. Assessing the cases took less than (2) hours. Identifying those (40) cases took more than (3) hours. It included copying and pasting to Excel, then performing multiple sorting operations which became difficult because of the merged fields resulting from the paste to Excel. Pasting from Excel rendered (4110) rows. After sorting and deleting, we now have (90) actionable rows to review. All in all, this exercise took 6 hours in order to adequately assess the patch's risk for our validated environment.
I would prefer to do this filtering directly within the Community, first filtering for the server version and build, then identifying the upgrade version and arriving at a list of all defects addressed in a concise list. The data is there, the sorting tools are not yet available to the end customer.