Adding a field to a Screen tab throws java.lang.IndexOutOfBoundsException

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


An error is thrown in JIRA UI when trying to add a field to a Screen tab.

The JIRA Server was contacted but has returned an error response. We are unsure of the result of this operation.

The following appears in the atlassian-jira.log

2018-03-19 06:32:34,156 http-nio-18080-exec-22 ERROR USER 392x329039x5 USERA /rest/api/2/screens/2/tabs/31307/fields [] Returning internal server error in response
Caused by: java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.rangeCheck(
at java.util.ArrayList.get(
at com.atlassian.jira.issue.fields.screen.FieldScreenImpl.getTab(
at com.atlassian.jira.action.screen.AddFieldToScreenUtilImpl.getTab(
at com.atlassian.jira.action.screen.AddFieldToScreenUtilImpl.validate(
... 267 more


Gathering the below SQL result might provide further insights into what happened.

SELECT * FROM fieldscreentab INNER JOIN fieldscreen ON (fieldscreentab.FIELDSCREEN = fieldscreen.ID) WHERE fieldscreen.NAME = '<AffectedScreen>';

(info) Replace <AffectedField> with the correct affected field name.

  • It appears that the ArrayList return was missing the Tab for the affected Screen in which the user tries to add a field into. 
  • There were duplicate sequence value in SEQUENCE column of fieldscreentab table.


The cause is unclear at this point to why the Tab of the affected Screen is missing from the list. 


Workaround A:

  1. Create a new tab
  2. Add a field to this new tab
  3. Drag and drop the field from new tab to the affected tab

This should resolve the error, adding new fields to the affected tab after doing the above will work.

Workaround B:

In some cases simply creating a new tab might resolve the issue

Last modified on May 3, 2024

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.