|
[
Permlink
| « Hide
]
Sulka Haro added a comment - 08/Dec/04 08:03 AM
Two days after upgrading our Jira to 3.x, I've already gotten requests from our internal users to be able to do this. Please, please include this in a near-future version.
 Having just spent the day manually converting existing features & enhancements into sub-tasks I can say that I really would like this feature.
We really would need the ability to convert issues to subtasks, and we really would like it soon. Is there any plan to when this is going to take place?
And that would be a great alternative to the CVS import that does not support subtask import.
And it could be easier to implements? Thank you guys! Hi,
Glad to let you guys know that this has been scheduled for 3.5. Cheers, Please review this post
and consider this issue as a part of a greater whole. Ahmad Is it me or does the above link
 not work? Try this link
.
Cheers, We are hoping to make a 'small' 3.5 release early January which will not contain this feature. The feature will be implemented as part of JIRA 3.6.
Could someone please explain why this issue keeps getting pushed forward? It seems like an easy change, and one that makes a big difference for anyone doing project management and using Jira. Just look at the number of voters and watchers...
I guess I'd like to know whether it's being pushed because Atlassian disagrees with its users about the importance of the issue, or whether it's because of some technical reason that isn't obvious to us outsiders. Hi Håvard,
> I guess I'd like to know whether it's being pushed because Atlassian disagrees with its We do not disagree. Our main problem is the huge number of feature requests that we know are a great improvements and the limited time that we have to implement them We do realise this would be very useful and hence this feature is scheduled. We had enough features implemented and thought that it would be a great idea to share them with our customers. hence we went with the 3.6 release, rather than let these features sit in our CVS and be unused. Thanks, Hello,
I am using the 3.6 version. However, I do not think this issue is implemented in this version. Is it still impossible to convert tasks to sub-tasks? Thanks for an update on this issue? Hi Bert,
Apologies for the late reply, we have fallen behind somewhat in dealing with feature requests. Unfortunately, this issue did not make it into the Jira 3.6 release. We will keep you updated on any further developments. Thanks, Atlassian Folks,
I think that what Jira needs is some arbitrary method to order issues in a hierarchy. The notion of a sub-task (or sub-issue, that is) is ok with me, but when there is only one additional level of contained element, it might not be enough for complex tasks. (OK, ok, you might limit the number of hierarchy levels by, lets say 10, so we do not get to infinity...) Often, some sub-task of a new feature seems easy at first, but you have to split it into several sub-sub-tasks as you realize its complexity. There, you might see, we are also getting into a sort of requirements management, if it is for new features or bugs or any other type of issue. I would expect something that lets me define some issue as sub-issue of another one. Also, a sub-issue shall be hooked under some other issue or sub-issue, if it needs to be, or unhooked if it becomes a stand-alone issue. The ability to only subtaskify an issue ( Anyway, I think that enough people have voted in support of these, they are on the top of the voting list. Please consider it, quickly! Thanks, This would be really great to have. Especially if supported via Jelly Script.
I concur with what Andreas says. My brain works hierarchically, it seems, so I see everything in a tree structure. Projects, issues, components, user/group structures, comments even!... I think of all these things as hierarchical in nature.
Sorry everyone, this won't make it for 3.7. We've spent more 3.7 time than expected overhauling low-level things like searching, so JIRA scales under load, doesn't leak memory or cause database locks.
I have no problems understanding that sometimes new functionality must be postponed in favor of memory leaks, database locks, etc. However, this issue was registered 2 years ago
 There have been a bunch of releases, and judging by number of votes and/or watchers, there's no doubt this is an important feature. Can you please prioritize it into whatever is the next release? I'm pratically chewing my arm off waiting for this feature. We use jira to manage our software developement projects and grouping issues under a single heading is something we need (and like) to do quite often. So muggins here has to sit down, create new subtasks, link the old high level task and then closed the old task. Very boring, time consuming work I'm sure you agree. So for this feature to be pushed back again has me on the brink of tears. Please do your very best to get this into the next release of the software or I may suffer some kind of mental breakdown if this doesn't stop soon, I have even asked santa for this godlen version of Jira!!! On the other hand if it does make it in to the next release, I'll be flying over to give you all a great big hug! (although I'm not sure this is a very motivational thing to say)
I recently switched companies where I was previously using Jira and now am using a collection of various tools to manage developemnt. This would be a major selling point in getting us to adopt this tool.
This is seriously missing... it's just odd that such an obvious feature (task->sub-task, sub-task->task, changing parents, etc.) would be omitted.
Out of curiosity, but what's the magic # of votes for this issue before atlassian actually implements what so many have been asking for? This issue was created in 2004 and here we are in 2007 and it's not going away, mainly because we really frackin do want the functionality. So how about we get thrown a frickin bone and next release actually includes this obviously needed and requested improvement.
Any chance of this happening?
Yes, we had a spike of implementing the conversions Issue <-> Sub-task and it will be implemented in the future. However, no date for implementation of this feature is set yet.
Cheers, We are still having the same requirement for moving issues to subissues and vice versa. So please, implement this feature.
As I said before, this feature will definitely be implemented in one of the future versions. We currently have regular release cycles of JIRA and we plan and release features as they fit into each release. Therefore I do not want to promise you which version this feature will be implemented in, but it is certainly on our roadmap.
Cheers,
Yay! Thanks Atlassian. Based upon the previous release dates, pushing it to 3.9 will mean GA in approx a year ... ?!?
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Improvement
Resolved
Major
Subtaskify issues
