Features​

OPT-1400 burnup performance enhancement​

Improved burnup graphics display performance.

OPT-1395 Product burnup improvement​

Product burnup more accurately represents product history.

OPT-1399 Sprint burnup improvement​

The graph displays the entire sprint duration and shows the sprint scope. The global scope has been removed so as not to disturb the reading of the graph. A guide has been added to follow the progress of the sprint.

OPT-1386 PDF “print” file name​

The file is named according to the PDF title.

OPT-1389 Export preference​

Export preferences are saved and reused for subsequent exports.

OPT-1390 Export file name​

The file is automatically named according to the product name.

Bugfix​

• OPT-1391 Remove “job started” toast.
• OPT-1392 Ignore existing emails
• OPT-1393 Display long accounts
• OPT-1404 Correct json parsing

Features​

OPT-1312 Improved task indicator​

The background tasks indicator displays the number of new events since the last consultation.

OPT-1325 Improved worklog analysis filters​

Added the ability to search for values in filters.

OPT-1328 Grouped user invitations & OPT-1327 User invitation enhancement​

Ability to invite several new users and improved interface.

OPT-1333 Improved product dashboard graphics​

Product dashboard graphics have been improved. A product burnup graphic has been added and the sprint graph can now be set to burnup instead of burndown. Burnup graphs can be set to choose the unit measured (number of items or ratings) and the duration and unit of the history (days, months, sprint).

OPT-1339 Item search enhancement​

Item search by reference now also works without prefix. When applicable, items from the same project are prioritized.

OPT-1347 Linked item enhancement​

By default, the latest modified items from the same project are presented first.

OPT-1365 Opening list item​

It is now possible to open the list of items from a kanban or product backlog column.

OPT-1373 Print settings​

Sub-items and evaluations can now be printed or not.

OPT-1374 Item export settings​

Ability to define exported columns.

OPT-1322 XLSX export enhancement​

Improved XLSX export formatting.

Bugfix​

• OPT-1324 UI Worklog filter problems
• OPT-1350 Default account too long
• OPT-1351 History not very explicit
• OPT-1361 Sorting bug with new search
• OPT-1362 Product deletion
• OPT-1363 SVG file bug
• OPT-1370 Untidy sub-tem printing
• OPT-1371 Ask estimate
• OPT-1372 Bug item lists
• OPT-1379 Epic (JS) deletion bug
• OPT-1387 Missing images PDF generation

Features​

OPT-1283 Printing backlog items​

A new feature for printing backlog elements is now available. It allows you to select backlog elements and generate a PDF. Document preparation is performed as a background task.

OPT-1203 Creation of backlog items from Storymap​

It is now possible to create backlog items from storymap items.

OPT-1284 Improved move to "to do" status​

When a backlog item is moved to "to do" status and an active sprint exists, Optera automatically places the item in the sprint.

OPT-1285 Account search​

A search by name has been added to account management.

OPT-930 Improve ask estimate​

Improved ask estimate option to take backlog sub-elements into account.

OPT-1294 Improved worklog display​

More understandable worklog display on backlog items.

OPT-1299 Product change on an item​

A new option lets you move a backlog item to another product directly from the backlog item page or modal.

OPT-1303 Enhanced description editing​

Added an edit button to enable editing of the backlog item description.

OPT-1308 Improved export + print buttons.​

The export and print options are automatically disabled if the number of selected elements exceeds the maximum allowed.

OPT-1310 Toast end of job​

A message informs of the end of a background job.

OPT-836 Return to top backlog​

When the sprint is closed, unfinished items that return to the product backlog are placed in first place.

Bugfix​

• OPT-1267 Some items cannot be quoted
• OPT-1270 Strange search results
• OPT-1278 Mark as read
• OPT-1279 Historical bugs
• OPT-1280 My dashboard items are in the wrong order
• OPT-1298 Unable to move an item to another project
• OPT-1306 Dashboard worklog history display

Features​

OPT-1247 Global search & navigation​

Optera now offers a global search from the search bar. This allows you to search not only for items, but also for products and organizations. This search enables rapid navigation between projects and items.

Features​

OPT-125 MFA​

Two-factor authentication with OTP. Compatible with mobile OTP applications such as FreeOTP or GoogleAuthenticator.

OPT-1002 Story Mapping​

Do story mapping in Optera. Create story maps for your entire product or a specific set of features.

OPT-1192 Time Budget Management​

Manage time budgets on time entry accounts and alert when a configurable threshold is exceeded.

OPT-1139 Tag enhancement​

Improved tag field for simplified entry.

OPT-1164 Product list enhancement​

The product list allow to archive products no longer in use. Filters can be used to display archived products. A product search by name has also been added.

OPT-1174 Email change security improvement​

Authentication required when changing email address.

OPT-1179 Export from backlog​

Backlog items in a Kanban column can now be easily exported.

OPT-1180 Excel export improvement​

Improved Excel export columns format.

OPT-1188 Automatic Websocket reconnection​

Optera.io now tries to automatically reconnect websockets in the event of disconnection. If the error persists (e.g. due to network connection problems), it is displayed to the user with a button to reconnect.

OPT-1200 Time tracking management rights​

You must now have “Account manager” or “Organization manager” rights to modify time tracking clients and accounts.

OPT-1229 Unauthenticated navigation improvement​

Small improvement in navigation for unauthenticated users.

Bugfix​

• OPT-1193 Search with folded side bar
• OPT-1207 Product/member search visual bug.
• OPT-1223 Wrong email logo
• OPT-1224 Focus login OTP

Bug fix release

Bugfix​

• OPT-1181 Web socket disconnection fix (Backend)
• OPT-1178 Web socket disconnection message
• OPT-1184 Fix 500 error in case of ConnectionResetError on websocket messages
• OPT-1130 Non-functional filter search
• OPT-1137 Margin mobile checkbox search item
• OPT-1141 Frontend request to be analyzed
• OPT-1176 Backlog sub-item displacement error

Features​

OPT-349 Exporting backlog items​

A new item export function is now available. It allows you to select backlog items and export them in CSV and XLSX (Excel) formats. The export is performed as a background task.

OPT-1100 Job closing and notifications​

When the user closes a background job or marks a notification as read, it is also closed or read in other tabs and browser windows.

OPT-1048 Release notes​

Functionality for exporting the list of completed backlog items in a release.

OPT-1136 Websocket disconnection management​

If websockets used to refresh kanbans, background task status and notifications are disconnected, an alert is displayed to the user with a button to re-establish the connection.

OPT-439 Sub-items indicator improvement​

Parent backlog items show the number of backlog sub-items still open in addition to the total number.

OPT-1107 Mobile table pagination improvement​

Improved pagination on mobile devices.

OPT-1051 Parent/child filter​

A new filter allows you to list only parents and independent backlog items, or only sub-backlog items.

OPT-1001 User dashboard performance improvement​

Improved user dashboard performance.

Bugfix​

• OPT-1140 Version services Backlogitem
• OPT-1127 Mobile tel click on tag bug
• OPT-1129 Kanban rights bug
• OPT-1119 UserJob error handling
• OPT-1109 Mobile loader bug
• OPT-1106 Wrong link to doc
• OPT-1108 Product dashboard / wrong link

Features​

OPT-1020 Background task display​

Background tasks are now displayed next to notifications. They indicate their status and give access to task error messages if any.

OPT-1040 User job summary​

A summary is displayed on completed jobs.

OPT-1042 Allow job deletion​

Completed jobs (successful or error) can be deleted by the user.

OPT-86 Bulk update backlog item​

It is now possible to update several items of a product from the item search screen. Updating takes place in the background.

The following fields can be modified:

• Status
• Corrective versions
• Versions concerned
• Type
• Epic
• Labels
• Priority
• Assignee
• Reporter
• Estimate (in hours or points depending on project)
• Business value
• Needs estimate
• Lead time
• Default count

OPT-1063 Bulk on Kanban​

The bulk update feature (OPT-86) is also available for an entire Kanban or Product Backlog column.

OPT-1055 Disable notifications on bulk update​

Option to disable notifications during a bulk update.

OPT-650 Move item to other product​

It is now possible to move items to other products. When moving, the user must indicate the corresponding type in the destination project for each type. The same applies to epics.

OPT-129 PWA​

Optera is now a progressive web app. It can be "installed" on a tablet or smartphone. The application uses PWA functionalities to cache its components. However, it cannot be used offline.

OPT-114 Notifications​

In addition to internal notifications, Optera now offers the option of receiving desktop and email notifications. For each type of notification, users can choose which channel they prefer.

OPT-828 Empty value filter​

Filters now propose an empty value when the field can be empty.

OPT-1030 Inter-product backlog item link​

It is now possible to create links between items from different products within the same organization.

OPT-1022 Pagination size​

The user can now choose the size of lists.

OPT-812 Reorder sub-tasks​

Backlog sub-items can be reordered to present them in a logical order. This order is resumed when the item is set to "to do".

OPT-978 Notifications via websocket​

Internal notifications are refreshed via a websocket connection.

OPT-1026 Notification deactivation​

Assignment, mention and team welcome notifications are no longer sent are no longer sent during Jira imports. All notifications are disabled in bulk updates.

OPT-933 Resolution popin​

When a backlog item is closed without passing through the "done" status, a popin asks for the resolution code (done, will not be done, impossible to reproduce, duplicate).

OPT-762 Prevent modal closure​

If the modal of the backlog item being edited is closed, Optera now asks for confirmation.

OPT-789 My items on personal dashboard​

The personal dashboard shows the items assigned to the user. A button displays all items concerned.

OPT-997 Column selection​

The user can customize the columns on backlog item lists.

OPT-794 Improved search items​

Various visual enhancements, including filters and pagination.

OPT-768 Kanban tag filter​

The user can filter the Kanban with tags.

OPT-951 Worklog Product Filter​

Worklogs can be filtered by product.

OPT-1009 Switch dark mode​

Switch between light and dark mode from the user interface.

OPT-896 Archived accounts column​

archived accounts have an archived flag instead of a checkbox.

OPT-957 Improved list performance​

Improved list performance, especially on dashboards.

OPT-972 Account restriction improvement​

Accounts are hidden as they are added to a product in the product account settings screen.

OPT-123 Notion of delay on backlog items​

Add a delay field to backlog items.

OPT-1007 Hide pre-backlog status​

Pre-backlog values are hidden when selecting status on current backlog items (to do, in progress, done).

OPT-981 Improved mentions notifications​

Mentions are now handled in such a way as to avoid duplication. The system only considers a mention if it has been added since the previous state of the description or comment field, rather than any mention added.

OPT-297 About screen​

A popin now displays some useful information about the application. In particular, the version of the API and the application used.

Bugfix​

• OPT-1047 Visual bug Items list Mobile
• OPT-1046 Visual bug search items Mobile
• OPT-1049 Visual bug Add Release button
• OPT-1025 View more dashboard button bug
• OPT-1036 Link item type error
• OPT-990 Wrong count on dashboard
• OPT-1023 Display filters
• OPT-1013 Improved switch darkmode + lang
• OPT-882 Worklog modification bug
• OPT-902 Add team member bug: form does not empty
• OPT-827 Missing customer creation error
• OPT-988 Link item error
• OPT-994 JIRA import error
• OPT-1067 Parent resolution
• OPT-665 Activation git pattern organization

Features​

OPT-897 Product backlog deactivation​

Allows product admin to deactivate backlog in simple cases where Kanban is sufficient.

OPT-525 Gitlab Webhook​

Displays merge requests, CI build jobs and commits on the item. See documentation.

OPT-870 Jira Import​

Import your items from a Jira project.See documentation

OPT-524 Slack integration​

Retrieve summary information when you mention a ticket in slack.See documentation

OPT-103 Account Restriction​

Allows you to restrict the number of accounts available on a product.When a user enters an account on a work log,he/she can then only select it from the predefined accounts.

OPT-515 Unified background task and notification system​

Preparation of a background task system for use with Jira imports and in anticipation of tasks to be developed in a later release. Automatic cleanup of completed jobs.

Bugfix​

• OPT-820 Account not visible
• OPT-973 Cache problem

Daily Scrum meetings, also known as "stand-up meetings", are an essential component of the Scrum methodology. These short, focused daily meetings enable the Scrum team to synchronize its activities, identify potential obstacles and plan the day ahead. However, to take full advantage of Daily Scrum meetings, it's important to run them efficiently and productively. In this article, we'll explore the keys to running a successful Daily Scrum and optimizing team collaboration.

Respect the basic structure​

Daily Scrum meetings must respect a well-defined basic structure to remain effective. The meeting must be short (generally limited to 15 minutes) and take place in the same place at the same time every day. Each team member will answer three key questions: What have I accomplished since the last meeting? What do I plan to accomplish between now and the next meeting? What obstacles or problems have I encountered or anticipated? Respecting this structure will keep the meeting concise and focused on essential information.

Focus on transparency​

Daily Scrum meetings should be a space of transparency where each team member openly shares their progress, challenges and needs. It's essential to foster an environment where team members feel comfortable sharing honestly and where problems can be identified quickly. Encourage mutual trust and ensure that all team members have the opportunity to express themselves freely.

Avoid excessive technical detail​

Daily Scrum meetings are not about solving complex technical problems. Rather, they are an opportunity to briefly share task progress and identify potential obstacles. Avoid getting lost in technical details during the meeting. If issues require more in-depth discussion, schedule separate discussions outside the meeting to avoid slowing down daily progress.

Keep the team engaged​

Team members must be fully engaged at Daily Scrum meetings. Make sure all members are present at the meeting and fully focused on the exchanges. This also means being punctual and keeping to the time allotted for the meeting. By maintaining a strong commitment, Daily Scrum meetings will become a consistent and effective ritual for the team.

Use a visual chart or tracking tool​

To facilitate understanding of task progress, we recommend using a visual chart or a tracking tool such as a Kanban. These tools enable the team to quickly visualize tasks in progress, completed tasks and obstacles encountered. This facilitates communication during Daily Scrum meetings and enables everyone to quickly understand the overall state of the sprint.

Encourage proactive obstacle resolution​

Obstacles and problems identified during Daily Scrum should be dealt with proactively. Encourage the team to find solutions quickly and take the necessary steps to overcome obstacles. By encouraging a proactive approach to problem solving, the team can maintain positive momentum and avoid delays.

An important event​

Daily Scrums are a key element of the Scrum methodology, enabling the team to synchronize on a daily basis and quickly detect obstacles. By following these few rules, you can optimize team collaboration and maximize the effectiveness of these daily meetings. By respecting the basic structure, promoting transparency, avoiding excessive technical detail, keeping the team engaged, using visual tools and encouraging the proactive resolution of obstacles, you can create an environment conducive to the success of your Daily Scrum and the efficient advancement of your product.