Release notes for version: 10.14.0
Please read before upgrading to platform version 10.14.0.
All changes available as usual in the changelog.
Project flags – yellow flag is actually not displayed in yellow color
Before:
Project flags – yellow flag was actually not displayed in yellow color.
Now:
Fixed. The yellow flag is displayed in yellow color.
The task list also includes tasks from project templates
Before:
The task list also included tasks from project templates, which was not expected behavior.
Now:
Fixed. Tasks from project templates are not included in the task list.
An empty e-mail section appears when adding an attachment to a task
Before:
An empty e-mail section appeared when adding an attachment to a task, which was not expected behavior.
Now:
Fixed. The e-mail section on a task only appears when it's not empty.
Timesheets permissions inconsistency
Before:
A user who had permission to see only his own timesheets was able to see timesheets of other users.
Now:
Fixed. A user who has permission to see only his own timesheets is not able to see timesheets of other users.
The old Meeting calendar page module removed
Before:
It was possible to add the Meeting calendar page module to a customized page.
Now:
It is not possible to add the Meeting calendar page module to a customized page. It was removed and replaced by the Scheduler page module.
Resource Management: The resource allocator for reservations cannot be changed
Before:
Due to missing project permission, it was not possible to change the resource allocator on existing reservations. The new allocator was not saved.
Now:
Fixed. It is possible to change the resource allocator on existing reservations and the new allocator will be saved correctly.
The WBS menu position overlaps with the right service bar
Before:
The WBS menu position overlapped with the right service bar, making it impossible to read the menu items.
Now:
Fixed. The WBS menu position was changed to not overlap with the right service bar.
WBS: Cannot move a subtask
Before:
In WBS, due to an issue with the "One side" option, it was impossible to move a subtask as a standard task to a project.
Now:
Fixed. It is possible to move a subtask as a standard task to a project.
Task journals are not visible due to a bug in the EasySwagger function
Before:
Due to a bug in the EasySwagger function, task journals did not render properly if they were a part of an object, making them not visible when supposed to be shown.
Now:
Fixed. Task journals are visible when supposed to be shown.
Unable to create a link between an Account contact and a task
Before:
The "Add Task" option was missing from the More menu in the sidebar of a detailed Account contact view. At the same time, the "Add Account" option was missing from the More menu in the sidebar of a detailed task view.
Now:
Fixed. Both options are available and allow you to create a link between an Account contact and a task.
Unable to edit custom fields in the Budgets module using the inline menu
Before:
It was not possible to edit custom fields in the Budgets module using the inline menu.
Now:
Added the ability to edit custom fields in the Budgets module using the inline menu.
Resource Management not loaded/defined on the project level
Before:
Resource Management not loaded/defined on the project level when the applied filter included no tasks to assign.
Now:
Fixed. Resource Management loads on the project level correctly even when the applied filter includes no tasks to assign.
Problem with the Total allocation chart in the Resource Dashboard
Before:
There was a problem with the Total allocation chart on the Resource Dashboard, which did not display a description when hovering the cursor, but instead displayed errors in the console.
Now:
Fixed. The Total allocation chart in the Resource Dashboard shows the description correctly after hovering the cursor.
Design issue in the dark theme of the Gantt's chart
Before:
Design issue in the dark theme of Gantt's chart – the contrast of black and white color in the header along with red stripes on the timeline.
Now:
Fixed. No issue.
Missing the "Activity cannot be blank" notification when creating a task without a required selected activity
Before:
Missing the "Activity cannot be blank" notification when creating a task without a required selected activity.
Now:
Fixed. When a task with a required selected activity to created without a selected activity, the "Activity cannot be blank" notification shows.
Private comments can be viewed in the task list
Before:
Private comments could be viewed in the Last Comment column in the task list by a user without the necessary permission to view other users' private comments.
Now:
Fixed. Correct visibility of private comments in the task list.
Not possible to add a related task to a project template
Before:
Adding a related task in a project template did not work due to a bug.
Now:
Fixed. Adding a related task in a project template works correctly.
Clicking on the filter name from the Budgets page module leads to a wrong page
Before:
When a user has set up a page module that tracked the "Portfolio Overview (tasks budget)" entity for a particular project and clicked on the filter name, the filter URL erroneously led to the global-level Portfolio Overview instead of the project-level Portfolio Overview.
Now:
Fixed URL to the project-level Portfolio overview.
Bugsnag error related to Easy Imports
Before:
Bugsnag error related to Easy Imports: Error in Stable – CLOUD **ArgumentError** in **easy_imports#import** wrong number of arguments (given 2, expected 0..1).
Now:
Fixed. No error.
Bugsnag errors related to Scheduler
Before:
Bugsnag errors related to Scheduler: LoadError plugins/easy_scheduler/lib/easy_scheduler/easy_gantt_resource_calendar_event.rb:1. No such file to load -- easy_calendar/easy_calendar_events/easy_calendar_event.rb
Now:
Fixed. No errors.
Bugsnag error related to EasyExtensions::Export::EasyVcard
Before:
Bugsnag error related to EasyExtensions::Export::EasyVcard – error in Stable: CLOUD **NoMethodError** in **users#show** undefined method `strip' for # "
Now:
Fixed. No error.
Bugsnag error related to CalDAV Outlook UID
Before:
Bugsnag error related to CalDAV Outlook UID: 40000008200 is out of range for ActiveModel::Type::Integer with limit 4 bytes
Now:
Fixed. No error.