3 New Features • 17 Improvements • 29 Bugfixes

🌟 New Features

(1) Use Flavors in Status Reports & New Flavor Type "Status"

The status report can now be customized further using Flavors.

Use Flavors in Status Reports

You can now create any number of Flavor groups in status reports and add any Flavor types to the status report template. This allows a status report to be customized beyond the standard text fields.

Steps:

1. Create a new status report draft
2. Enable the Flavors section
   
   
   
   
3. Add any Flavors and/or Flavor groups as needed, and optionally use the new Flavor type Status (see below).
   
   

We recommend saving these customizations directly as a status report template. 

Use Status Flavors in Portfolio Views

In portfolio views, Status Flavors can be displayed as columns. However, they must first be assigned the Status Reports context. To do this, go to the Flavor configuration and select Context > Status Reports. 

Once you have assigned the context to the Flavor, the portfolio list can interpret and display its values. When adding it as a new column, these new Flavors will be listed under a separate section for the Status Report context:

Flavors assigned with the Status context will be marked with an "S" in parentheses in portfolio lists:

New Flavor Type "Status"

If the default fields for project status (Overall Status, Schedule Status, Cost Status, Goal Status) are not sufficient, you can now add custom statuses in the Flavor table within status reports using the new Status Flavor type. This Flavor behaves similarly to a standard selection field but has built-in traffic light colors. Status names can be customized, and additional statuses can be added in neutral colors.

(2) Conditions for Flavor Value Validation (Beta)

Most Flavor types now include a new option called Define Condition, which allows for custom validation of input values.

 

The condition must be defined as an expression in the Condition text field. The syntax and capabilities are similar to the formula editor used for Formula Flavors.

 

 

The Validation description field allows defining the tooltip text for validation errors. A red exclamation mark will indicate a validation issue. However, saving the value or setting the status to completed will not be prevented. 

 

 

Note

This feature is still in beta. The core functionality is fully available, but in the future, defining conditions will be made more user-friendly with a formula editor. 

 

 

(3) Define a Context for Flavors

Until now, Flavors were universally applicable custom fields that could be used in project master data, tasks, time entries, people, and now also in status reports.

However, it was not previously possible to display Flavor values in "non-contextual" list views. For example, in the time evaluation list, only Flavors from the time tracking context could be displayed.

From now on, it is possible to assign a specific context to Flavors, allowing them to be displayed in "non-contextual lists" as well 🤝

Example: Time Evaluation

In the time evaluation view, associated Flavor values from other contexts can now be displayed. The screenshot shows a value labeled (P), which is from the project master data of the project to which the time was logged—here, the priority. The label (Pe) indicates a value from the personal master data of the person who logged the time—here, their deputy.

Possible Contexts:

• No Context (all previous Flavors had no context)
• Status Reports
• Tasks
• Projects
• People
• Times

🌟 Improvements

• Shortcut for time tracking: Using the shortcut CTRL + ALT + T directly opens the dialog for recording a new time entry, from anywhere in the software.
• Open views in a new tab: Any view can now be opened in a new browser tab via the Views menu > Three-dot menu > Open in new tab.
• Sorting adjusted in time tracking dialog: The sorting of time tracking entries in multi-time tracking (week/day view dialog) is now alphabetical, first by project title and then by task title.
• Changes in time evaluation tables without reloading: Changes to individual time entries in the Times or Time Evaluations list views are now applied without requiring a page reload in the background.
• Stabilized remaining time calculation in the portfolio list: In the project list, a field for the remaining project duration is displayed by default. Now, project end dates far into the future can be entered without affecting the portfolio list's performance.
• Exporting teams: Authorized roles can now export teams via (Settings > Teams > Export button). The export includes team names and members, along with their names and email addresses. 
  
• The task context menu has received two new options system-wide:
  • Log time: Opens the multi-time tracking window (which can also be opened using the shortcut CTRL+ALT+T). A new row for the project/task combination is automatically added.
  • Favorite for time tracking: The project/task combination is saved as a new favorite row in time tracking for future use:
    
    
• More configuration options for labels: Labels can now be better configured, for example, by restricting editing permissions. Additionally, the button in the context menu Remove label has been renamed (formerly Delete label). Labels can now only be permanently deleted via the configuration menu, preventing accidental deletions.
  
  
  
  
  
• Formula editor expanded with functions for cube root and exponents: pow(base, exponent) and cbrt(number) can now be used in formulas.
• Updated status history widget: Previous status reports are now directly clickable within the widget:
  
  
  
  
• Extended bulk moving of tasks (time-wise):
  The options for bulk time shifting have been expanded. Additionally, users can now manually define the number of days by which tasks should be shifted. 
  
  
  
  
• Work schedules can now have a start and end date:
  With the appropriate HR permissions, work schedules in user profiles can now include a start and end date. If changes occur, work schedules will be historically tracked and correctly considered in workload views for past periods.
  
  
   
• API enhancements:
  
  • • Locking time entries: 
      • New field locked in the API endpoint /timerecords: Allows locking a specific time entry. The tag accepts true or false, for example:

        <TimeRecord>
           <Id>681c88a0-5890-4c3b-b799-812fa860252e</Id>
           <Locked>true</Locked>
        </TimeRecord>

        In the user interface, locked entries can no longer be edited or deleted. The lock status can be displayed in the Lock Status column in time evaluations.

        The lock status can only be set via the API. The API does not modify entries when Locked = true, unless Locked is explicitly set back to false via the API in the same request that modifies the data.

    • New endpoint to retrieve flavors: /api/Reports/flavors and /api/Reports/flavors/excel allow retrieving all used flavors (custom fields) in the workspace. The flavors are output with their type and name.
    • New endpoint for restoring archived projects:  A POST request to /api/Integration/project/unarchive/{projectId} (without an XML body) can restore projects from the archive.
    • Extended /project endpoint: The optional Currency field is now available. If not specified, the default currency remains EUR, as in the user interface. Allowed values: "EUR", "USD", "CHF", "CAD", "GBP", "AUD".
    • Implemented DELETE functionality for multiple endpoints, e.g., for the /task endpoint. Example: 
      

      DELETE https://{customerSubdomain}.smenso.cloud/skyisland/api/integration/task/{id}

🐛 Fixes

• The feed widget in projects now displays specific messages for activities older than three months, informing users that activities can still be accessed via activity logs. Previously, the message was misleading.
• Adjusting the table width in the Time Tracking section of task details now behaves more precisely:
  
  
  
• Removing a relation flavor value (if it was the last one in a cell) previously disabled new value input. This is now fixed.
• Fixed an issue where changing the color of holidays was not saved correctly.
• The default view and arrangement of status report widgets have been improved.
• Various bug fixes for exports:
  • When exporting task lists, columns sorted in the view were not exported—now fixed.
  • Decimal places were sometimes lost during export—now fixed.
  • Sorting by a persisted formula flavor (number) did not work correctly—now fixed.
  • When exporting task lists via the /project endpoint, formula flavors with the fromParent tag were not exported correctly. The formula is now properly resolved.
  • When exporting formula flavors that display a button, the button title is now exported as text if the button column is included in the export.
• Various fixes for moving tasks in the Gantt view, such as bulk-moving tasks, including those with multiple hierarchy levels, or extending/shortening parent tasks. Subtasks and lower-level tasks are now unaffected when the parent task is extended.
• Favoriting project-independent views, such as portfolio views, was only possible if at least one project view was also saved as a favorite. This is now independent.
• Fixed a permission issue in bulk task editing where it appeared that restricted members could delete tasks in multi-selection mode. Although deletion was not actually executed, the UI incorrectly suggested that it was possible. This is now fixed.
• Corrections in the absence list, which previously did not behave correctly in some cases.
• Fixed an issue with grouping by calendar weeks in the Times and Time Evaluations list views. Some entries were incorrectly assigned to calendar weeks.
• Various bug fixes for importing data via API:
  • Importing tasks with multiple hierarchy levels via the API resulted in incorrect storage of sub-tasks—now fixed.
  • When importing absences via the API (using the /absence endpoint), public holidays were sometimes incorrectly considered—now fixed.
  • When creating a new project with the isPrivate tag, no user was sometimes assigned permissions, preventing access. This is now fixed, ensuring that the user who creates the private project via the API is always granted at least one permission by default.
• Email notifications are now only sent once when a person is notified both through assignment and via an @mention.
• Various snackbar message corrections.
• When duplicating tasks with multiple subtask levels in task lists, the subtasks initially appeared to not be duplicated. They are now immediately visible without requiring a refresh.
• When deleting tasks, these actions are now displayed in the project log (feed). The visibility of the restore option has also been stabilized.
• Fixed a display issue in the project master data widget when using long names for locations, project types, or project folders.
• Buttons (formula flavors using the "Button" function) were initially not displayed correctly as buttons in task details.
• In time tracking (multi-time tracking), marking a row as a favorite was possible even when only a project was selected, without an associated task. This led to an invalid entry. Now fixed.
• When setting a subtask to completed within a parent task, the subtask’s status was displayed incorrectly in detail views if a non-standard workflow was used. This behavior is now corrected.
• When using list widgets that display various list information, the contexts of lists and columns were sometimes not correctly loaded and displayed. List widgets have been further refined and improved.
• Using project master data flavors in a rich text field of a status report (via the "Label" button) sometimes did not work. Depending on various conditions, the menu failed to open. This is now fixed.
• When shifting tasks in bulk processing, some options resulted in not only a time shift but also an unintended extension of task durations. This is now fixed.
• The time recording dialog in the task detail no longer displayed necessary information in case of multiple entries - now fixed.

[Update 07.02.2025] 

• Creating duplicate Flavors with the same name is now prevented for security reasons.
• Inserting Flavors with a project master data context in a portfolio list resulted in incorrect display - fixed.
• Bulk-moving tasks from one project to another temporarily stopped working - fixed.
• The date filter in the My Times and Time Analysis lists did not work correctly at times - fixed.
• Flavors in time entries that were locked via the API were sometimes still editable - this is now correctly prevented.
• Time tracking: Adjusted dialog behavior when projects in already saved time entries are changed again.
• Loading times for the My Times and Time Analysis lists have been significantly improved. 
• When changing a multi-grouping that grouped by at least two fields back to a single grouping, the change could not be saved in a view. The save was ignored, and the multi-grouping by two fields persisted - this behavior has been corrected.
• When applying task templates via bulk processing, Flavor groups and values appeared to be randomly sorted and arranged - this behavior has been corrected so that the task template is applied 1:1 to the tasks.