Release notes 4.13

iObeya Core

• IOBPDT-1480 - Provide the capability to share room templates across multiple domains to create new rooms from it
• IOBPDT-2201 - Multiselection - let users make a selection frame even when it starts on a non-selected element
• IOBPDT-2253 - Add a new domain setting allowing room administrators to archive their room
• IOBPDT-2256 - Provide a better user experience when importing rooms via the platform admin interface
• IOBPDT-2486 - Increase the number of characters to 25 in the Standard card value
• IOBPDT-2499 - Add a news center in the product to access product news without leaving iObeya via a new sub-processor add-on using Beamer
• IOB-13646 - Provide all the add-ons packaged and disabled by default in iObeya
• IOB-14172 - The order in the list of language should be the same everywhere
• IOB-14344 - Grant only 'can use' permission as the default permission when adding groups to a room from the platform administration interface
• IOB-14347 - Add new screenshot parameters in the context file to fine tune the performance of the platform
• IOB-14364 - Improve performance of the LDAP sync step Get User Changes 
• IOB-14385 - Add a new screenshot parameter in the context file to deactivate system screenshot generation
• IOB-14425 - Skip invalid usernames when importing LDAP groups in iObeya so that the the users import process is not stopped and blocked
• IOB-14585 - Add a new screenshot parameter in the context file to disable the action to force board screenshots to be refreshed after a platform update

Azure DevOps

• IOBPDT-2236 - Display the sprint dates automatically in the ADO sprint tables
• IOBPDT-2359 - Alphabetically sort the list of domains when configuring a new ADO instance
• IOBPDT-2519 - Increase contrast of the board background of ADO table in compliance with our accessibility guidelines

Agile

• AOS-230 - Increase contrast of the board background for new Program Boards in compliance with our accessibility guidelines

Jira connector

• IOBPDT-2236 - Display the sprint dates automatically in the Jira sprint tables
• IOBPDT-2254 - Loader - Remove loader when changed issue in Jira card creation pop-in
• IOBPDT-2359 - Alphabetically sort the list of domains when configuring a new Jira instance
• IOBPDT-2401 - Being able to see the configuration settings in read-only mode of a existing Jira board
• IOBPDT-2519 - Increase contrast of the board background of Jira sprint table & Jira free table in compliance with our accessibility guidelines
• IOBPDT-2626 - Take into account major changes introduced in Jira regarding Epic Links being replaced by Parent Links (4.12.1)

QCD

• IOBPDT-1883 - Display values on the QCD graphs
• IOBPDT-1952 - Provide more precision on the vertical axis of the QCD charts
• IOBPDT-2075 - Display decimals on axes of the QCD Charts
• IOBPDT-2353 - Allow to display decimals on Y-axis of QCD Charts depending on the scale of the min/max values
• IOBPDT-2430 - Improve QCD problem category filter by adding a search bar in the Action card editor
• IOBPDT-2463 - Optimisation of frontend API calls on the QCD Action Cards
• IOBPDT-2534 - Move min-max scale settings into the general settings of the QCD graphs
• IOBPDT-2577 - Create a configuration Toggle on/off for escalated actions displayed via the action table mode 3
• QCD-3355 - Enhance Tree creation in action table mode 3 editor and /actionTable endpoint performance

API / Integrations

• IOBPDT-2660 - [CLOUD - FACADE API] Provide a  dedicated endpoint to extract all QCD actions from a platform
• IOBAPI-196 - [CLOUD - FACADE API] Provide new POST endpoint to Update Period of a QCD board 
• IOBAPI-254 - [CLOUD - FACADE API] Provide GET - Card Activity - Area in the /cards endpoint
• IOBAPI-263 - Add a shortcut in the detailed information contextual menu on board element to copy the element ID to facilitate data mapping during integration projects
• IOBAPI-264 - [CLOUD - FACADE API] Provide PUT Gauge endpoint to update an existing Gauge value
• IOBAPI-293 - [CLOUD - FACADE API] Add the hyperlink url and label into the response of the /cards endpoint

 

iObeya Core

• SUPIOBEYA-18958 - Update the algorithm of placing out-of-box elements inside the board when rotating elements
• SUPIOBEYA-18962 & SUPIOBEYA-19736 - It’s not possible to download room metrics report from the platform administration interface
• SUPIOBEYA-19470 - Impossible to remove a user from a group from the detailed information panel available in the user list
• SUPIOBEYA-19504 - The hyperlinks leading to the administrator documentation available on the homepage of the platform administration are broken
• SUPIOBEYA-19525 - Archived date of archived rooms is deleted 30 days after the rooms have been archived
• SUPIOBEYA-19648  & SUPIOBEYA-19647 -  AggregateDoesNotExist exception error message on various interactions with board elements after creating a room from a room template
• SUPIOBEYA-19817 - Uncaught (in promise) Error: consolidateLetterIds need not be empty on various scenario when using QCD consolidation on today or yesterday period
• IOB-13533 - Guiding navigation stop working when navigating to a board on a platform with a URL starting with some specific keywords
• IOB-14010 - The undo/redo stack should be reset once context is changed on Kanban board
• IOB-14075 - Exception on incompatible multi-touch behavior
• IOB-14223 - On the reset password page several separators are missing between items in the list of languages
• IOB-14346 - ERROR [IntegrityCheckJob] Error user check when upgrading iObeya version with a number of declared users that ends  by 99 (e.g 1099, 10099, 56499)
• IOB-14404 - Editing a background with multiple categories from the platform administration interface erase the background version
• IOB-14451 - TypeError: Cannot read properties of undefined (reading 'offsetX') generated when editing the room

Azure DevOps connector

• SUPIOBEYA-18122 - iObeya Read-only user see a notification message “You are not connected to ADO” when they enter a board/room even if they still have a valid ADO PAT token
• SUPIOBEYA-18435 - The AzureDevOps instance URL overflows when the URL is too long in the dropdown list of ADO instance in the room settings
• SUPIOBEYA-19874 - The TFS card imported into a TFS Kanban from the ExchangeZone does not return to its initial place if it is moved in a status column that is not authorized by any transition flow
• SUPIOBEYA-20042 - Opening the ADO card editor takes too much time to display the information
• TFS-387 - A message should be displayed when the mouse hover the button "Create work item" when user does not have required permissions
• TFS-440 - The name of toolset item in the dock is displayed incorrectly if the TFS project has a long name
• TFS-446 - The link between TFS cards that are on a whiteboard doesn't appear on the Board Preview tool
• TFS-449 - When updating the status of an ADO card by moving it to another column on a ADO kanban board, the the status is changed in ADO after the push but the status displayed on the card is not updated
• IOBJIR-1072 - Missing margin below the text description on the ADO and Jira board creation pop-in

DCM

• SUPIOBEYA-20121 - The two templates files to import data are missing from the DCM documentation resulting in dead links
• SUPIOBEYA-19892 - New DCM sequence added to the board may not appear until another element is moved or the page is refreshed

Jira connector

• SUPIOBEYA-19199 - The push indicator on a Jira card with pending modification should not be kept when moving the card to another board via the Exchange Zone
• SUPIOBEYA-20501 - All Jira cards on a board are marked as “deleted in Jira” if a single Jira issue that is on the board has been deleted in Jira
• IOBJIR-1055 - iObeya Read-only user see a notification message “You are not connected to Jira” when they enter a board/room even if an Jira OAuth token is valid
• IOBJIR-1102 - Remove default message "No results matching" when opening the Jira card tool from the tool dock and no search as been made
• IOBJIR-1109 - The links between Jira cards that are on a whiteboard doesn't appear on the Board Preview tool
• IOBJIR-1118 - The margin is missing on each side of the message displayed when no results are returned by a search in the Jira card tool
• IOBJIR-1124 - TypeError: Cannot read properties of undefined (reading 'displayDeactivated')

QCD

• SUPIOBEYA-19433 - High latency to see data updates on QCD charts and tables
• SUPIOBEYA-19274 - Improve performance of retrieving historical data of QCD to avoid errors
• SUPIOBEYA-19461 - The username displayed in the feedback is not the good one when adding a QCD action table or adding a QCD action card to the board
• SUPIOBEYA-19884 - QCD Actions tables are not updated correctly after updating to 4.12
• SUPIOBEYA-20270 - Screenshot of some QCD boards with QCD charts and tables take longer time to be generated leading to high CPU pick and waiting screenshot queue
• QCD-2246 - When editing a QCD card from My cards view no escalation notification should appears as we are not into any specific room
• QCD-2340 - The focus is not placed at the top of the list when switching between pages in the QCD action plan
• QCD-3508 - The board period is not correctly updated on a weekly QCD board when using the API endpoint /boardperiod 
• QCD-3511 - Impossible to move a new QCD action table created on a board without refreshing the page
• QCD-3512 - QCD action that has been escalated remains listed on QCD action table mode 2 even if the escalation level is removed
• QCD-3513 - The due date of QCD cards displayed in the shortcut to change it from the contextual menu is incorrect
• QCD-3514 - The synchronization indicator remains displayed on QCD action card even after deleting the last synchronized copy from a collection
• QCD-3516 - On QCD shared boards permissions are ignored in some cases allowing users to edit QCD actions from the destination room via the Action table component
• QCD-3524 - Exception error QCDGetEscalatedActionsCountServlet appears in the log when escalated actions came from a room that has been archived
• QCD-3529 - QCD actions are deleted from the source board after removing the shared board from the destination room