Home / Documentation / Release notes 4.10

Release notes 4.10

iObeya 4.10 (Cloud version) • Released in May 2022

Improvements

iObeya Core

  • IOBPDT-1283 - Allow bulk edit permissions on rooms in the platform administration interface validation issues on platform upgrade
  • IOBPDT-1331 - Assign roles when adding users to a room in the platform administration interface
  • IOBPDT-1935 - Board settings contextual menu has been reorganized to make it easier to change the backgrounds and access the main settings
  • IOBPDT-2113 - New PPT files to make customized backgrounds downloadable from the Platform
  • IOBPDT-2199 - Reduce time to migrate and to bootstrap iObeya when upgrading to a new version
  • IOBPDT-2270 - Board backgrounds catalog now includes 2023 calendars
  • IOBPDT-2309 - Allow room admin to add a new group from LDAP
  • IOBPDT-2333 - Keeping the links between board elements while transforming notes into cards
  • IOBPDT-2339 - New whiteboard icon in the room configuration view

Agile

  • IOBPDT-2347 - Correct spelling mistake on the Portfolio Canvas board background: KPIs instead of KPI’s

Azure DevOps connector

  • IOBPDT-2251 - Having the links sorted in alphabetical order in the Azure “‘Configure links display” tab

Jira connector

  • IOBPDT-2251 - Have the links sorted in alphabetical order in the Jira “‘Configure links display” tab
  • IOBPDT-2283 - Having a message informing users that their cards will be updated while activating the display links toggle
  • IOBPDT-2330 - Having a scroll bar on the Jira description field in a Jira card
  • IOBPDT-2346 - While creating a Kanban Board, display a warning message when a user selects one or more projects which have a draft workflow scheme

QCD

  • IOBPDT-2269 - Having the ability to see and select non-QCD boards from the action table when you select the mode “All rooms”
  • IOBPDT-2268 - Having the ability to escalate actions even if no letter is assigned to the action card
  • IOBPDT-2379 - A message has been added to “Actions QCD” to warn users about limitations that they might face in viewing actions, as it depends on the permissions that have been assigned to the user
  • IOBPDT-2443 - The QCD board has now been included in the standard “new board creation” workflow
  • QCD-3354 - Improvement of escalation notifications display time and notifications deactivated by default
  • QCD-3364 - Saving escalation settings in room parameters was slow and timed out frequently
  • QCD-3365 - Loading QCD action plans with many actions was slow and is much faster now

DCM

  • IOBPDT-2444- The DCM board has now been included in the standard “new board creation” workflow

Bug fixes

iObeya Core

  • SUPIOBEYA-18025 - Exception LoopPath when exporting a board in ZIP format
  • SUPIOBEYA-18640 - After downloading a planning board, the elements in the empty zone disappear

Azure DevOps connector

  • SUPIOBEYA-17861 - On the bulk import the card title is cut when there is a “|” sign
  • SUPIOBEYA-17863 - An exception occurs while using the exchange zone to move Azure cards from a blank board to an Azure board
  • SUPIOBEYA-18189 - Connexion issues between Azure and iObeya on huge projects with a lot of sublayers

Jira connector

  • SUPIOBEYA-17917 - In the bulk import view, impossible for users to have access to the issues in the tab 2
  • SUPIOBEYA-18196 - An exception occurs in the bulk import when a user selects an issue to import on the board
  • SUPIOBEYA-18228 - An exception occurs when using the filter tool
  • SUPIOBEYA-18371 - The research of epic link in the card editor does not work if the project key is composed of a non [A-Z] character

QCD

  • SUPIOBEYA-18048 - The indicators could not be modified in bulk if the selected time period of the board did not contain the current date
  • SUPIOBEYA-18049 - There was a problem of performance slow down and timeout issues when the time periods were changed which was due to a large of history data being stored
  • SUPIOBEYA-18095 - The action table was not getting updated when a board or room was imported
  • SUPIOBEYA-18131 - There was an error in the logs when exporting QCD boards with letters without the property letter groups set
  • SUPIOBEYA-18192 - The search by ID in the action plans was no longer working on entering part of the action ID, although, worked only if the whole action ID was entered.
  • SUPIOBEYA-18273 - The actions that were closed could be seen on the action tables
  • SUPIOBEYA-18274 - In mode 3, “All types“ of QCD actions, although the filter of “closed actions” is inactive yet the user was able to see all the closed actions on the action tables
  • SUPIOBEYA-18298 - During indicator set up in a letter, the threshold name was not being shown correctly, Threshold 2 was being seen as Threshold 1 in case of letters with 2 or 3 circles
  • SUPIOBEYA-18333 - The problem was that the user was not being able to transform an action into an action card by clicking on the edit button in action plans, the reason being that the actions were not linked to the right letter
  • SUPIOBEYA-18358 - When read-only users entered a board with auto-consolidation running, the consolidation was getting blocked 
  • SUPIOBEYA-18376 - When a board was shared and the time period was changed, it caused the QCD add-on to hang
  • SUPIOBEYA-18463 - When exporting/importing a board an exception “Card has no master“ was being raised
  • SUPIOBEYA-18503 - When the user wanted to specifically view an action linked to a specific day of the letter the result showed the whole list of existing actions associated with the letter