Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-8310

RuntimeException: No suitable constructor found for class IssueOperationsBarUtil in JIRA 6.0 master

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest (View bug fix roadmap)
    • 6.2
    • None
    • None

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

      The constructor for the class IssueOperationsBarUtil has changed again.

      https://stash.atlassian.com/projects/JIRA/repos/jira/diff/jira-components/jira-core/src/main/java/com/atlassian/jira/issue/util/IssueOperationsBarUtil.java?until=cca91df51289862ea7e94369d8b62e79fac25134&since=df6772e862d262c20dd2e6de371a74e6e3d4cb42

      This will mean that older versions of GH will not be compatible with JIRA 6.0.

          Form Name

            [JSWSERVER-8310] RuntimeException: No suitable constructor found for class IssueOperationsBarUtil in JIRA 6.0 master

            Boris Nose added a comment -

            The problem is fixed. Thanks!

            Boris Nose added a comment - The problem is fixed. Thanks!

            JoanneA (Inactive) added a comment -

            Tested in 5.1, 5.2 and 6.0, changing the issue detail view in plan/work mode and configuring the fields that are displayed, did not see any exceptions.

            JoanneA (Inactive) added a comment - Tested in 5.1, 5.2 and 6.0, changing the issue detail view in plan/work mode and configuring the fields that are displayed, did not see any exceptions.

            Michael Tokar added a comment -

            Fixed this on a branch off shipit, which I then merged into default so that JDOG would not be affected.

            Testing this will involve using the Detail View under all JIRA versions to ensure that it works. Also involved is configuring the detail view. The CI builds should go green as well.

            I left the original branch open so that we can merge it back to shipit if needed for emergency release.

            Michael Tokar added a comment - Fixed this on a branch off shipit , which I then merged into default so that JDOG would not be affected. Testing this will involve using the Detail View under all JIRA versions to ensure that it works. Also involved is configuring the detail view. The CI builds should go green as well. I left the original branch open so that we can merge it back to shipit if needed for emergency release.

              Unassigned Unassigned
              mtokar Michael Tokar
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: