Jira Structure - Gantt resource units in structure formula

[Justin]

Cc: @Daria_Baltiyskaya_ALM_Works_ for visibility.

Is it possible to be able to use the resource units in a formula?

I want to capacity plan, but don’t want to use a Gantt chart. 
The goal is to have a column that tells me how much of the resources capacity is utilised for an initiative based on the estimates in all child tasks, where the initiative has a fixed start and end date. 

if this is not possible, what are some alternatives?

[Nicholas Ellis _ALM Works_]

Hi Justin,

Welcome to the community!

Unfortunately this is not possible presently.  Here is the list of Gantt attributes that are available in structure.

You should be able to accomplish this with Structure alone and some formula columns.  I would simply roll up the work estimates (and maybe group by resource), then you could compare it to this formula to estimate how much work you can burn down before the due date (or any other date field).

with days_remain = DAYS_BETWEEN(today(), due_date) :
with team_size = 3 :

with working_days = ( days_remain / 7 ) * 5 :

working_days * team_size

This should give you the number of days of work you can do before the due date, based on your team size.

Cheers,
Nick [Tempo / ALM Works]

[Justin]

Thanks @Nicholas Ellis _ALM Works_ 

This seems like a good start, however, the team size differs for each resource. 

Let's say I have resource_1 that has a team of 5 and resource_2 that has a team of 3.
How would I have that reflect in formula? 

So.. if structure is then grouping by resource_1 the rolled up up estimates should only SUM if it is assigned to resource_1

---

Edit: okay so I found a very hacky solution, and I would really prefer to be able to do it in a more dynamic way, but this is how I am rolling up the original estimate when it matches a special issue type I just created called "Capacity". 

CASE(department,
  "resource_1",
  PARENT{SUM{IF (department.parent || department) = "resource_1" : original_estimate}},
  "resource_2",
  PARENT{SUM{IF (department.parent || department) = "resource_2" : original_estimate}}
)

Note: department is a cascading field. 

The capacity issue type contains a custom field for the team size. 

[Nicholas Ellis _ALM Works_]

Hi Justin,

I can see your thinking here, but I expect there is a slightly easier way to do this.  What you are doing here is going up one level with  the PARENT{} function, and then going back down multiple levels with SUM{}.  I would restructure it like so to check if we are on the right level (it might not be level 1) to avoid the use of PARENT{} around the SUM{} function.

IF level = 1: 
  CASE(department,
    "resource_1",
    SUM{ IF (department.parent || department) = "resource_1" : original_estimate },
    "resource_2",
    SUM{ IF (department.parent || department) = "resource_2" : original_estimate }
  )

This should be slightly more efficient than the code you shared, as it now only looks down the hierarchy  with SUM{}.

Cheers,
Nick

[Justin]

@Nicholas Ellis _ALM Works_ 

Thanks for trying to help here, that one unfortunately produces undesired results.
This might be because we have a custom field called level that mapped incorrectly. 

Is there a way that I can force it to look at the structure level?

Edit: found out I can use depth also and it produces an empty cell.

---

Here are some more thoughts I have has, just to clarify we are on the same page. 

Essentially, I made a huge hacky CASE statement to do the following, which is not possible:

WITH my_dept = department : 
  PARENT{SUM{IF (department.parent || department) = my_dept : original_estimate}},

So, basically on the current row, get the department value and only sum all of my siblings and their descendantsof they share a department field.

Hope that helps clarify a few things. 

[Nicholas Ellis _ALM Works_]

Hi @Justin,

Sorry for the long response time.  If you're still trying to get this working I would reach out to our support team at service-st@tempo.io 

Cheers,
Nick [Tempo/ALM Works]