-
Suggestion
-
Resolution: Fixed
It should be possible to convert an issue into a subtask of another issue.
- is duplicated by
-
JRASERVER-5604 Task Sub-task relation
- Closed
-
JRASERVER-4495 make an issue a sub-task
- Closed
-
JRASERVER-4863 Allow issues to be moved to a sub-task of another issue.
- Closed
-
JRASERVER-7794 Make existing issues sub-tasks
- Closed
-
JRASERVER-8291 transform an issue into a subtask of another one issue
- Closed
-
JRASERVER-9441 Ability to select any item in JIRA (irrespective of whether it is a "parent item" or a "sub-task item") and move it under a different "parent item" so it can become a sub-task item under this new "parent item".
- Closed
-
JRASERVER-9490 Add another user option under "Operations" called "Make item a sub-task". This option will then take the current JIRA item and allow the user to specify which JIRA item will become its new "parent".
- Closed
-
JRASERVER-9999 Changing a subtask to a task and vice-versa
- Closed
-
JRASERVER-11086 Allow to move top level issue to be a sub-task of another issue and vice versus.
- Closed
-
JRASERVER-11099 Ability to change Standard Issue Types to Sub-Task Issue Types
- Closed
- is related to
-
JRASERVER-4446 Sub-issues should be able to contain their own sub-issues
- Closed
-
JRASERVER-5617 Change a sub-task to be a normal issue
- Closed
-
JRASERVER-12768 Bulk change of task to subtask AND/OR implement subtask creation or linking in Jelly Tags
- Closed
-
JRASERVER-13245 Bulk Convert Issues to Sub-task and back
- Closed
-
JRASERVER-17752 Control permissions over convert subtask to issue
- Closed
-
HIROL-909 Loading...