Converting a standard issue to subtask will end in a generic 500 error if the new parent Sprint field is populated

XMLWordPrintable

    • 7
    • Severity 3 - Minor
    • 1

      Issue Summary

      Converting a standard issue to subtask when the parent issue key with sprint filled from the user account having no Schedule Issues or Manage sprints ends in a generic 500 error.

      Steps to Reproduce

      1. Create a new Story ( any other standard-issue type)
      2. Use the option from the (...) from the Jira issue view -> convert to sub-task. OR use the bulk edit option to change the issue type.
      3. Choose a new parent issue key that is having Sprint value filled
      4. As a user who has no permissions to Schedule Issues or Manage sprints, try converting the to the sub-task

      Expected Results

      Jira should report messages that the user is missing the required permisison.

      Actual Results

      500 error message is reported

      Workaround

      Conversion will work from the user account having this permission

      Refer - https://jira.atlassian.com/browse/JRACLOUD-78307 for error converting subtask to issue.

            Assignee:
            Unassigned
            Reporter:
            Rahul Kumar
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: