Index was outside of the bounds of the array fro defects in ALM.

The username patriciadm3 is not registered on this site. If you are unsure of your username, try your email address instead.
Question ID: 110251


  The above index was outside of the bounds of the array error keeps popping up when i try to update specific defects 1 and 17 in our ALM instance for one of our projects,  the issue is causing me to not be able to update properly those defects and lock up the module change capability when I had last touched those two defects.


How can I resolve this,


Marked as spam
Posted by (Questions: 379, Answers: 35)
Asked on October 25, 2021 12:21 pm
Answers (1)
Private answer

Hello Homerj,

I have seen this issue in the past and it is almost always that the entity has been corrupted and needs to be removed or otherwise repaired of the issue on the back end.  It is not really recommended to make backend non gui chnages so I would suggest that you get with your ALM specific support team to address it.

Note what actions had you performed that lead to this error.  Note what were you doing and how were you entering this data, as if a screen shot (using the screen capture tool, or by using a third party screen shot/screen capture tool and then pasting the image into the comments or what was occurring because we see issues using certain actions that can lead to corrupted comments sections and the entity being inaccessible)?   As long as a defect in error is highlighted each time the defect module is entered the issue will repeat and lock the client.  You may have to get out of the error and change the view type and then exit the module and the next time you enter the module the error shouldn't occur (as it will always occur so long as the focus on a defect in error is present.

Hope this helps, but you may need to engage your ALM support team to insure nothing is damaged further,


Marked as spam
Posted by (Questions: 0, Answers: 771)
Answered on October 25, 2021 12:27 pm