Height provides 4 lists so far, but I’ll focus on calendar and gantt lists. This feature request has several parts:
- A variant of the single-select custom attribute type, which I’ll call loop where a user adds options, selects a starting date for the first option and finally types a number that tells how far apart the options are, in days, weeks, or months.
- Using user-defined colors for each option in the loop attribute to display how the options spread out in both calendar and gantt lists, with a switch to show/hide.
- The automation part is able to track all tasks using this attribute and flag them with the appropriate option according to the task status attribute ONLY. Once the loop has exhausted all options it, well, loops back to the first option.
- Users can design 1 or several loop type custom attributes according to their needs, but can only display one at a time in calendar and gantt lists.
Current date: July 8, 2022. In the settings menu, I create a new custom attribute of type “loop” and name it “Sprint”, add 3 options named “Sprint 1”, “Sprint 2”, and “Sprint 3”. Each option has its own custom color. I set the starting date to July 10, 2022 and type “5 days” as the space between options. I then open a list of type calendar, click a checkbox to reveal Sprint, and immediately get date boxes colored according to sprint options, with Sprint 1 colored from July 10 to 14, Sprint 2 from 15 to 19, etc. I then flag several tasks with the Sprint attribute, all of them are automatically assigned the Sprint 1 option until July 14. Any task still active by July 15 is automatically moved to Sprint 2, and so on without any action on the user’s part.
Current date: July 8, 2022. In the settings menu, I create a new custom attribute of type “loop” and name it “Quarter”, add 4 options named “Q3”, “Q4”, “Q1” and “Q2” in that order. Each option has its own custom color. I set the starting date to July 1, 2022 and type “3 months” as the space between options. I then open a list of type gantt, click a checkbox to reveal Quarter, and immediately get date columns colored according to Q options, with Q3 starting from July 1 to September 30, Q4 from Oct 1 to Dec 31, etc. I then flag several tasks with the Quarter attribute, all of them are automatically assigned the Q3 option until Sep 30 where any task still active by the next day is automatically moved to Q4, and so on without any action on the user’s part.
In closing (I promise)…
Weekends and holidays should be handled accordingly. Some of these scenarios are standard across multiple use-cases and can be fully baked in the app, that means the user is simply given a checkbox to load the feature or not. But, as I have come to notice and appreciate in Height app approach, giving the user full custody of their preferences, as suggested in the scenarios above, is a really unique and powerful proposition.