Release notes 4.8 (On-prem)

Improvements

iObeya Core 4.8.6

• IOBPDT-148 - Provide bigger boards for the Agile add-on
• IOBPDT-510 - Provide whiteboards in portrait format
• IOBPDT-685 - Add more information to the room list in the administration interface
• IOBPDT-718 - The clickable iObeya logo on the change password page should redirect to the application
• IOBPDT-842 - Be able to filter users by the group in the user’s list
• IOBPDT-1214 - Being able to modify the login of a local user with the bulk import functionality
• IOBPDT-1280 - Display archive date in the rooms & domains views in the administration interface
• IOBPDT-1288 - Display if the archive date of a room is inherited from the domain
• IOBPDT-1328 - New border on activity cards to easily differentiate them
• IOBPDT-1378 - Having a predefined order in the collections of cards
• IOBPDT-1348 - Note to Card transformation
• IOBPDT-1422 - Better synchronization of archive date between domains and rooms
• IOBPDT-1478 - Have an “Assign / Send-to myself” action on cards
• IOBPDT-1532 - Being able to make bulk changes to a list of users while using the bulk import 
• IOBPDT-1540 - Provide bigger boards for planning boards
• IOBPDT-1583 - Allow platform administrator to edit the login of the users
• IOBPDT-1607 - Fix some typos in the board background catalog
• IOBPDT-1928 - Display the last visited boards on the homepage instead of the most visited boards
• IOBPDT-1930 - Accessibility - Popin component should only have 1 cancel and 1 save button
• IOBPDT-1937 - Board background has been graphically refreshed in accordance with WCAG recommendations
• IOBPDT-1980 - Provide bigger boards for kanban boards
• IOBPDT-2009 - Customized content of the email templates should not be reset after a restart or an upgrade
• IOBPDT-2042 - iObeya favicon updated
• IOBPDT-2135 - Provide bigger boards for the whiteboards
• IOBPDT-2136 - Accessibility - Review the design of generated boards to increase contrast and legibility
• IOBPDT-2143 - Calendar 2022 added to the templates available in the iObeya catalog
• IOBPDT-2202 - Check the private key when configuring a new instance of Jira to avoid validation issues on platform upgrade
• IOBPDT-2218 - A new user-friendly message on the license expiration banner
• IOBPDT-2270 - Add 2023 calendars to the board background catalog (4.8.5) 
• IOBPDT-2274 - Improvement on invitation email content for new accounts to facilitate new user onboarding
• IOBPDT-2332 - Display a message informing users that they will lose the links while transforming notes into cards
• IOBPDT-2435 - Correct typo in SWOT Analysis board background (4.8.5) 
• IOBPDT-2450 - Correct typo in persona board background (4.8.5) 
• IOB-14364 - Optimize LDAP connector sync STEP 7 checking for user modifications to reduce duration time and risk of impact on the platform activity (4.8.5) 

Agile add-on 4.8.0

• IOBPDT-1568 - Add more sprints in the SAFe Boards
• IOBPDT-2046 - Being able to use values higher than 10 in the feature card WSJF field 
• IOBPDT-2060 - Having more than 99 story points in story cards

Azure DevOps connector 4.8.4

• IOBPDT-1709 - Being able to organize work items by state with an Azure DevOps Kanban board
• IOBPDT-1718 - Being able to choose which ADO dependencies to display on a board
• IOBPDT-1978 - Provide bigger boards for Azure DevOps Add-on
• IOBPDT-2065 - Render the HTML content in the workitems description field to make it legible while editing an ADO card
• IOBPDT-2150 - New select all components for rows and columns in board creation
• IOBPDT-2301 - A better management of classification nodes (area and iteration path nodes)
• IOBPDT-2319 - Do not scramble Azure cards on an Azure Sprint board when they are already on the correct cells after a platform upgrade, a board import, or a board duplication

Jira connector 4.8.6

• IOBPDT-1704 - Create and edit Jira links and dependencies directly from iObeya
• IOBPDT-1924 - Possibility to create more than 11 rows in a JIRA board
• IOBPDT-1979 - Provide bigger boards for Jira add-on
• IOBPDT-2029 - Being able to link Epics and User Stories in the Jira card 
• IOBPDT-2150 - New select all components for rows and columns in board creation
• IOBPDT-2167 - Long Jira issue ID is not fully displayed on the Jira card
• IOBPDT-2275 - iObeya is compatible with Jira Data Center 8.13
• IOBPDT-2326 - Do not scramble Jira cards on a Jira board when they are already on the correct cells after a platform upgrade, a board import, or a board duplication
• IOBPDT-2484 - Remove the API calls made when a user drag and drop a Jira card on a board

QCD 4.8.7

• IOBPDT-1875 - Having more information regarding the sources from a consolidated indicator
• IOBPDT-1974 - Add min & max operators to the global consolidation parameter
• IOBPDT-2069 - Being able to export all QCD actions of a room
• IOBPDT-2073 -  Increase the number of escalation levels that can be configured in a room to 100 
• IOBPDT-2106 - Ability to select the box to valorize in the "Input of Indicators" interface for custom cut-out letters
• IOBPDT-2107 -  Be able to consolidate values stored in a daily custom cut-out letter
• IOBPDT-2120 - New min & max operators on the consolidation formula editor in QCD 
• IOBPDT-2129 - Ability to select the box to valorize in the "Input of Indicators" interface for temporal  cut-out letters
• IOBPDT-2360 - Match the QCD API documentation with the business object actions
• IOBPDT-2577 - Create a configuration Toggle on/Toggle off for escalated actions displayed via the action table mode 3
• 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 were slow and is much faster now

Bug fixes

iObeya Core 4.8.6

• SUPIOBEYA-6809 - Customized email templates are reset after a server reboot
• SUPIOBEYA-16335 - Exceptions may occurs ramdomly when saving room settings on an unstable network connection
• SUPIOBEYA-16552 - Board background catalog spelling Error on "FeedbackS"
• SUPIOBEYA-16648 - Emojis in board title and board content are lost when importing a board export in a room
• SUPIOBEYA-16935 - The first month of a planning board is doubled
• SUPIOBEYA-19690 - LDAP group sync job should not stop to sync all users when a group contains a username with a special character and should only skip the concerned username (4.8.6)

Agile 4.8.0

• SUPIOBEYA-16630 - An error occurs when importing a Team board in another room that doesn’t have a Program Board

Azure DevOps Connector 4.8.4

• SUPIOBEYA-16897 - It’s not possible to find and import an Azure card when the search result returns more than 1000 work items because the result set is not ordered by Workitem ID
• SUPIOBEYA-17843 - Shared queries including data using a tree structure in ADO do not return any results in iObeya
• SUPIOBEYA-17863 - An exception occurs while using the exchange zone to move an Azure card from a blank board to an Azure board 
• SUPIOBEYA-18189 - Connexion issues between Azure and iObeya on huge projects with a lot of sublayers
• SUPIOBEYA-19518- The Team field retrieves only 100 results
• SUPIOBEYA-19857 - On the Azure tables when clicking on ‘Update all cards’ the browser crashes with an error message: Out of Memory

Board Preview  add-on 4.8.1

• SUPIOBEYA-17130 - Board Preview documentation link embedded in the application leads to a 404 error page

DCM add-on 4.8.3

• SUPIOBEYA-17716 - Change type action on DCM board generates errors and avoid changing the type of DCM notes

Jira Connector 4.8.6

• SUPIOBEYA-15631 - After transforming a story card into a Jira card, the JIRA card is not associated with any toolset item
• SUPIOBEYA-18332 - In the card editor, the “Epic link” field displays only the last 50 modified values
• 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
• SUPIOBEYA-18456 - Limit of 100 results returned on the Jira team field which prevents users from being able to select their team when they create a Jira board
• SUPIOBEYA-18883 - While dragging and dropping a Jira card, he execution  takes more than 20 seconds 

QCD add-on 4.8.8

• SUPIOBEYA-15557 - Suggest an action on binary indicators doesn’t work
• SUPIOBEYA-16192 - Consolidation remains blocked when accessing aboard
• SUPIOBEYA-16490 - Shift between the period area selected in the menu and the period selected in letters
• SUPIOBEYA-16590 - Consolidation loading issue when you have a formula with an integer not filled in
• SUPIOBEYA-16935 - The filter on the board name does not work in the QCD action plan view
• SUPIOBEYA-16989 - Screenshots of the QCD board generates an error when it contains a letter with all the box disabled
• SUPIOBEYA-17161 - Consolidation is blocked when a user without editing rights accesses a board with automatic consolidation enabled
• SUPIOBEYA-17232 - The indicator value was not saved
• SUPIOBEYA-17372 - When using the indicator update service (/indicator value), the letters are updated but not the associated elements: tables and graphs.
• SUPIOBEYA-17509 - QCD API returns duplicated indicators values on objects and requires to specify 2 times for the indicator to be used when creating a QCD action
• SUPIOBEYA-17572 - Board may get stuck while changing the time window of a QCD board to view historical data
• SUPIOBEYA-17798 - Following the upgrade to 4.8 some letters with consolidation are not editable
• 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-18153 - The indicators that have been deleted are still considered in the calculation of the consolidation and block the total consolidation of the letter
• SUPIOBEYA-18192 - The search by ID in the action plans is no longer working with partial ID references and only works if the full ID number is 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-18501 - Issue with the sort by in action plans
• SUPIOBEYA-18503 - Actions from other periods are displayed when filtering by wedgeNumber
• SUPIOBEYA-18909 - QCD escalation not working in a specific room