Hierarchies in Replicon

  • 1
  • Idea
  • Updated 4 years ago
Merged

This conversation has been merged. Please reference the main conversation: Roll up on task level

I find the limited support Replicon provides for hierarchical entities a particular point of frustration with this product.

Essentially, while it is possible to make departments and project tasks hierarchical, there is very limited capability around the actual hierarchy.

There are a number of things that I think should take into account the hierarchy, but I will start with the most glaring problem: reports.

As far as I can tell, there is no way to get reports to sum up the various hierarchy levels.  I can add Task Name (Full Path), and the report correctly puts in all the hierarchy levels (and orders them right).  But if you are grouping by Task Name (Full Path), it only shows the hours (for example) summed up against the tasks that actually had hours.

I mean if the task is this, with the corresponding hours entered:

Task A (4 hrs)

Task A / SubTask 1 (7 hrs)

Task A / SubTask 3 (13 hrs)

Then that is exactly what gets shown on the report.

However, I think most people would expect the time report to be actuall shown as this (with the subtask hours summed up for the next higher level task):

Task A (24 hrs) -- 24 = the 4 at this level plus the 7 and 13 at the lower level)

Task A / SubTask 1 (7 hrs)

Task A / SubTask 3 (13 hrs)

I always have to report this way, and the only way to do it is post-process in excel manually, which generally takes an hour for a decent sized project.

The same thing goes when reporting departments.

Photo of Ken Clark

Ken Clark

  • 5 Posts
  • 0 Reply Likes

Posted 4 years ago

  • 1
Photo of Ken Clark

Ken Clark

  • 5 Posts
  • 0 Reply Likes

Also - the most obvious corollary to this same problem is the Project Management "Tasks" tab view in the Actual vs Estimated column.  In order to determine the overall number of hours for a high level task, I have to expand the entire tree below it and add things up in my head.


This conversation is no longer open for comments or replies.