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

Cannot use the link in Issue Edit to move a subtask

XMLWordPrintable

      Firstly you need to have two different subtask issue-types that are not "compatible" with each other (eg use different Field Configurations).
      Now edit one of these sub-tasks.
      You will not be able to select a different issue-type in the edit page and it will have text saying
      "There are no issue types with compatible field configuration and/or workflow associations.
      The issue type can only be changed by moving this issue."

      This includes a link to a URL looking like http://localhost:8090/jira/secure/MoveIssue!default.jspa?id=10060 but this URL is only valid for moving parent issues.
      Subtask move needs to be something like http://localhost:8090/jira/secure/MoveSubTaskChooseOperation!default.jspa?id=10060.

      Clicking the provided link will produce an error message:
      "Sub-tasks cannot be moved independently of the parent issue."

            [JRASERVER-14232] Cannot use the link in Issue Edit to move a subtask

            Justus Pendleton (Inactive) added a comment -

            Link to the correct form to allow this to function properly.

            Justus Pendleton (Inactive) added a comment - Link to the correct form to allow this to function properly.

            Mark Lassau (Inactive) added a comment -

            MoveSubTaskType expects some state to be held already in the session.

            Also the move link for top-level issues goes to the "choose operation" screen as well where you can move it to another project, or issue type.
            So even though this is not ideal, it is consistent and less risky considering we want to ship 3.13 soon.

            Mark Lassau (Inactive) added a comment - MoveSubTaskType expects some state to be held already in the session. Also the move link for top-level issues goes to the "choose operation" screen as well where you can move it to another project, or issue type. So even though this is not ideal, it is consistent and less risky considering we want to ship 3.13 soon.

            AntonA added a comment -

            Michael,

            Can you have a look at this. Please write a func test for this.

            AntonA added a comment - Michael, Can you have a look at this. Please write a func test for this.

            AntonA added a comment -

            I think we need to link directly to the MoveSubTaskType operation rather than the MoveSubTaskChooseOperation!default.jspa operation.

            AntonA added a comment - I think we need to link directly to the MoveSubTaskType operation rather than the MoveSubTaskChooseOperation!default.jspa operation.

              jpendleton Justus Pendleton (Inactive)
              mlassau Mark Lassau (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 2h
                  2h