Using "Move" option on sub-task of a next-gen projects returns 500 error

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • Component/s: next-gen
    • None
    • 12
    • Severity 3 - Minor

      Issue Summary

      Trying to move a subtask of a next-gen project leads the customer to a 500 error.

      Steps to Reproduce

      1. Create a subtask to an issue of next-gen project
      2. Use the "Move" option from the three dots on the top right corner.

      Expected Results

      The user gets the option of moving the issue to the required project and issue type.

      Actual Results

      500 internal server error is thrown

      Workaround

      Currently, there is no known workaround for this behaviour. A workaround will be added here when available

            Assignee:
            Nhat Tran
            Reporter:
            saksham (Inactive)
            Votes:
            10 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: