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

Allow issues to be moved to a sub-task of another issue.

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be good to be able to move an existing issue to become a sub-task of another issue.

      This would be useful in cases where a number of issues have already been created and the user wishes to group them as sub-tasks under one parent issue (e.g. Documentation issues for 3.0).

            [JRASERVER-4863] Allow issues to be moved to a sub-task of another issue.

            Jeff Turner added a comment -

            Andreas - you're absolutely right; thanks for the note, I'll fix it now.

            Jeff Turner added a comment - Andreas - you're absolutely right; thanks for the note, I'll fix it now.

            Andreas Deimer added a comment -

            BTW, does it really make sense to mark this issue with a version number even if it is not fixed?!?

            I do not think that forcing a DUPLICATE to be displayed in the release notes when its duplicated issue is not fixed. Anyway, it would be better to not mark any duplicate issues with a version number but only the "root" issue. When the root issue (would be JRA-4495 in this case) is fixed, it shall be listed in the release note.

            What do you think?

            BRgds
            Andreas

            Andreas Deimer added a comment - BTW, does it really make sense to mark this issue with a version number even if it is not fixed?!? I do not think that forcing a DUPLICATE to be displayed in the release notes when its duplicated issue is not fixed. Anyway, it would be better to not mark any duplicate issues with a version number but only the "root" issue. When the root issue (would be JRA-4495 in this case) is fixed, it shall be listed in the release note. What do you think? BRgds Andreas

            Jeff Turner added a comment -

            It won't – we intend 3.1 to be a rather minor release containing
            bugfixes and accumulated features. 3.1 will be released around the end
            of January, after which we'll review things like this for inclusion in
            3.2/3.3.

            Cheers,
            Jeff

            –
            ATLASSIAN - http://www.atlassian.com
            -
            Like our software? Tell your mates and you can win an iPod photo
            http://www.atlassian.com/mates

            Jeff Turner added a comment - It won't – we intend 3.1 to be a rather minor release containing bugfixes and accumulated features. 3.1 will be released around the end of January, after which we'll review things like this for inclusion in 3.2/3.3. Cheers, Jeff – ATLASSIAN - http://www.atlassian.com - Like our software? Tell your mates and you can win an iPod photo http://www.atlassian.com/mates

            Sulka Haro added a comment -

            This issue has been marked as fixed in 3.1 and then closed as duplicate of JRA-4495. JRA-4495 however is not marked as being fixed in 3.1 and is open. Does this mean the issue will or will not be fixed in 3.1?

            Sulka Haro added a comment - This issue has been marked as fixed in 3.1 and then closed as duplicate of JRA-4495 . JRA-4495 however is not marked as being fixed in 3.1 and is open. Does this mean the issue will or will not be fixed in 3.1?

              Unassigned Unassigned
              keith@atlassian.com Keith Brophy
              Votes:
              3 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: