Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30215

Bulk Edit: Unable to progress with index greater than five.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Low
    • None
    • 5.2, 7.2.0-OD-05, 7.1.4, 7.10.2, 7.13.3, 7.13.9, 8.5.1, 8.5.3
    • Bulk Operations

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Issue Summary

      Attempt to bulk move issue types during edit of Issue Type Scheme fails with issue type not updated.

      Steps to Reproduce

      1. Start with a project using an Issue Type Scheme with multiple issue types
      2. Create Issues associated to the issue types
      3. Edit the Issue Type Scheme associated with the project to change the issue types used or apply a new scheme with different issue types
      4. A series of steps will now be presented to associate the issues with different issue types
      5. For each step use the enter key to proceed to the next step
      6. The edit will fail with the error presented as above and browser showing a connection error.
      7. On checking the project the issues will not have been migrated to the new issue types

      Expected Results

      Issues will be migrated from the original issue type to the new chosen issue type as defined in the edited scheme.

      Actual Results

      Issue types will not have been updated and the atlassian-jira.log will display and error of type (log snippet from 8.5.1 instance)

      http-nio-8451-exec-18 ERROR      [o.a.c.c.C.[.[localhost].[/jira_path].[action]] Servlet.service() for servlet [action] in context with path [/jira_path] threw exception [java.lang.IllegalArgumentException: Unable to progress to bulk edit bean with index greater than 1. 2 bulk edit beans available] with root cause
      java.lang.IllegalArgumentException: Unable to progress to bulk edit bean with index greater than 1. 2 bulk edit beans available
      	at com.atlassian.jira.web.bean.MultiBulkMoveBeanImpl.progressToNextBulkEditBean(MultiBulkMoveBeanImpl.java:299)
      	at com.atlassian.jira.web.action.admin.issuetypes.MigrateIssueTypes.doSetFields(MigrateIssueTypes.java:142)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:498)
      	at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)
      	at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
      ...
      

      Workaround

      The workaround to ensure the issue types are updated is to not use the enter key to proceed through the update steps but to ensure the next key is clicked with the mouse.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              rmassaioli Robert Massaioli (Atlassian)
              Votes:
              13 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

                Created:
                Updated: