How about keep the current one level display, but use tags to indicate the relationship of a task to others.

e.g. if task X has parents A, B and C and dependents of Y, we'd have to render something like:

TX This is an example
< Project tag> <Parent tag : A, B, C> <Depedents: Y>

and just get into the 2nd level, not deeper than 2.

Not having a hierarchical view of tasks belonging to parent tasks is really getting in the way. And I think everyone expects a hierarchical task organization, so ditching multiple parents would be a much better compromise for us to get what we need here. In the absence of that, I'm going to try to get us to something taht works better. I'm relatively new to Dropbox and have used lots of other task management tools in the past that work much better in this way. So I am going to try to move everyone to something else. I wish that Maniphest did this for us.

You may want to talk to @zeeg at Dropbox regarding Phabricator.

@anne I'm not sure how you meant it, but your comment comes across as sort of weirdly passive-aggressive. By all means, if Maniphest isn't working for you, we encourage you to look at other options.

We understand that this feature would be helpful, but we don't currently believe this is the most important thing we could be working on. There isn't a huge amount of active interest in it, and you can already create hierarchical relationships (just not view them when more than one level deep). There's also a rough approach to getting a deep view earlier in this task, too (T4207#52492). Of course these approaches aren't as nice as real tree support, but we don't believe there's a huge gap between what you can do today and what first-class support will eventually look like.

This request is competing with many, many other feature requests (including some from your coworkers at Dropbox) for priority. You can find more information about feature requests and priorities here:

https://secure.phabricator.com/book/phabcontrib/article/feature_requests/

If closing the gap between what's available today and a full implementation of this feature is absolutely make-or-break for your use case, you're probably correct to look at alternatives. We generally prioritize features which have a significant impact on many users, and very few users have use cases where this is mandatory functionality which prevents use of the tool.

I have installed P1094 on our installation and it's more or less exactly what I want. The only major improvement for me would be to have something similar in the project/tag-view. Showing the same dependience-tree for all tickets in that tag. Not sure if that's doable. The untill-then-fix is to have a "mother-of-all-tickets"-ticket per tag which has all other tickets as childtickets.

In T4207#55409, @qgil wrote:

Original request: http://fab.wmflabs.org/T162

Actually, it's https://phabricator.wikimedia.org/T96.

Just adding my vote to increase the priority for this feature.

For us subtasks are a big deal because they help non-devs with project tracking and sorting out info.
Actually, if we were able to display the tree of tasks we could do user stories / sprints / tasks very easily and that'll make phabricator A very easy decision

Added my vote to increase the priority for this feature. Thanks.

In case anyone might find it useful I put up P1828. It's my first libphutil script so it's a bit messy and you have to hardcode some of your specific server and user info but so it goes. It generates remarkup-ready dot code with a graph of the specified project's ticket dependencies.

Having a tree view is much needed thing. It sucks when all the tasks/subtasks are on the same level on a board. Would be nice if these are in tree view.
Thanks

Slightly adjusted task detail:

• use non breaking space for indentation
• reference P1094 quick hack and the related screenshot

In T4207#127358, @altendky wrote:

In case anyone might find it useful I put up P1828. It's my first libphutil script so it's a bit messy and you have to hardcode some of your specific server and user info but so it goes. It generates remarkup-ready dot code with a graph of the specified project's ticket dependencies.

How can we use that?
Where to put that file and how to call it within web interface of Phab.

In T4207#141783, @d.maznekov wrote:

In T4207#127358, @altendky wrote:

In case anyone might find it useful I put up P1828. It's my first libphutil script so it's a bit messy and you have to hardcode some of your specific server and user info but so it goes. It generates remarkup-ready dot code with a graph of the specified project's ticket dependencies.

How can we use that?
Where to put that file and how to call it within web interface of Phab.

Sorry to disappoint but I never integrated it into Phabricator. At this point it just runs locally and then you can copy/paste the output into a ticket/wiki/whatever to get it rendered. Also, I don't think the hyperlinks ever worked.

Definitely want to weigh in, and say that this is a vastly important feature for myself. Having the tree view in other bug trackers is helpful for planning, triaging, and almost every aspect of software development.

I agree with a previous commenter about how this impacts the usability of Workboards. I'll do a quick check to see if I can make a query to do this, but I would expect parent tasks to be the most visible items, and then show the subtasks as a tree view, or not at all.

After a few months of using P1094, we have found it invaluable in getting an overview of big and deep tasks. It is sufficient for our needs, we're happy with it continuing to work locally.

Does this also include the functionality to specify what subtype to be used when you click "Create subtask", or is this just the visual element?

I think that adding the possibility to specify that subtasks of "User stories" subtype should create "Subtasks" subtype as default would be a great improvement. Not sure if you have that in your pipeline already?