Home / Documentation / Release notes 4.18

Release notes 4.18

iObeya 4.18 (Cloud version) • Released on 29th April, 2023

Improvements

iObeya Core

  • IOBPDT-2512 - Change the datatype of the email description to support more content when customizing email templates (4M+ characters)
  • IOBPDT-2743 - Make ''My Cards'' a permanent item on the main menu

Azure DevOps

  • IOBPDT-2361 - Allow to view collection items on ADO Cards with a read only user account
  • IOBPDT-2302 - Ability to use the priority field for importing and sorting on board via the bulk import

Jira connector

  • IOBPDT-2481 - Keep the iObeya visual link between 2 cards/notes when converting them to Jira cards
  • IOBPDT-2636 - Allow cards or notes to be transformed into EPIC by reusing the issue summary to populate the Epic name which is a mandatory field in Jira
  • IOBPDT-2701 - Change the card creation order when using the bulk-import so that the cards are imported in the order of the query, or the user selection
  • IOBJIR-1260 - Do not create separate groups on the board for linked issues when using the bulk import

QCD

  • IOBPDT-2315 - Introduce QCD lite mode for users with “edit only” permissions so that they can focus on their rituals using only essential features

DCM

  • IOBPDT-2761 - Reduce the loading time of the DCM task popup when there are a lot of elements in the backlog

Documentation

  • DOC-336 - Explanation of how to use the QCD Lite mode in iObeya

Bug fixes

iObeya Core

  • SUPIOBEYA-21422 - Changing card’s color rollback for a few minutes on few occasions and take longer time to be taken into account by iObeya
  • SUPIOBEYA-22216 - Application error triggered after room creation through template with synchronized cards
  • SUPIOBEYA-22296 - Application error triggered when editing Agile cards on a board without an Agile card toolset in the dock

DCM

  • SUPIOBEYA-20554 - Some ghost DCM tasks are no longer on a board but was still taken into account in the KPIs calculation
  • SUPIOBEYA-21642 - Import task in room parameters did not work if duration equals to 0 minutes
  • SUPIOBEYA-21804 - Unable to add a QCD action from a DCM task

Jira connector

  • SUPIOBEYA-19113 - An error is triggered by Jira when creating a Story from iObeya linked to an Epic and that the Epic issue type has been renamed in Jira
  • SUPIOBEYA-20499 - Button to access Jira board configuration panel was not localized in all supported languages
  • SUPIOBEYA-21742 - Error when creating a second card from the dock mentioning that the assignee field is not present on the screen configuration in Jira

QCD

  • SUPIOBEYA-19259 - Board was blocked when consolidation was launched, the bug has been corrected and a dedicated endpoint has been created to unblock the user in case the problem resurfaces again. A troubleshooting page has been created on the resource center for more information if the user encounters this problem again
  • SUPIOBEYA-21692 - Escalation Icon was not refreshed properly after modification when there is a lot of actions in the letter
  • SUPIOBEYA-21714 - When moving to trash or exchange area an escalated card in the escalation room, or importing actions, the escalation level is replaced by the ones defined in the escalation room
  • SUPIOBEYA-21746 - Concurrent edition of an action status may not be reflected on the action counter on a QCD letter and the action plan for instance.
  • SUPIOBEYA-22308 - When escalating an action by editing a synchronized card, the action is not appearing in action table showing the corresponding escalation level