Leveling Priority Formula - Structure/Gantt

[Frédéric Sandioisanji]

Hello, 

I am trying to set a way for the leveling priority can skip a date or range of dates when doing scheduling. For instance, lets say I want a 1 week break for everyone on the team, and I want that week to be account for in the resource leveling and calculations.

I do not want to adjust the Calendar, I want to work under Resources -> Leveling Priority -> Leveling Priority -> Formula. 

I have tired Start, start, StartDate, startdate, GanttStartDate, ganttstartdate, Date, Start_Date, start_date, Gantt_Start_Date, "StartDate", "startdate", "GanttStartDate", "ganttstartdate", "Date", "Start_Date", "start_date", "Gantt_Start_Date", "Start", and "start" and countless other different syntax values to try to access the "Start" value shown here.

Start Date does not work because thats based on the value on the Jira issue, and the gantt is not using that value to add leveling delays nor is it editing the jira issue. 

When I try to use all of the other values or even try to do something like "Start" it will provide me with this error message when I hit save settings
"Selected attribute is not supported. Please select a Rank field or a Jira field or an attribute of the Number type."

So, lets use the photo for an example, if the start date shown is between 10/jun/22 and 16/jun/22 I want to set the start date to 18/jun/22. This would be for every issue that falls within that value, not just a single issues (otherwise I could easily just use manual scheduling).

I believe there is just a syntax issue on my end, but when I try to do anything associated with a date it gives me that error message. 

Any help here would be great. 

Thank you

[Nicholas Ellis _ALM Works_]

Hello Frederic,

Welcome to the community!

The short answer is if you want to simply have Structure.Gantt give the team a week off you can do that in the resource settings, just set availability to 0% for that week.  Here is the related documentation

As for the error you're getting, it is because the leveling priority field is looking for a number not a date. It is the leveling priority field's job to determine the priority of issues, this is why it is looking for a rank field, which is mentioned in the error message.  You could write a formula to give issues a "rank" value, but it would just be a number, not a specific date.

The idea of resource leveling is that when resources are overloaded, we want to move some work into the future, but we want to make sure we aren't delaying high priority work.  So we use leveling priority to let us know if two issues both need to be done at the same time, which one is more important and will stay in place, as well as which is less important and can be delayed.

Cheers,
Nick [ALM Works]