Modify ↓
Opened 19 years ago
Closed 19 years ago
#1251 closed defect (fixed)
Integer out of range error if no components in system
| Reported by: | anonymous | Owned by: | Sam Bloomquist |
|---|---|---|---|
| Priority: | normal | Component: | ScrumBurndownPlugin |
| Severity: | normal | Keywords: | |
| Cc: | Trac Release: | 0.10 |
Description
Probably not an issue for most people- If there are no components defined in the system, the burndown tab throws an integer out of bounds exception. This is easily fixed by adding a component, but I determined this by examining the source. The error message is just the exception text.
Attachments (0)
Change History (4)
comment:1 Changed 19 years ago by
| Owner: | changed from Sam Bloomquist to anonymous |
|---|---|
| Status: | new → assigned |
comment:2 Changed 19 years ago by
| Owner: | changed from anonymous to Sam Bloomquist |
|---|---|
| Status: | assigned → new |
comment:3 Changed 19 years ago by
| Status: | new → assigned |
|---|
comment:4 Changed 19 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.



(In [2062]) fixes #1251 - put in a check to make sure the list of components is not empty before trying to get the first object in the list