OCTO:Open Core for Technology Orchestration/New and Noteworthy
Jump to navigation
Jump to search
New and Noteworthy in OCTO Milestone V1.4.1 (October 8, 2025)
OCTO Other issues/enhancements resolved
- 629 - Promote does not work from a single object in VSCode
- Promote action from the item editor function correctly now as intended, not showing a blank screen.
- 937 - OCTO - Chart resizes but becomes unreadable
- The chart now resizes to the available size but it becomes unreadable when there are many items in the chart. The resize option should be selectable: Shrink to fit or do not resize. See att.
- 939 - Oct client - Outline plugin
- Add an outline plugin to Octo. (Replaced with OctoFlow).
- 953 - OCTO - Wizards from link will visit build() twice
- Wizards from link (and possibly all links) visit the build method twice.
- 965 - SECURITY - Octo leaks configurations when item link is not correct
- When a link does not go to an organization, it needs to be blocked.
- 967 - Initial octo load still shows weird font for theme
- Initial octo load still shows weird font for theme.
- 976 - Octo Client - Check URLs in the hosted FontAwesome CSS file
- There are still external references in the FontAwesome hosted CSS files.
- 978 - Octo Client - Construct the OctoLink using the WizardInfo
- We need the OctoLink API URL to also be available for wizards opened as modal dialogs. The URL should come from the WizardInfo object.
- 1003 - Octo - Custom LLM settings in Octo Admin
- Allow users to adjust LLM parameters like Temperature, Top-k, and Max Tokens directly from the admin panel for more tailored model behavior.
- 1006 - Displaying a wizard from the link results in building it twice
- When navigating to a wizard via a direct link, the wizard component is being constructed twice.
- 1014 - OCTO - Bottom section gets corrupted when spooledfiles is docked in the editor area
- Steps to reproduce. Remove spooled file from the bottom section. Install spooled files in middle section. Open build queue. Find an entry and use Show spool file context menu. The bottom section is gone
- 1018 - Octo Server - Avoid logging the content of tunneled requests
- Octo server should not automatically log requests that are tunneled through it when an error occurs. Only the error message and a stack trace should be logged.
- 1019 - Octo - R&D on AI and Octo editors integration
- Explore how the Octo Agent could enhance the Octo Monaco Editor with additional functionality, such as AI-powered outlining, source structure, and code analysis.
- 1022 - Octo - Header date pipe issue
- The workspace info popover in the header contains an Angular date pipe that may block the good loading of the page.
- 1023 - Oct client/server - Add AI based editor outline
- Add an AI-powered outline view that dynamically displays an overview of the source content for the currently selected editor.
- 1026 - Octo Client - Browser resizing
- Resizing the browser doesn't reflect in the workspace sections.
- 1028 - Octo Client/Server - Add code docs generation to the web editor
- Add AI-based docs generation for a whole editor content in the web client.
- 1036 - OCTO - Bottom Section Space Disappears on Task Interaction
- The Bottom Section vanishes whenever any interaction occurs on OCTO.
- 1038 - Octo Client/Server - Configure default embeddings and coding LLM
- Add configuration for default LLM that Octo server should use for embeddings and code operations.
- 1039 - Octo client - Make dev-only plugins available on Devkube
- Currently, dev-only plugins can only be installed when running on localhost. We need to extend support to allow installation when running on DevKube as well.
- 1045 - Octo client - Add OctoFlow view
- An immersive view ,currently code-named OctoFlow, that delivers AI assistance tailored to the user's context.
- 1051 - Octo - Model Context Protocol (MCP) Specs Study
- Model Context Protocol (MCP) Specs Study
- 1053 - Change password workflow in Octo does not work
- Go to user settings, change password. Password cannot be changed. See user settings.
- 1054 - Octo client - Make the user addition/removal local UI scrollable
- Make the search result of the users to add or remove from an organization locally scrollable.
- 1055 - Octo Server - Logging password update/reset fails
- Persisting password update/reset change log to DB fails.
- 1057 - Octo client - Revisit user settings layout
- Scrolling not working in VS Code. Update the html code using color template. Clean up code
New and Noteworthy in OCTO Milestone V1.3.4 (July 2, 2025)
OCTO Other issues/enhancements resolved
- 1013 - Octo Client - Search dropdown in silver theme .
- The dropdown beside the search box should react on the silver theme as well.
- 1012 - Octo Client - Only use check box space when enabled.
- The vertical space should no be used unless the check boxes are visible.
- 1011 - Octo Client - TD/OMS version manager falling back to an incorrect version.
- When the TD/OMS version manager is unable to determine the plugin version, it should default to the latest available version. However, it is currently falling back to an incorrect version instead.
- 1010 - Octo Client - Octo admin org owners section misbehaves.
- Octo admin org owners section misbehaves. See screenshot in the issue.
- 1009 - Octo Client - Allow admins to remove orgs without being owners.
- An Octo admin should be able to remove an organization even if they are not its owner.
- 1008 - Octo VS Code - Solution editor not showing up.
- Opening a solution using the context menu does not launch the Solution Editor.
- 1007 - Octo - Source editor maximize/restore issue in Firefox.
- In Firefox, after maximizing and then restoring the window, the source editor renders with an incorrect width. See screenshot.
- 1005 - Octo Client - Source Editor Resize Breaks Bottom Section Visibility.
- Reproduction Steps:1. Open a source file in the source editor. 2. Toggle to hide the bottom section. 3. Maximize the source editor using its local toolbar. 4. Minimize the
source editor. **Expected Behavior**: The bottom section should remain hidden. **Actual Behavior**: The bottom section becomes visible again, but with a distorted layout.
- 1004 - Octo Client - Opening Octo in VS Code from main toolbar is unreliable.
- Opening Octo in VS Code by clicking the "VS Code" button in the main Octo web header is currently unreliable. This functionality depends entirely on the operating system
correctly passing a link to the Octo extension, which must already be installed. During development, this process often gets confused b ween the installed extension and the running Octo host in VS Code. For now, I'm omitting this feature until we can define reliable testing steps
- 1001 - Octo server continues streaming from Ollama despite client disconnection.
- When the web client disconnects from the Octo server during a streaming session, the server correctly stops sending data to the client. However, the server
continues to stream tokens from the Ollama LLM backend.
- 998 - Octo Client/Server - Enable RAG build from ZIP file.
- Octo should support building a RAG using uploaded ZIP file contents, useful for quickly generating a RAG from sources like a downloaded GitHub repository.
- 995 - Octo Client - TD/OMS version manager.
- If there is only one configuration available, the version manager should use it regardless of whether it is marked as default.
- 994 - Octo - Separate RAG building from agent settings.
- Decouple RAG settings and building from agent to enable dynamic switching of models and indexes.
- 992 - Octo Server - Support link crawling and content scraping for RAG
- Octo Server should support deep crawling and content scraping from URLs provided as RAG sources to be used as contextual documents.
- 991 - Octo client - Add TDOMS version 17.1 to version manager.
- 990 - Octo client - Allow Agents with RAG content from links.
- An AI agent should be capable of expanding its knowledge base by retrieving and processing content from remote URLs.
- 988 - Octo client - Avatar or logo upload fails.
- Uploading user avatar or organization logo is failing.
- 977 - Octo Client/Server - Add RAG based AI agents support.
- Integrating a RAG (Retrieval-Augmented Generation) agent would significantly enhance Octo plugins, given the right idea and integration. Add a UI in the Octo admin to facilitate the configuration and creation of AI agents. Additionally, enable the Octo server to create and manage RAGs and serve streamed tokens from RAG-enabled LLMs.
- 969 - Octo Client - The item editor's task overview should scroll to reveal the selected tab.
- The item editor's task overview should scroll to reveal the selected tab if it is horizontally hidden when loading from a link or upon a reveal even.
New and Noteworthy in OCTO Milestone V1.3.3 (May 14, 2025)
| We've introduced the silver theme. | In the Octo web client, we've added a new theme: silver.
|
|---|
| Octo now adapts to all VS Code color themes. | Octo now comes with out-of-the-box support for all VS Code color themes. This means that Octo automatically adapts to any color theme you choose in VS Code, ensuring a seamless and visually consistent experience.
|
|---|
| We've enhanced graph rendering. | Octo's charting has been improved, especially for dark themes.
|
|---|
OCTO Other issues/enhancements resolved
- 634 - Octo VS Code - Dark theme preloading white page
- When the dark theme is active, The VS Code view hosting the Octo plugin shows a white page prior to full loading of the plugin. See att.
- 793 - octo toolbar tour
- the octo toolbar tour, by default seems to popup in a sort of dark theme, not that readable, cannot close but have to press got it, which is not overly clear.
- 911 - Octo VSCode - Opening a chart opens two views
- A chart view opens twice in VS Code. For example, when selecting the Dependencies Chart from a component's context menu.
- I03039 - OCTO - Item editor only uses half screen in full screen mode
- The bottom half of the screen is empty when I make the item editor full screen. As a result I have to scroll to see everything in the top half of the screen.
- 928 - Octo Client - The expanded plugin should be positioned in the center of the page
- An expanded plugin should be centered on the page, leaving space on both the right and left sides.
- 932 - Octo client - Renaming and adding folders in TD/OMS plugins directory
- Rename the current tdoms-v16-0-m2 to tdoms-v17-0-m2. Retrieve tdoms-v16-0-m2 from the octo-app/V1.3.1 branch. Perform the necessary wiring to ensure the builds succeed..
- 936 - Flicker is back in Octo
- After switching configurations, following a link or pressing F5. We first see empty octo placeholders with 'Install Plugin'. This was fixed but now it is back. See attachments
- 938 - Octo client - Copy to clipboard not working in wizards
- 940 - Octo - Agentic AI Integration R&D
- Octo should offer custom AI agent building capabilities. DeepSeek is a good candidate for an LLM as it is open-source, powerful, and can be easily installed locally. Octo should also utilize a Retrieval-Augmented Generation (RAG) approach to contextualize the LLM responses.
- 941 - Octo client - Add a media viewer plugin
- A plugin to display images and videos within Octo.
- 942 - Octo Client - Add option to fit chart to view
- Allows users to click a menu button to make charts exactly fit the view.
- 943 - Octo Client - "Collapse/Expand Nodes" button missing from toolbar
- The chart plugin is not displaying the "Collapse/Expand Chart Nodes" button in its toolbar
- 944 - Octo Client - Chart node tooltip misplaced
- When double-clicking a chart node, its tooltip is misplaced in the window top left
- 945 - Octo Client - Chart node issues in dark theme
- The name of a leaf node is not visible in dark theme. Improve the node text in dark theme.
- 946 - Octo Client - Encode the presence of '?' in chart URL parameter
- The presence of '?' in a URL parameter name or value causes problems for the targeted server and local reading of parameters.
- 949 - VSCODE - Octo is getting really slow in VSCODE
- When OCTO runs inside VSCode, we see that it can take a long time to load the webviews. This is because all webviews get the task selected events and start building their UI even when they are not visible
- 950 - VSCODE - Webview fades to black in VSCode dark theme
- When VSCode is in dark mode, the Octo webview flicker which looks unprofessional.
- 951 - VSCODE - Hundreds of /product requests when a webview is started
- When the webview is started, hundreds of requests are send from the webview to the gravity server
- 952 - VSCODE - Avoid reloading the webview when it is already loaded.
- At the moment the complete webview is reloaded for a new event. There are issues with this approach. It is slow. The whole of gravity needs to be reloaded
The plugin looses its internal state. We need a way to communicate with the webview and send the event without having to reload the whole plugin
- 954 - OCTO - Search bar overlays the context menu
- In Web and VSCode the context menu is below the search bar. See att.
- 956 - Octo Client - Automate the addition of plugins in the middle section of VS Code
- The placement of Octo plugins into the middle section when running as a VS Code extension should be automated. This automation will also enable the handling of Octo events from other webviews.
- 957 - Octo Client - Enable Octo to react to color theme selection in VS Code
- When a user selects a color theme in VS Code, Octo should react by picking the closest matching Octo theme. This ensures that plugins blend seamlessly into the VS Code environment.
- 959 - Octo client - Add gray-silver theme
- Add a third gray-silver color theme to the Octo web.
- 960 - Octo client - Visit TD/OMS task component HTML
- Ensure icons remain in their designated positions and do not shift to the right.
Address the excessive or incorrect use of Bootstrap classes, such as d-flex and row, along with their attributes.
- 964 - OCTO - Stacking order of views is not preserved
- When refreshing, the stacking order is not preserved. For example: WorkManagement and Tracker in the left stack. 1- Work Management is visible. 2-Refresh (e.g. switch configuration or press f5) 3-Tracker view is visible. Please maintain the stacking order when saving the workspace state.
- 966 - Octo Client - Missing result prompt for "Send test mail" action
- In Octo admin, when testing an email configuration by sending a test email, the prompt console indicating success or failure no longer appears.
- 968 - Octo Client - Horizontal scroll in one-tile logged-off workspace
- A horizontal scroll appears below the login form in the one-tile workspace. See att.
- 971 - Octo Server & Client - Implement tunneling to circumvent CORS
- Octo server should implement a tunneling mechanism to effectively circumvent CORS restrictions.
- 973 - Octo Client - Make the wizard scrolling optional
- Allow the wizard components to decide whether to use vertical scrolling.
- 974 - Octo Client - Allow unencoded params reading from OctoLink
- An OctoLink is automatically decoded. Sometimes you need to read a parameter before decoding mainly if it includes the special character '&'.
- 975 - Octo Client - Upgrade Axios to 1.8.4
- We're lagging behind. Additionally we need the streaming feature introduced starting from version 1.7.x
- 979 - Octo Client - Enable a wizard to hide the link section
- A wizard should be able to hide the link section if it is not relevant. Additionally, truncate the displayed link if it is too long to avoid breaking the UI ( Of course the copied link should remain intact)
- 983 - Octo VSCode - The context menu "Add to Build Queue" event
- The event dispatched by the context menu action "Add to Build Queue" is not reaching its consumers.
- 986 - Octo client - Tile menu wrap issue
- The tile menu wraps when it should not.
- 987 - Octo client - Event missing the entity class name in some cases
- The class name of the entity related to the event is not always set in the right place within OctoEntity.
- 961 - create a command to reset the Octo admin token.
- For the docker-compose en Kubernetes environment there is a script available that will clear the currently set admin token.
- 980 - Reconfigure Harbor to run https through apache proxy
- The Remain Harbor (Docker) repository has been reconfigured and is now only available at https://harbor.remainsoftware.com.
- 981 - There is a vulnerability in the version of mongoose (6.11.3) being used in the Octo Docker image.
- The current version of Mongoose in the Octo Docker image has been replaced with version 6.13.6.
New and Noteworthy in OCTO Milestone V1.3.2 (February 12, 2025)
| External Resources Localization & User Sign-Ins Geolocation Switch On/Off | We've localized all external resources, allowing Octo to run completely offline without requiring an external internet connection. Additionally, the geolocation feature for user sign-ins, which is a security measure, can now be switched off in the Octo Admin authentication settings. We've also added a guided tour to provide more details about each of the settings inputs
|
|---|
| Extended Support for Email SMTP Server Settings | In Octo Admin, email SMTP settings no longer require credentials (E.g., To support internally configured SMTP servers). Additionally, we've added a guided tour to provide more details about all the settings inputs.
|
|---|
| We've added support for Octo-wide user account removal, enabling, and disabling. | In Octo Admin, you can now delete an Octo user or enable/disable their account.
|
|---|
| We've added support for Octo environment settings. | Admins can now add, edit, and delete Octo meta configuration files, such as deployment variables, directly from Octo Admin.
|
|---|
| Octo Docker for Kubernetes and has been further optimized and integrated with an nginx service for https support. | HTTPS integration is made possible by adding a seperate Nginx container running as a reverse proxy. Except for providing your own SSL certificates this is a hands-off setup. For Kubernetes using a TLS secret makes setting up certificates for HTTPS communication fairly simple, further information can be found at https://remainsoftware.com/wiki/index.php/OCTO:Installing_the_Docker_image_on_a_Linux_system#Setup_of_Nginx_with_Octo_in_Kubernetes.
|
|---|
OCTO Other issues/enhancements resolved
- I02886 - Some wizards in OCTO are opened with the footer first when opened from a link.
- Some wizards are opened with the footer first (previous, next, finish, cancel buttons) and below that the actual wizard content follows.
- 720 - Octo - Enable an admin or org owner to remove a member.
- A global Octo admin or an org owner should be able to remove/disable a user/member.
- 758 - Octo client - Contain the overflowing tabs within a horizontal scroller
- When too many tabs are opened in the item editor or source editor they collapse to the next line. Keep them within one line by making it horizontally scrollable (for example: as In VS Code).
- 763 - When maximizing the Item Editor, it does not display in full screen.
- There are two issues: 1. When maximizing the Item Editor, it does not display in full screen. 2. When minimizing the Item Editor, the Work Management view displays as empty..
- 808 - OCTODEV - Layout Issue in Source Editor.
- Multiple refresh and scrolling issues.
- 820 - OCTO - Help Tour in VS Code is stuck.
- The help tour in VS Code in Work-Management is stuck on the search options box. Hide and show will reset the view.
- 831 - Octo Client - Create a Monaco editor component.
- Use directly the Monaco editor source code and drop the wrapping angular module: 'ngx-monaco-editor".
- 837 - OCTO - Workspace link errors.
- In some cases the workspace links are throwing errors which cannot be resolved by clearing the cache. It looks like the associated user does no longer exist and this trips the workspace link. In this case, delete the workspace link and do not throw an error.
- 840 - Octo Client - Optimize components change strategies.
- Only require Angular components update if needed..
- 844 - Octo client - Add automatic support for default editor languages.
- Monaco editor supports out of the box languages but they have to be picked and activated..
- 845 - Octo client - Switch the editor theme centrally in the core.
- Octo Monaco editor theme switching should be handled by the Core.
- 847 - Octo client - Automate event topic registration on VS Code side.
- Currently, prior to event re-dispatching in the VS Code side, the event topic should already be known to Octo extension. Automate this process using plugin info's already available on the VS Code side.
- 848 - Octo client - A plugin shouldn't be handed its own event.
- Prohibit the event manager from feeding a dispatcher its own event.
- 849 - Octo client - Add support for starred event topics.
- The event manger should be able to handle global/prefix topics with formats such as "someTopic/*".
- 850 - Octo client - Enable a plugin to know whether it's visible/revealed .
- A plugin should be able to know whether it's visible. This comes in handy, for example, to decide to build or delay that.
- 854 - OCTO - The revealed plugin does not take the initial input.
- When I click a task, the components view is installed and revealed but it does not take input task and build the UI.
- 856 - Guide screens stays open
- 859 - Octo client - Add support for Octo reveal actions in VS Code.
- Make plugin reveal in VS Code possible.
- 860 - Octo server - Upgrade Mongo driver and Mongoose.
- Upgrade Mongo packages and all other npm ones. Then test and set the server "featureCompatibilityVersion" to Mongo 8.0.3
- 863 - Octo server - Add comments service
- Implement support for comments handling in Octo server.
- 867 - Octo client - Add core support for comments.
- Any Octo object should be able to use the comment support from the Octo server.
- 868 - Octo client - Add help tours to wizards.
- Octo wizards should be able to show help tours.
- 872 - Octo Client/Server - Add support for disabling/removing a user from Octo.
- Currently, we only support removing members from an organization. An admin should be able to disable or delete a user Octo-wide.
- 874 - Octo Client/Server - Add support for environment variables admin.
- One should be able to read and update Octo server/image related environment variables using Octo admin UI.
- 876 - Octo Client/Server - Configuring SMTP mail server without credentials.
- Enable configuration of the outgoing mail server (SMTP) without requiring a username and password.
- 879 - Octo Client - Internalize CSS and script resources.
- Octo client should render properly even when offline. To achieve this, resources like CSS and scripts referenced in the index.html and style files need to be localized.
- 880 - Octo server - Ignore geolocation when offline or switched off.
- Octo server should disregard geolocating sign-ins and sending alert emails if there is no internet connection or if this feature is disabled in Octo admin.
- 881 - OCTO - Refresh issues.
- 1) When switching the theme between dark and light modes, the login screen retains the previous theme until the cursor moves over it. 2) After refreshing the page, the build queue displays only one record, regardless of the total number of records
- 883 - Octo client - Kanban providers dropdown freezes.
- You can't select another Kanban provider from the dropdown list unless another one is already active and showing own cards.
- 888 - Octo client - Add help tours to Octo admin.
- Add missing help tours to Octo admin.
- 890 - Octo client - An embedded plugin should not react on events.
- An embedded (not installed) plugin should not register for events and should rely on parent @input fields.
- 891 - Octo Client - Upgrade Angular to version 19.
- Let Octo use the Angular version 19.
- 892 - Octo Client - Upgrade Monaco editor to version 0.52.2.
- Upgrade Octo Monaco editor to version 0.52.2.
- 893 - Octo Client - Upgrade Typescript dependency to 5.6.3.
- Upgrade Octo Typescript dependency to 5.6.3
- 895 - Octo VS Code - Allow the component editor to open in the middle section.
- In the web client, the component editor opens in the right section. In VS Code, it should open in the editor section, which is the middle one.
- 898 - Octo VS Code -The sign-in form not showing up.
- In VS Code, the work-management view stays blank instead of showing the login form.
- 899 - Octo VS Code - Work-management filters storage fails .
- The storage and retrieval of work-management filters in the local memento are failing.
- 900 - Octo client - Ensure consistent scrolling sizes between VS Code and web.
- Enhance scrolling in Octo views across both VS Code and web platforms.
- 901 - Octo client - Prevent opened tabs from wrapping.
- To prevent the opened tabs, such as those in the source editor and item editor, from wrapping and breaking the layout, make them horizontally scrollable. Additionally, ensure the selected tab is revealed upon selection.
- 903 - Octo client - Tabs should only load when selected.
- When multiple tabs are already open in the source editor/ item editor, the hidden tabs unnecessarily load upon reload.
- 904 - Octo client - Add a color picker.
- Integrate a color picker library into Octo core, ensuring that other components can easily and transparently utilize it.
- 905 - Octo Client - Refactor the plugin scrollbar area calculation.
- Refactor the calculation of the scrollable height of a plugin into a single function and put it in the core plugin. This will centralize the logic and remove the scattered calculations from the component HTML.
- 906 - Octo Client - Make the table body scrollable and the header sticky.
- In table layout views, make the table body scrollable while keeping the header sticky
- 907 - Octo server - MongoDB buffering timed out exception.
- In some cases, MongoDB connections throw a buffering timed out exception. This error may occur because a model is being used before the connection is fully established.
- 908 - Octo client - Solutions component double loading.
- The Solutions component should only rely on the task being injected by the embedder (e.g., item editor) instead of both listening to task selection events and receiving the task as an @Input. This results in double loading.
- 912 - Octo VS Code - Upgrade and test the package.json files.
- Upgrade and test the package.json files.
- 913 - Octo Server - Enhance logging for organization interactions.
- The Octo server should log more detailed information about organization interactions, such as updates and removals.
- 914 - Octo Client - URL case sensitivity .
- URL parameters are case sensitive, so typing one manually can lead to a "Page Not Found" error. A plugin should be able to test whether it can handle a URL regardless of case sensitivity.
- 916 - Octo server - User sign-up failure.
- User sign up fails because of a missing tenant DB connection.
- 917 - Octo - Allow searching users by ID in Octo Admin.
- Given a user id, one should be able to look it up in the Octo Admin/Users section, Handy when viewing a user by their ID from the server logs.
- 918 - Octo client - Drop the TD/OMS milestone 1 folder code.
- The folders: octo-ts-angular-client\src\app\plugins\tdoms-versions\tdoms-v16-0-m1 and octo-ts-core\extensions\tdoms-versions\tdoms-v16-0-m1
have been detached and are no longer being compiled by Angular.
- 920 - Octo server - Show the logger name when logging.
- The Octo server should also display the service name and the requester name, if available, when logging.
- 921 - Octo Client - Enable wizard to display HTML-based messages.
- The wizard container should be capable of displaying messages (such as errors and warnings) that include HTML tags.
- 922 - Octo Client - Link copying fails.
- Link copying via the context menu fails in Oto devkube.
- 924 - Octo Client - Wizards should use the message area within the wizard container.
- The Octo wizard should display messages in the designated wizard container area instead of using the core alert toast that appears in the bottom right corner. When a wizard is open, these toasts are not visible.
- 925 - Octo Client - Pass the height of the wizard container to the wizard.
- A wizard should be able to ask the wizard container for the available height it can use.
- 926 - Octo Client - Remove outdated and redundant configuration check from Item Editor.
- Configuration checks and initializations are handled in the superclass OctoVersionedPlugin.
- 929 - Octo Client - Add the color picker to the wizard example.
- Add the color picker to the wizard example.
New and Noteworthy in OCTO Milestone V1.3.1 (October 16, 2024)
| Create Transfer History plugin | We can see the transfer history in VSCode and the Web.
|
|---|
| Create Log History plugin | We can see the log history in VSCode and the Web.
|
|---|
| Create Version Conflict plugin | We can see the version conflict in VSCode and the Web.
|
|---|
| Component View Displays Only Objects - Add Members to the View | We can see the member in the component view in VSCode and the Web.
|
|---|
| Display Compile Errors in Source Editor | The source editor now offers real-time feedback on compilation errors.
|
|---|
| 'Impact Analysis' dropdown menu in Chart Plugin | We can see the impact analysis menu in VSCode and the Web.
|
|---|
| Display Compile Result in a View Reacting to Build Queue Items | Compile result can now be displayed in the view based on the build queue item.
|
|---|
OCTO Other issues/enhancements resolved
- I02892 - OCTO - Spool File issue.
- When we click the spool file plugin, it should not enter a loop.
- I02879 - OCTO - Copy Log History is not working.
- When we copy the log history link and try to open it, a 404 Not Found error is returned.
- 688 - Loader not appearing in Solutions Component within Item Editor
In the Item Editor, when we invoke the Solutions component, the Loader component within it is not appearing as expected. This issue seems to disrupt the expected flow and user experience.
- 788 - OCTO- Version Conflict initially show only required confirmation records.
- Initially, We show only the records with the required confirmation.
- 741 - Octo client - Tours UI issue
- In some conditions the the tour UI misbehaves. See attachment
- 743 - Preserve Multiple Open Tabs in Item Editor After Hard Refresh
- Currently, when multiple item tabs are open in the item editor, performing a hard refresh (Ctrl+F5 ) in OCTO results in only one tab remaining open, with the rest being closed. This causes inconvenience to users who need to keep their work organized across multiple tabs.
- 744 - Octo client - Keep the main tile toolbar regardless of plugin scrolling effect
- Force the visibility of the main tile toolbar out of the effect of contained plugins scrolling
- 745 - Octo VS Code - Duplicate events intercepted in VS Code
- Octo VS Code event interceptor is getting duplicate events although this is not the case in the Octo web client.
- 746 - Octo client - View resizer not showing up
- Under some conditions the drag-line view resizer doesn't show up
- 751 - Octo client - Kanban collapsible toolbars not working
- 752 - Octo client - Make only the Kanban columns scrollable
- For a better user experience, only the Kanban columns should be scrollable. The rest shouldn't.
- 755 - Octo client - Add a TD/OMS Angular template plugin
- An Angular component which is a template / skeleton that contains all one basic needs to start developing a TD/OMS plugin
- 756 - Octo client - Analytics toolbar link menu not working
- Clicking the link icon to open in tab from the plugin toolbar doesn't work
- 757 - Octo client - Create an example plugin implementation of the TD/OMS template
- Add an implementation example of the TD/OMS template plugin
- 759 - Opening a TD/OMS component not working if a spool file is opened
- If a spool file is already opened in the source editor then clicking a component in the Components view doesn't open it.
- 764 - Octo Client - Remove duplication from TD/OMS plugins
- Now that so many stuff is taken care of in the root TD/OMS plugin, duplicate code/logic/UI should be removed from all plugins.
- 765 - Octo Client - Changing a plugin key make its installed instances corrupt
- If a plugin instance is already installed then changing its key in the plugin class effects the UI and make it difficult to uninstall using the normal toolbar.
- 768 - Octo Client -Move/drop the utilities folder from the UI to TD/OMS core
- Move the utility files from the Angular TD/OMS components to the core section of TD/OMS within the extension folder. Update dependencies and drop duplicates.
- 769 - Octo Client - Add support for the Select2 library
- Select2 is a select box with support for searching, tagging, remote data sets, infinite scrolling, and many other highly used options.
- 771 - Octo Client -Opening a source editor from link not showing all editor tabs
- Opening a too long URL using the window.open(url) built-in function, which we use in turn, seems to truncate the URL leading to incomplete URL delivered to Octo plugins.
- 772 - Octo Client - Allow a plugin to not show the login form
- In TD/OMS plugins case, only WM plugin should show the login form when installed in a multi tile workspace.
- 774 - Octo Client - Login form not reacting on theme change
- Upgrade the Angular libraries being used in Octo client, such as the Angular core and cli and their dependencies, to the latest version 18.x. We're lagging behind (14.x) so
many major versions.
- 776 - Octo Client - Upgrade & Clean module dependencies
- 777 - Octo Client - Add support for Angular Material components
- 781 - Octo Client - Replace context menu with Material one
- Material menu supports multi-level and cross-views-border rendering out of the box,
- 782 - Octo Client - The settings icon in the toolbar not showing up
- If not signed in, the configuration dropdown is not showing up as it should
- 807 - Bug in Work Management plugin view
- When the Item Editor view is maximized and minimized for a task, the Work management view blanks out.
- 809 - Octo Client - Enable dropdowns contribution to the main Charts plugin
- A chart data provider should also be able to contribute menu's, including dropdowns, to the Charts core plugin.
- 816 - Octo Client - Dependency charts duplicate plotting
- In some cases, re-opening a dependencies chart by clicking its link from the component context menu plots a duplicate chart.
- 750 - The source does not open in the Source Editor
- When a spool file is open, the source of an object cannot be opened in the Source Editor from the Component view.
- 761 - OCTO - New object template issue
- When the new object template wizard opens with the categories default value set to "All," the search result dropdown should display the first template description as selected.
- 747 - Preserve Multiple Open Tabs in Source Editor After Hard Refresh
- Currently, when multiple source tabs are open in the source editor, performing a hard refresh (Ctrl+F5 ) in OCTO results in only one tab remaining open, with the rest being closed. This causes inconvenience to users who need to keep their work organized across multiple tabs.
- 748 - Add a filter to select the task.
- When we choose the option to move a solution to another task, the dropdown menu contains many entries, making it challenging to select the specific task. Therefore, we need to add a filter to streamline the selection process.
- 770 - Change Solution Type functionality in the ITEM Editor
- We can now change the solution type of a solution in the ITEM Editor.
- 783 - Error When Closing the Last Item in Item or Source Editor
- An error occurs when the last item or source is closed in the respective editors. This issue affects both the item editor and the source editor, leading to an unexpected error and potentially disrupting the user experience.
- 785 - Inconsistent Type Dropdown Styling Across Views
- The type dropdown added to the components view has a different style compared to the ones used in other views. To ensure a consistent user experience, we need to standardize the style across all views.
- 784 - Incorrect Error Message Displayed in New Object Wizard
- A correct error message should appear when attempting to create an object that already exists using the New Object Wizard.
- 785 - Inconsistent Type Dropdown Styling Across Views
- The type dropdown added to the components view has a different style compared to the ones used in other views. To ensure a consistent user experience, we need to standardize the style across all views.
- 790 - Enhance The current entity service implementation has only one method, which retrieves all records of an entity type based on the provided page number. To improve the functionality and usability of the service, the following enhancements are required
- - Retrieve All Entities from All Pages: Add a method that allows retrieving all records of a specific entity type across all available pages, rather than limiting the retrieval to a single page.
- - Get a Single Entity by ID:Implement a method that retrieves a single entity based on its unique identifier (ID).Entity Service with Additional Methods for Improved Data Retrieval
- 796 - After the last Octo update, VScode WorkManagement configs are missing
- After updating to the latest version of Octo, the WorkManagement functionality within VSCode is no longer working. Specifically, the configurations that should be visible in the view are missing.
- I02780 - The information of the Details tab is not visible in VSCode and standalone link
- When we have a link for the item editor it does not show contents in the details tab.
- 797 - Task status doesn't refresh or show progress after transfer in VSCode
- When a task is transferred from VSCode's work-management interface, it fails to automatically refresh and update its status. Additionally, if the task continues running in the background, no progress icon is displayed to indicate its ongoing status. This can lead to confusion as the user might not be aware of the task's current state or if it is still in progress.
- 801 - Solution tiles display 'null' for missing descriptions
- In the current implementation, some solution tiles are displaying the text 'null' as the solution description when the description is missing or unavailable.
- 803 - Replace all fetchWithResult2 calls with fetchWithResult
- The fetchWithResult2 method has been deprecated and removed from the entity service. However, it appears that this method is still being used in multiple places across the code. To ensure that the application continues to function correctly, all instances of fetchWithResult2 need to be replaced with the fetchWithResult() method.
- 802 - Compare with production in new tab does not work
- From the solution, I can choose "Compare with Production" in new tab, but it does not work.
- 806 - Task tab switching (Solution, Details, Ratification) broken on OCTO production
- Users are unable to switch between the task tabs (Solution, Details, and Ratification) on the OCTO production environment. This issue began occurring recently and is impacting user productivity as they cannot navigate between these tabs effectively.
- 810 - Create OCTO Client Service for EVFEventFile API Integration
- This issue aims to develop an OCTO client service for the EVFEventFile API. This client service will enable efficient and seamless communication between the client-side applications and the EVFEventFile API.
- 817 - Octo Client - Allow dynamic context menu contribution to chart nodes
- Allow a chart data provider to contribute (right-click) context menu to the nodes of a chart tree
- 825 - Octo Client - Add an Outline plugin
- A core Outline view that can handle showing different content types
- 830 - Octo Client - Make the TD/OMS task component more customizable
- The TD/OMS task component should be customizable depending on where it's being shown (Whether it's clickable, show the second line, check box...)
- 823 - Display Compile Errors in VS Code Source Editor
- Currently, the feature that displays compile errors from the EVFEventFile API is working well on OCTO. However, this functionality is missing in VSCode.
- 789 - Adding 'Impact Analysis Report' dropdown menu in Chart Plugin
- The new functionality on chart plugin is added as a dropdown for impact analysis to display dependency mapping based on the impact analysis report code selected.
- 819 - OCTO Include Dropdown to filter object or member inside Search
- In the Components Plugin View, the dropdown for selecting Object or Member for the component selection is to be included inside Search.
- 832 - Navigate to specific members in source files for compile errors
- Currently, compile results are displayed directly in the source editor, which works well when the errors pertain to the entire source file. However, when the compile results reference a specific member within the file, we need to improve the experience by navigating directly to that member in the source editor and displaying the associated errors.
- 828 - Adding tdoms task component header of selected task on Components & Item Editor
- The task header will display key details about the task to provide context and improve navigation associated with that task in Item Editor plugin and Components plugin.
- 839 - Template plugin component changes
- Add " this.updateStateLink();" to getPluginInfo method. Add "this._pluginInfo.withLink(this._pluginStateLink);" to updateStateLink method
- 799 - The object is not connecting to the connection list
- The bug to connect an object to a task and add it in connection list was fixed.
New and Noteworthy in OCTO V1.3.0 (1.3.0 Release: July 3, 2024)
| Dependency Charts | We are proud to present a depdendency visualization engine with the following initial options. The plugin will be automatically installed when the 'Dependency Chart' action is selected for a component.
The tree visualization collapses and expands when you click on a node. Use the expand/collapse toolbar item to expand and collapse the entire tree (
|
|---|
| Kanban improvements | The Kanban board has been improved in the following areas
|
|---|
| Move solution to another task | We can move the solutions to another task in VSCode and the Web.
|
|---|
| Change the solution type. | We can change the solution type in VSCode and the Web.
|
|---|
| Change the transfer path. | We can change the task transfer path in VSCode and the Web.
|
|---|
| Disconnect solutions from the task | We can disconnect the solutions (and optionally delete the objects and source from disk) in VSCode and the Web.
|
|---|
| Assign/Unassign Programmer
|
We can assign or unassign the programmer from the task in VSCode and the Web.
|
|---|
| Complete Task
|
We can complete a task in VSCode and the Web.
|
|---|
| Workspaces View
|
We've added a view where you can see and manage all your workspaces links in one place.
|
|---|
OCTO Other issues/enhancements resolved
- 811 - OCTO - Failed to fetch transfer history
- When we attempt to retrieve the transfer history of the solution, it should return the corresponding transfer history records for that solution.
- I02689 - Unable to create a new member
- If a member is already part of the task, we can now create a new member with the same source file and library.
- 737 - Move Solution functionality in the ITEM Editor
- We have added the same move solution functionality to the ITEM editor currently available in work management.
- 733 - Disconnect functionality in the ITEM Editor
- We have added the same disconnect solution functionality to the ITEM editor currently available in work management.
- I02749 - Build queue rest API sometimes works with the wrong user
- In the build queue, users can now only see their objects, not those of other users.
- 623 - Add to build queue does not work when the file is saved
- When we save the source in VS Code, the object is now added to the build queue.
- 633 - Octo VS Code - Add workspace state rebuild support.
- Loading Octo in VS Code should be able to rebuild the current workplace state from memento.
- 635 - Octo client - Add a plugin to handle workspace links.
- A plugin where to view and edit user's own workspace links. It should be available both in web client and VS Code.
- 636 - Add to build queue does not work when the object is already in the build queue.
- The appropriate message is given when the object is already in the build queue.
- 641 - Octo Memento Retains Task Selection Across Configurations.
- When a task is selected within the work management system for a specific configuration in Octo, and subsequently, the user switches to another configuration, the selected task
persists within the Octo memento. However, upon reloading the configuration, an informational alert is displayed indicating that the selected task is not found in the current configuration. This behavior can lead to confusion and inefficiency for users..
- 648 - OCTO - Item Editor Issue
- Identifying which object was designated as either *COMPILE or *TERMINATE has been simplified.
- 649 - Inconsistencies in Promote Wizard Page Display and Grouping Logic
- Upon selecting a sub-environment in the initial wizard page and proceeding to the next step, inconsistencies arise:
- 1. Duplicate Transfer Object Groups: The following wizard page presents two groups with identical transfer objects. This redundancy confuses users and disrupts the workflow.
- 2. Incorrect Grouping by Task Number: Furthermore, the grouping logic on the second page is based on task number rather than sub-environment, which contradicts our intended design and creates confusion among users.
- 650 - Promoting a Solution from Solutions Tab Leads to Full Transfer Overview Instead of Target Object
- Currently, when attempting to promote a solution from the Solutions tab, the system displays the entire transfer overview showcasing all transfer objects related to the task. This results in unnecessary clutter and confusion for users, as they only need to see the object they intend to promote.
- 653 - Implement Link to Open Compare Editor
- Currently, users can access the compare editor via the "Compare with Production" context menu. However, there is no implementation that allows users to open the compare editor directly from a link. This feature would significantly enhance user experience by providing more flexible access to the compare editor.
- 654 - Octo Client - D3js integration
- Integrate the D3.js library charts to be used by Octo plugins.
- 655 - Implement VS Code Source Compare that Opens Dedicated Compare Editor
- This issue proposes implementing a source compare feature in VSCode that functions similarly to the Octo Monaco editor. This would involve opening a dedicated compare editor window when comparing two files.
- 656 - VS Code Octo server setting update does not work anymore
- I've encountered a problem with the VSCode Octo extension. It appears that the server setting update feature is no longer functioning. Upon investigation, it seems that the script file responsible for handling the save action has been removed from the media directory.
- 657 - Create a source compare with revision for Monaco in OCTO
- We implemented a feature that allows users to compare different sources with revisions specifically for Monaco in OCTO.
- 658 - Rename the Object Service to Entity Service
- The Object Service currently performs the same functions as the Entity Service; however, it was named differently. To maintain consistency and clarity within our codebase, the Object Service is renamed to Entity Service.
- 660 - Monaco - Typing is slow
- Every cursor action in the Monaco web editor has a delay. Coding is not nice in the editor.
- 661 - Monaco - When scrolling to the end of the document the editor titles disappear
- When scrolling to the end of the document the editor titles disappear
- 674 - The attribute shouldn't be mandatory during the creation of the panel group
- When creating a panel group in OCTO, the attribute is no longer mandatory.
- 675 - Create a source compare with revision for Monaco in VS Code
- We implemented a feature that allows users to compare different sources with revisions specifically for Monaco in VS Code.
- 676 - Octo Client - Add charts examples plugin
- Add an Octo plugin to illustrate how to use the core chart data providers and types.
- 677 - Replace 'objectAttribute' with 'source type' from SourceReply
- Currently, we use 'objectAttribute' from the solution to define the extension of the source. However, this field doesn't always exist, causing inconsistencies and potential errors. To improve reliability, we need to switch to using the 'source type' that can be retrieved from the SourceReply.
- 680 - OCTO - Disconnect solution issue.
- The sequence of solutions in the disconnect solutions wizard was incorrect.
- 681 - Source saving is not working
- Source saving does not work if the spool is open.
- 682 - Revert Bootstrap to 5.2.3 Due to UI Problems in 5.3.3
- We have recently upgraded Bootstrap from version 5.2.3 to version 5.3.3 in our project. However, this upgrade has introduced several UI problems that are impacting the user experience. These problems were not present in version 5.2.3, which suggests that the new version has introduced changes that are incompatible with our current implementation.
- 683 - Item Editor Optimizations
- When the item editor refreshes, it refreshes all open editors. This can be inefficient and disrupt user workflow. We propose the following optimizations:
Refresh Only Active Editor; When a task is selected, the open item editors should not be refreshed; Don't refresh the spool file component on task selection.
- 685 - Octo client - Plugin reveal with preinstall causes dispatch event issue
- A revealed/automatically installed plugin may get the same event more than once.
- 686 - Octo client - Enable tree chart expansion and collapse
- Make it possible to expand/collapse a tree chart.
- 687 - Octo client - Allow plotting a chart directly from a URL
- Make it possible to draw a chart directly from a URL pointing to some JSON file containing tree data.
- 691 - Octo client - Allow chart data providers to register for URL handling
- An Octo chart data provider may choose to register for URL handling. The core will revive the right data provider to further process and plot the incoming URL.
- 692 - Running men icon disappears in dark mode during task transfer
- When a task transfer is initiated, the running men icon is displayed correctly in light mode. However, if the mode is switched to dark mode, the icon becomes invisible. This issue needs to be resolved to ensure the icon is visible in both light and dark modes.
- 693 - Source Editor Plugin
- We can scroll the title away
- When the mouse pointer is in the header of the view and the source editor is open then using a scroll will scroll the title out of view.
- 694 - Octo client - Automatically dismiss info toasts
- Automatically dismiss info and success toasts after a short given time.
- 696 - Info message "Task not found in Test 16.1M00 " displayed every time.
- Whenever you log in to OCTO or reload the page, the "Task not found: / in Test 16.1M00" message is displayed every time.
- 697 - Components filter does not work for STMF objects
- IFS objects can be filtered
- 698 - Checkout One Object Does Not Work as Expected
- Currently, the checkout functionality is not working as intended. Instead of fetching only the specified object, the system retrieves all objects and the GUI subsequently filters to display the correct one. This results in unnecessary data retrieval and processing.
- 699 - Show the long IFS name in the solutions tab
- 700 - New Object Wizard does not show the correct error message
- The new object wizard now provides the correct error message.
- 701 - Refreshing Browser Shows Login Dialog Briefly for Logged-In Users
- If a user who is already logged in to Octo refreshes the browser, all displayed plugins initially show the first login dialog. After a short period, the login dialog disappears, and the content of the plugins is shown. There is no need to show the login dialog if the user is already authenticated. This behavior can be confusing and disrupts the user experience. The expected behavior is to directly show the plugin content without the login dialog if the user is already logged in.
- 702 - Replace Hardcoded Field Names in OCTO Code with Static Fields
- In the OCTO codebase, there are numerous instances of hardcoded field names. This approach can lead to maintenance challenges and increase the risk of errors. To enhance code maintainability and readability, replace these hardcoded field names with static fields sourced from params or the corresponding entity classes.
- 705 - Build Queue Unresponsive to Save Event in VS Code
- When saving a source file in VS Code, the build queue does not react to the save dispatch event.
- 707 - Add Scrollbar to Task Details in Item Editor
- In the item editor, task details are displayed without a scrollbar when their content exceeds the tile height. Currently, the entire tile scrolls to view all details if all headers are expanded. This makes navigation and usability difficult.
- 708 - Change Hardcoded Fields to Read-Only Fields in VS Code
- In the current implementation of VSCode, there are certain fields that are hardcoded. To enhance flexibility and maintainability, these fields should be converted to read-only fields. This change will ensure that the values can be viewed but not altered directly, improving the overall robustness of the application.
- 709 - Octo client - Opening KanBan via link doesn't work
- Kanban URL API doesn't work correctly.
- 710 - Octo client - Open a chart via a link
- Add URL API support to charting.
- 711 - Octo VS Code - Add support for Octo charting in VS Code
- Enable opening the Octo charts plugin in VS Code.
- 712 - Make selection of multiple environments more clear
When a task contains multiple environments and we attempt to transfer it, the message displayed on the wizard is unclear. Users are not explicitly informed that they must select an environment from the environment selection list. This can lead to confusion and hinder the task transfer process.
- 713 - Wizard doesn't display the message.
- The wizard displays a message when no reason code or transfer path is found for the application.
- 714 - Create New object Template Issue.
- There should be no spaces in the name of the new object wizard when a message is selected.
- 715 - Checkout and promote is not working for IFS object
- Checkout and promotion are now possible for IFS objects.
- 716 - An unnecessary message is displayed
- Unnecessary messages will no longer be displayed in the connection list.
- 717 - CMD Source Type Missing in Source Editor
- The type of the CMD source on the source editor is empty, resulting in the source code not being highlighted. Please update the source type to ensure proper syntax highlighting.
- 718 - Octo client - Transitional page shows up before loading the perspective
- When reloading Octo web client and before loading the perspective, a transitional page indicating there is no perspectives yet is shortly shown when is shouldn't..
- 719 - When pressing refresh, the item editor gives an error
- How to reproduce: Open a task in the item editor > Press F5 > Error (see attachment).
- 722 - Build Queue Message text issue.
- We have shortened the lengthy message text in the build queue.
- 723 - Add Functionality to Delete All Spool Files from Spool File Component
- Implement a feature that allows users to delete all spool files within the spool file component efficiently.
- 724 - Octo client - Plugin addition/removal should be allowed for all org owners
- Any owner of an Octo org should be able to remove/add a plugin within an org perspective.
- 725 - Octo client - Plugin reveal should work regardless of perspective authority
- Plugin reveal should work even if the user can't install the plugin being revealed.
- 726 - Connection list issue
- We can now choose a particular object to remove from the connection list.
- 728 - Error Opening Solution Due to Invalid Page Number
- Opening the solution in the earlier versions does not work.
- 729 - Tasks do not filter on the release field
- We can now filter tasks based on the release field.
- 730 - Access token not found message is displayed each time on configuration switch
- When switching configurations, an error message stating "Access token not found" is consistently displayed. This issue occurs every time a configuration change is made, regardless of the specific configurations being switched.
- 731 - Update 'getJsonWebToken' in the Login Service to Handle Refreshing Token from Old Token
- The current implementation of the getJsonWebToken method in the Login Service does not support the functionality of refreshing an old token to obtain a new one.
- I02750 - Item editor refresh does not refresh ratification
- After activating the ratification, refreshing the ratification tab in the item editor does not retrieve the updated task information.
- 734 - Octo client - Add a TD/OMS chart data provider
- A TD/OMS chart data provider that is registered by the Octo available providers and will be automatically initiated to handle chart URL meant for TDOMS.
- 735 - The displayed file name based on the solution is wrong for a member in VS Code
- When viewing a file associated with a solution member in Visual Studio Code, the displayed file name is incorrect.
- 736 - Source Type Missing When Opening Source from Component
- When opening a source from the component, the source type is not displayed. This issue makes it difficult to identify and categorize the source properly.
- 738 - Mismatch in Source File ID between Item Editor and Components View
- The source file retrieved from the item editor and the components view does not have the same ID. As a result, the file will be opened twice if it is called from both the item editor and the components view. This discrepancy leads to redundancy and potential confusion for users.
New and Noteworthy in OCTO V1.2.3 (Milestone 3: May 15, 2024)
| 605 - Solution and object decoration | Solutions can have issues. These are shown using decorations.
|
|---|
| Create new objects | Octo now enables the creation of new objects in VSCode and the Web.
|
|---|
| Enhancements to Source File Editor | Enhanced Alert Mechanism: In case the source file cannot be saved for any reason, an alert warning will immediately pop up to notify you. Additionally, the editor will intelligently switch the source file to a read-only state, ensuring that you can still access and review the content without risking any unintended alterations.
|
|---|
| Enhancing Task URL Navigation for User Flexibility | Currently, when a task URL is clicked, users are directed to the Solution tab within the item editor by default. While this provides a quick access point, it limits user control and flexibility. Recognizing the importance of empowering users, we propose a solution to allow customization of the default tab selection through URL parameters.
|
|---|
| Open an Octo Workspace in VS Code | You can now open a workspace in VS Code. This is one of more coming steps aiming to make the interaction with an Octo workspace between the web client and VS Code simple, stateful and seamless.
|
|---|
| Open a plugin in New Tab | Each linked plugin can now be opened in own browser tab.
|
|---|
| Improved Source Editor with Enhanced Syntax Highlighting | The source editor now boasts an upgraded feature set, including advanced source code syntax highlighting. Notably, it can seamlessly showcase the syntax of the most prevalent source code extensions, enhancing readability and usability for users.
|
|---|
| Enhanced Source Editor with Production Comparison Feature | The source editor has been upgraded with a powerful source comparison feature. Users can now easily compare their code with the production version from an Object file, facilitating efficient editing and seamless saving of changes.
|
|---|
Other issues/enhancements resolved
- 643 - Signout form has html error
- An HTML issue caused a UI glitch in the signout form. This has been fixed.
- 202 - Change task date does not work on task API
- The following error is thrown: Value 1221129 is invalid for expectedCompletionDate.","messageID":"OMQ600A"
- 556 - Initial load reads the tasks more than once
- Initial load reads the tasks more than once
- 557 - Octo client - Enable users to clear cache from menu
- Octo users need sometimes to clear the browser local storage/cache for different reasons. Make it easy to do so from a menu instead of having to go through browser dev-views.
- 558 - Octo client - Refactor connection list conflict wizard to use the ConfigManager
- The connection list conflict resolution wizard page should use the central TD/OMS Configuration Manager.
- 559 - Octo client - TD/OMS configuration dropdown
- Recheck the TD/OMS configuration switching and caching.
- 561 - Octo client - Make ready the TD/OMS code for M3
- Make a copy of TD/OMS code base and set needed parameters to be used for milestone 3.
- 562 - Work-Management Task Fetch Returns Empty Result After Refreshing Page with "Current" Filter Applied for Programmers
- Upon refreshing the Work-Management page while filtering tasks by the "Current" filter and being designated as a programmer, an unexpected issue arises. Post-refresh, the task fetch operation fails to retrieve any tasks, presenting an empty task list. This critical setback disrupts the smooth flow of work management, particularly for programmers who heavily rely on this tool for task organization and prioritization.
- 563 - Inconsistency in Spool File Opening
- Source Editor Visibility Issue
- Currently, there exists a discrepancy in the behavior of opening spool files in the source editor. While the spool file can indeed be opened in the source editor, if the source editor window is hidden, the spool file opens in a hidden manner as well. Implement a solution that ensures the source file editor is brought to the forefront upon opening a spool file, regardless of its previous visibility status.
- 564 - Transfer wizard issues
- The overview page is not shown when we have conflicts to confirm; The overview page is not grouped by library list
- 565 - Optimization of Transfer Wizards Utilizing Recent Octo Wizard Enhancements
- Recently, numerous optimizations have been introduced to the Octo wizard, enhancing its efficiency and performance. However, the prototype wizards within our reference system have not yet been implemented with these functionalities. This issue tracks these changes. The goal is to prove that the new base classes are fit.
- 566 - Pagination Functionality Failure in Connection List Component
- The pagination feature has been incorporated into the connection list component to enhance user experience by efficiently managing large datasets. However, an issue has been identified where the pagination functionality does not work as expected. Specifically, clicking on a page initially functions correctly, but subsequent attempts to navigate between pages result in the failure to reload data.
- 568 - Octo VSCode - Read plugins automatically
- Let Octo VS Code read automatically all the plugins available in the Octo market.
- 569 - Spoolfile view refresh does not work in VSCode
- The spool file refresh does not work in VSCode. See attachment,
- 572 - VSCode picks up and old spoolfile
- When I double-click on the spooled file in the spool file view, sometimes an older version of the same spool file is shown. It looks like VSCode cashes a spool file with the same name and shows that. Open in the browser on the spooled file does show the correct data.
- 573 - Add to build queue does not work in VSCode
- When the source is saved, or the add to build queue options are selected. Nothing happens in VSCode.
- 575 - Inconsistent Error Message Display in Form Octo Wizard
- In the Form Octo Wizard, there appears to be an inconsistency in the display of error messages when attempting to change the message type from "error" to "info". Despite the attempt to modify the message type, the wizard consistently displays error messages instead of the intended information messages.
- 576 - Decoding Issue with Copyright Symbol (©) on Server Side
- When attempting to save a source file containing the copyright symbol (©), the encoded string is sent to the server. However, upon receiving the encoded string, the server encounters a decoding failure.
- 578 - Octo - Let entities provide their own URL query parameters
- An Octo entity may provide the URL query parameters necessary to build its state when loaded from a link within a UI component. As a result, each Octo entity may be linkable.
- 577 - Octo VSCode - Automate event topics registration
- Automatically detect a plugin registered event topics and register them in the VS Code WebView view.
- 584 - Task Form Application Sorting Issue
- The task form within our application is currently experiencing an issue where applications are not displayed in a sorted manner. This lack of sorting impacts the user experience and makes it challenging for users to efficiently navigate through the applications. To enhance usability and organization, it's crucial that applications are displayed in a sorted order within the task form.
- 585 - After switching configurations these error messages appear
- After switching configurations, error messages appear: Unauthorized or expired token, please log in again (on build queue and spool file component).
- 587 - Error in OCTO Startup
- Missing Required Field 'appCode' in Components Plugin
- Upon initiating OCTO, an error is encountered originating from the Components Plugin. The error message specifies that a crucial field, 'appCode', is missing.
- 588 - Work Management Filter Issues
- In the work management filter feature, we have identified two significant issues that are impacting user experience: Selected application disappears after a hard refresh; Filter retains data of current config after switching to another config.
- 590 - Octo VSCode - Upon reload, close erroneous editors
- If an Octo editor is open and you reload or restart your VS Code, that editor will show up with an error that the file cannot be found.
- 591 - Octo VSCode - Reload all plugins upon sign in/out
- In VS Code, Octo plugins are not reloading as a reaction on a sign in/out events
- 592 - Enhancing Source API
- Revise Client Model and Implement Updates by Octo
- The Source API requires revision to meet evolving user needs and optimize performance. This issue aims to initiate the process of enhancing the Source API by revising the client model and implementing necessary updates by Octo.
- 593 - Task Selection Memento Feature Fails to Persist in Workmanagement Plugin
- The Workmanagement plugin functionality, the "Memento of Task Selection," is currently experiencing a persistent failure to retain the selected task.
- 598 - Loading a Task from URL Prompts Login Despite Existing Local Storage Login Data
- When attempting to load a task from a URL within the item editor, the system prompts the user to log in even though login data from local storage already exists.
- 599 - Customizing Default Tab Selection in Task URL
- Currently, when a task URL is clicked, the item editor displays data within tabs such as Solution, Details, and Ratification. However, the Solution tab is automatically selected by default. To offer users more control and flexibility, we aim to implement a solution where the default tab selection can be customized through URL parameters. This enhancement empowers users to define which tab will be automatically selected upon clicking the URL, enhancing user experience and efficiency.
- 600 - Octo VSCode - Plugins views not showing all plugins
- Upon reload in VS Code, the plugins view can't initialize the plugins anew as they're already registered
- 601 - Octo VSCode - TD/OMS plugins should all react on the sign in/out events
- In Octo VS Code, - the TD/OMS plugins should all react on the sign in/out actions either showing the sign-in form or plugin content.
- 602 - Incorporating Last Change Date in Source File API for Client-Side Updates
- With the recent addition of the last change date to our source file API, it's essential to update our client-side functionality to leverage this information effectively. This enhancement aims to regenerate the API to accommodate this new feature, enabling clients to retrieve changes efficiently and reuse the last changed date for updating the source after saving alterations.
- 607 - Octo client - Welcome page editor in admin mode malfunctioning
- An octo admin/owner should be able to view the welcome page editor when selecting the Welcome link from the avatar sub-menu.
- 608 - Octo client - The components plugin not retaining its content from memento
- The components plugin is not loading its content from a memento state.
- 610 - Update Database Entities with Enhanced Versions Featuring Key Fields Retrieval
- Currently, our system utilizes database entities that lack a method for efficiently retrieving key fields. To enhance functionality and optimize operations, we propose replacing the existing entities with newly enhanced versions. These enhanced entities will incorporate a method capable of retrieving the key fields associated with each entity.
- 611 - Octo client - Replace colors in HTML files with the template ones
- When common colors styles are defined in the core templates, plugins' HTML files should use them instead of re-defining their own within the file.
- 612 - Octo & WebContainers API Integration
- 614 - Old database entity "CreateObjectMonitorExtended" refactored to "CreateMonitorExtended" in the new database
- The legacy database contains an entity named "CreateObjectMonitorExtended," while in the new database, this entity has been refactored to "CreateMonitorExtended." This situation poses a compatibility issue during data mapping.
- 615 - Promote and Checkout Functionality Fails
- Transfer Process Halts at Selection Stage
- Users attempting to promote items and proceed to checkout encounter a critical issue where the transfer process stalls indefinitely at the selection stage. This impasse prevents users from completing their intended actions, disrupting workflow and potentially causing delays in important tasks.
- 617 - When Closing One Item Without Selection in the Editor, the Following Item Displays Empty Content
- When two items are open in the item editor, and the user selects the second item and then closes the first one without actively selecting it, the editor fails to display the content of the second item correctly. Instead, the content area appears empty, leading to confusion and potential data loss.
- 618 - Octo VSCode - A wizard should close upon Finish button click
- An Octo wizard plugin should be dismissed upon finish click when opened in VS Code UI.
- 619 - Octo VSCode - Octo plugins loaded at the bottom section keeps loading
- If the Octo plugins view is collapsed, then the plugins opened at the bottom VS Code section keep loading.
- 620 - Octo Client - Regroup the local context menus
- Regroup the context menu (the ones trigger by the dots) to make it shorter and easier to navigate.
- 621 - Update Component Imports to Utilize TdomsApiNamespace Instead of Hard-Coded Version Plugin
- We've identified a critical issue where certain components within our system are importing classes using hard-coded version plugins. To resolve this issue comprehensively, we need to replace all these imports with the class TdomsApiNamespace.
- 622 - The view header should not scroll out of focus
- Bottom+Right ViewStack
- When we scroll in the bottom viewstack then the header scrolls out of focus. We can then also not resize anymore.
- 624 - VSCode
- Source save fails with special characters
- The source fails to save correctly in VSCode. I have added a special © character in the source. This works on the web.
- 625 - Unsaved Changes Prompt Not Dismissible
- When a source file is open and has unsaved changes in the source editor, closing the editor window prompts a save dialog, as expected. However, upon clicking the "Cancel" button in the save dialog, the dialog remains open, which is inconsistent with standard behavior and creates a usability issue.
- 627 - Octo Client - Sections toggler issues
- Some sections toggler issues still persist: See issue for more details.
- 628 - Octo Client - The tile toolbar in the middle section
- Some sections toggler issues still persist: See issue for more details.
- 630 - Octo VSCode - Add 'Open in VS Code" menu option
- Given an Octo URL, make it possible to open VS Code from the web client then activate the Octo plugins. (If both already installed, of course).
- 631 - Octo client - Add 'Get link" to plugins' main toolbar
- Add a toolbar menu entry to all plugins that implement the Linkable interface.
- 642 - Source Editor Crashes Parsing DDS Files
- When attempting to parse DDS files within the source editor, users are encountering frequent crashes. Upon parsing DDS files, the editor becomes unresponsive and ultimately crashes, resulting in potential loss of unsaved work and frustration.
New and Noteworthy in OCTO V1.2.2 (Feb 21, 2024)
| 449 - Replace icons to install and remove a plugin | The icones to install and remove a plugin have been replaced. The new icons are visible below.
|
|---|
| Generate database entities in the type script | Created database entities in TypeScript corresponding to the database model.
|
|---|
| Task Ratification | Task ratifications can now be displayed directly within the task item editor, enabling users to easily confirm or approve tasks from this interface.
|
|---|
| Task Ratification Filter in Work Management | The work-management system now features a dedicated filter designed to exclusively display task items that necessitate ratification.
|
|---|
| Spool File Plugin | The spool file plugin is now fully operational, allowing seamless access to spool files. Users can effortlessly view spool files within the interface, and with a simple double-click on any spool file row, its contents can be displayed directly within the source editor.
|
|---|
| Build Queue Plugin | We have added the build queue plugin to Octo. This program will cut your build times in half by utilizing clever parallelization techniques. Dependencies are added to the queue automatically when an object is queued for compile.
|
|---|
| 462 - Connection List plugin | We have added the connection list plugin to Octo. Now, there are two options available: either connect the object directly by selecting "Connect," or connect all the references by choosing the "Connect with Rules" option.
|
|---|
| 482 - Solution Conflict in Connection list | Now, it is possible to resolve the solution conflict by referring to the connection list. By default, the action would be to select connect, and the "Alternative" column would remain blank. When an alternative action is chosen, the value in the "Alternative" column will be displayed.
|
|---|
| Source Editor Enhancements | We have added the following items to the source editor:
|
|---|
| Memento and State Link Sharing for Workspaces | The Octo workspace, formerly referred to as the perspective, has undergone significant enhancements:
|
|---|
| Plugin Multi-Version Support and Plugin Info | Depending on the TD/OMS API configuration, Octo will load the appropriate version of TD/OMS plugins. We've added a view to display plugin-related information, including the URL API provided by each plugin
|
|---|
| Octo Plugin and Wizard Linkability | We're striving to ensure that every Octo component can be accessed and viewed through a link. We've improved the context menus by adding link options where appropriate. Additionally, the majority of wizards can now be accessed via a link.
|
|---|
| Octo Integration with VS Code | We've enhanced Octo's integration with VS Code with the aim of providing you with the same functionality available on Octo in the web.
|
|---|
| Component URL Tracker for Displaying Source Component in Source Editor | Now, it is possible to view the source component linked to a specific URL directly within the source editor.
|
|---|
| Add Max Line Length to the source editor | With the recent enhancement to the source files, you can now visualize the maximum allowed line length directly within the source code editor.
|
|---|
| Add Promote/Checkout Wizard Tracked URL Handling | Now, you can efficiently manage tracked URLs directly within the promote/checkout wizard.
|
|---|
| Enhance Configurability for Tracked URLs | The capability to modify configurations from tracked URLs has been realized and is now fully operational.
|
|---|
| Add Dark Mode to Transfer Wizard Pages | The transfer wizard pages have been enriched with dark mode functionality, providing users with an improved visual experience.
|
|---|
Other issues/enhancements resolved
- 646 - Create New Object Issue
- Upon selecting the copybook, the source file should automatically populate from the corresponding field in the New Object Templates file.
- 644 - Connection list REST API does not work
- Currently, we're receiving a 400 response instead of the expected 200 due to a recent update on the server side.
- 616 - Solve solution conflict stopped working
- Solve solution conflict was stopped working.
- 597 - OCTO - Build queue is not working correctly
- The attempt to load the build queue from the URL does not produce the expected outcome.
- I02647 - OCTO - Build queue issue
- When we click "add to build queue," only the chosen solution should be included in the queue, instead of adding all solutions for the task.
- 552 - Open the solution conflict wizard with the link
- The solution conflict wizard can be accessed through the link provided in OCTO.
- 579 - Add a new field Time in the Build Queue.
- Introduce a new "Time" field within the Build Queue plugin.
- 567 - Build queue is not being displayed
- When clicking on the task to add the build queue, the build queue plugin fails to appear.
- 418 - Synchronous Reading of Large Source File Results in Encoding Error
- When attempting to read a source file with a large content synchronously, we encounter an encoding error. The issue arises from the current process of reading the file, where the encoded chunks are first retrieved and then encoded. The correct approach is to encode each chunk separately and then concatenate all encoded results.
- 421 - Make Octo support versioned plugins
- Octo support now installing a plugin that has many versions
- 423 - Octo client - Update TDOMS plugin to support multi-version
- Keep TD/OMS plugin code per milestone version so that old version code can be still fixed and served
- 422 - Unable to Display Components in VSCode: Implementation of VSCode WebView for Octo Components Integration
- Currently, we are experiencing an issue where the components are not being displayed within VSCode. This is issue has been successfully resolved.
- 427 - Remove "TD/OMS" Prefix from Current Plugins
- The task involves eliminating the "TD/OMS" prefix from the names of all existing plugins. This change should be implemented uniformly across all plugins to ensure consistency and clarity in naming conventions.
- 432 - Octo client - Show plugin info such as version
- UI to to show plugin info such as version.
- 437 - Octo client - The install link not showing up
- When there is no plugins installed yet, an install-link should show up which is not..
- 438 - Promote Transfer Workflow Malfunction
- The Promote Transfer action is not adhering to the intended workflow, leading to disruptions in information collection, pre-processing validation, and result display.
- 441 - Single Click Row Selection Failure on Build Queue
- The current functionality for selecting table rows is experiencing a usability flaw. When users attempt to select a row by clicking on it, the row doesn't highlight until a double-click event occurs. This behavior is inconsistent and not aligned with the expected single-click selection.
- 442 - Build Queue Issue
- The build queue shouldn't be triggered when selecting either the task or the solution.
- 444 - Correct Spelling Errors in tdoms-build-queue
- The CompileQueue API schema contains a misspelled property, "processingArrary," which needs to be corrected.
- 445 - Implement Authorization for "Confirm" Button in Transfer Conflict Resolution
- Currently, during transfer conflicts, users are prompted to resolve issues by clicking the "Confirm" button. However, the use of the "Confirm" button requires proper authorization, which hasn't been implemented yet. This issue entails adding the necessary authorization mechanisms to enable the seamless functionality of the "Confirm" button during conflict resolution in transfer scenarios.
- 447 - Uncaught DOMException: Failed to execute 'setAttribute' on 'Element': ';' is not a valid attribute name
- After initiating OCOT, the following error was triggered:Uncaught DOMException: Failed to execute 'setAttribute' on 'Element': ';' is not a valid attribute name.
- 450 - Tracked URL Not Working in Work Management, Item Editor, and Components
- The tracked URL provided is not functioning as expected in the following views: work-management, item editor, and components.
- 451 - Octo client - Let the checkout component use the new wizard core
- The checkout component should implement and use the wizard types from the Octo core.
- 456 - Update Promotion and Checkout Implementations for OCTO Core Wizard Integration
- With the recent implementation of the wizard in the OCTO core, the existing implementations for promoting and checking out of the wizard need to be revised to align with the new OCTO core wizard structure. This issue involves ensuring that the promotion and checkout processes seamlessly integrate with the updated wizard functionality in the OCTO core.
- 481 - Change the solution type in the Connection list plugin
- Now we can change the solution type of the object in the Connect list plugin.
- 497 - UserId Not Consistently Added to ConnectionInfo Object
- In certain scenarios, we have identified an issue where the user ID is not consistently added to the ' connectionInfo' object. To ensure a seamless and comprehensive user experience, it is crucial to include the user ID during the login process.
- 498 - Update Operation Incorrectly Removes Blank Lines in Long Task Comments
- When updating a long task comment, the system incorrectly removes the blank lines.
- 504 - Refactor Code for Reusability Across Plugins
- Currently, there is a substantial amount of duplicated code scattered across multiple plugins. This redundancy not only makes maintenance challenging but also increases the risk of inconsistencies and errors. To enhance code maintainability and promote a more modular architecture, we should refactor the common code and make it reusable across all relevant plugins.
- 548 - Add a new column in the Solution conflict wizard
- Add a column to the solution conflict wizard to present the conflict message.
- 549 - Build Queue issue
- If the task is selected, the objects are not getting included in the build queue.
- 452 - Octo client - An Octo wizard should be linkable
- Add URL API support to the core wizard handling so that a wizard can be opened from a link.
- 453 - Octo client - Let the Promote component use the new wizard core
- The Promote component should implement and use the wizard types from the Octo core.
- 454 - Octo client - Search box not reacting correctly to theme change
- The search box not reacting correctly to switching between light and dark themes.
- 455 - Octo client - Plugin toolbar
- The plugin toolbar not showing all menus when there is still room to show more.
- 457 - Octo client - Integrate Octo wizard into VS Code
- Make it possible to use the Octo wizard core within VS Code.
- 459 - Octo Wizard Dispose Functionality Not Working
- The dispose functionality for Octo Wizard is not functioning as expected. As a temporary workaround, the hide method is being employed.
- 465 - Octo VS Code: Clicking a link in the WM opens in browser
- Clicking a link in an Octo plugin such as WM or components views within VS Code opens directly in browser.
- 467 - Unable to Add Login Form to PromoteComponent
- When attempting to integrate a login form into the PromoteComponent, a critical obstacle has been identified. The PromoteComponent extends OctoWizardComponent, which, unfortunately, lacks the necessary getOnLoginCallback method. This method is crucial for handling login functionality.
- 468 - Octo client - Let the wizard core takes care of sign-in UI
- The core wizard container should take care of showing the sign-in form and call back its embedded wizard if sign-in action is needed.
- 469 - Octo client - Refactor TD/OMS components sign-in code
- The sign-in code is the same for all Octo TD/OMS components using it. Refactor it to some common place to be re-used.
- 470 - Octo client - Let plugins require some state before and after being installed
- A plugin can require plugins being installed before/after its own install.
- 471 - ngOnInit Method Called Twice When Promoting Wizard Component from Tracked URL
- When attempting to promote the wizard component from a URL that is being tracked, the ngOnInit method is being invoked twice, contradicting the expected behavior defined by the Angular lifecycle.
- 476 - Octo client - Allow a plugin to reveal or install another plugin the Angular lifecycle.
- Allow a plugin to reveal or install another plugin the Angular lifecycle.
- 477 - Octo client - Make the WM plugin pagination stick to the bottom.
- Make the WM plugin pagination stick to the bottom.
- 479 - Update Client Model Due to Changes in ConnectionListAPI
- The client model, which interacts with the ConnectionListAPI, needs to be regenerated to align with the modified specifications of the API.
- 478 - Octo client - Show the Kanban provider name above the login form.
- Show the Kanban provider name above the login form.
- 483 - Octo client - Update the core and plugins to use OctoPluginInfo
- Update the core and plugins to use the new OctoPluginInfo type.
- 485 - Unhandled Multiple Target Environments in Promote and Checkout Transfer Wizard
- The Promote and Checkout Transfer Wizard currently lacks support for the scenario where the Select Transfer Process returns multiple target environments. This results in user confusion and potential errors during the transfer process. The wizard should be enhanced to handle and guide users in selecting the desired target environment when faced with multiple options.
- 487 - Octo client - Update the TD/OMS plugins version manager
- The version of the TD/OMS plugins to load should be first determined by the currently selected configuration by the user.
- 489 - Octo client - Refactor TD/OMS plugins settings handling code
- Local and server-side settings handling is almost the same for all TD/OMS plugins. Refactor it to the TD/OMS core (as config manager) so that it can be globally reused in and outside UI.
- 490 - Octo client - Le the TD/OMS WM use the newly refactored code
- Update the TD/OMS work-management plugin to use the new TD/OMS session and configuration managers located in the TD/OMS core.
- 491 - Octo client - WM configurations and search flags dropdowns issue
- The WM configurations and search flags dropdowns have a layering issue. The first being cut off and the second shows up through the local off-canvas settings panel.
- 492 - Octo client - Monaco editor doesn't show its content initially unless resize
- The Monaco editor being used in Octo client doesn't show its content initially unless you trigger a UI refresh by resizing it.
- 493 - Octo client - Search box component doesn't react on theme change
- Search box component doesn't react on theme change.
- 496 - Octo client - The plugins tile showing no plugins
- The plugins tile is showing no plugins but an empty page.
- 502 - Octo - Keep perspective memento state upon browser reload
- In browser, a perspective should be able to rebuild its memento state upon browser page reload even without a perspective link in the address bar.
- 503 - Octo client - Make the sign-in form label customizable
- Let Octo plugins define their own sign-in form label.
- 511 - Ratification shown for non ratification environment
- If the ratification is not active in the environment, then the ratification groups must be ignored.
- 512 - I am member of two ratification groups but I see only one
- I am member of two ratification groups but I see only one. I am member of both groups.
- 513 - Ratification Groups Displayed as Links Without Corresponding Wizard URL
- The current implementation displays ratification groups as links, but fails to couple them with the appropriate wizard URL, preventing the "Open link in new tab" option from functioning as expected. As a result, attempting to open a ratification group in a new tab does not direct the user to the corresponding wizard in a browser tab.
- 518 - Create OCTO Client Service for infoService API
- The objective of this issue is to develop an OCTO client service for the infoService API. This client service will enable efficient and seamless communication between the client-side applications and the infoService API.
- 522 - Source editor issues
- See the link for more
- 510 - Get link in ratification does not work
- The tracked URL for ratification is no longer functional.
- 516 - Octo client - Make analytics use the TD/OMS config manager
- Refactor analytics plugin code to use the global and unified TD/OMS config manager.
- 517 - Octo client - make buildQueue and ConnectionList linkable
- The buildQueue and connectionList plugins should be able to load and build own UI state from an Octo link.
- 525 - Octo Client - Add the connection list and build queue to Octo VS Code
- Integrate the connection list and build queue plugins into the Octo VS Code extension.
- 527 - Octo client - Make a plugin side space more customizable
- Allow a plugin's layout to consume either the whole page space or just the middle part.
- 528 - Inconsistency in build queue getObjects Method - Incorrect File Name 'OMV1'
- The getObjects method in the build queue is currently returning a data result with the file name 'OMV1'. However, it appears that this file name is not recognized by the result object model. I propose that the returned file name be updated to 'CreateMonitorExtended' to align with the expected naming convention.
- 529 - Octo client - The welcome page not showing up
- The welcome page admin link from the avatar dropdown menu is not showing the right page.
- 530 - Implementing OCTO Client Service for Spool File API and Client Model Generation
- The objective of this issue is to generate a client model and develop an OCTO client service for the Spool File API. This client service aims to facilitate efficient and seamless communication between client-side applications and the Spool File API.
- 531 - Octo client - Allow plugins to show selected content even if not logged in
- Currently, the core will show only the plugin login form (preventing the host plugin from loading) if the user is not yet signed in. A plugin should be be able to show some off-signed-in-wall content necessary for its own good functioning besides the login form. Example: the Kanban should show the available providers dropdown so that the user can select one to login to using the login form.
- 534 - Unnecessary System Info Reloading in Work-Management View
- The current implementation of the work-management view results in the reloading of system information every time the view is reloaded. This leads to unnecessary overhead and potential performance degradation. System information reloading should be optimized to occur only when necessary, such as during a browser refresh, to enhance efficiency and user experience.
- 535 - Octo client - Confirm dialog cut-off in VS Code
- Opening Octo dialogs (such as confirm ones) in VS Code are cut off by the iframe the plugin is running within.
- 537 - OCTO VSCODE: Source lines of big source not fully loaded
- Source lines of big source not fully loaded on VSCode.
- 536 - Octo VS Code - Opening links in browser prohibited
- When running in VS Code, opening URLs is prevented by their sandboxed iframes for security reasons. Use, instead, Octo Command Manager to send native VS Code commands to open links in external browser.
- 539 - Octo client - Unify building wizard page function
- The Promote and Checkout wizard pages have different functions to build their content. One used when reacting on local event and the other when loading from a URL. Unify common code in one function to be used in both.
- 541 - Error Thrown Upon Task Checkout: "The URL is Not Supported"
- When attempting to checkout a task within the system, users are encountering an error message stating, "The URL is not supported."
- 542 - Octo Client : Add spool file plugin to VS Code
- Add the spool file plugin to the Octo VS Code extension.
- 543 - Octo client - An org owner should be able to create org-scope workspaces
- In addition the the org creator, a user added to an org owners list should also be able to create workspaces with org-scope.
- 544 - Octo client - Tour steps malfunction
- The help tours UI not showing all the steps.
- 545 - Issue with Item Editor Not Refreshing Solutions After Task Changes
- When utilizing the Item Editor , we've noticed a critical issue where the solutions fail to refresh properly after making task changes either from the work-management interface or by refreshing from the item editor refresh menu.
- 546 - Octo client - Add connection list wizard to VS Code
- Add the link to the wizard triggered within the connection list plugin so that it also works within Octo VS Code extension.
- 547 - SpoolFile API is changed, regenerate the client model and adjust the appropriate service and related components
- The SpoolFile API has undergone changes, necessitating updates to the client model, service, and related components.
- 553 - Unable to Open Source from Components View
- When attempting to open a source from thecomponents view, users are encountering a malfunction where the operation fails to execute as expected. Previously, this feature was functional, but it appears to have ceased working without any apparent cause.
- 550 - Connection List issue.
- Modified the message that appears when an object is being connected within the connection list. Incorporate pagination functionality into the connection list component. The functionality of the help tour plugin has been restored. Members are not being removed from the connection list as anticipated.
- 639 - Issue in New Object Wizard
- When we click on the "GET LINK" button, the create new wizard fails to populate accurately.
New and Noteworthy in OCTO V1.2.1 (Oct, 18 2023)
| 394 - Enhance Source File API for Efficient Retrieval of Large Source Code | We have optimized the way that very large sources are handled by Octo.
|
|---|
| 393 - Create OCTO Client Service for Solution API | Now, it is possible to disconnect a solution from the item editor.
|
|---|
| 390 - Implement Paging and Context Menu for Task Solutions | We've resolved a user interface issue to enhance your experience. Previously, task solutions and task details were displayed together on a single page, which could become cluttered, especially when solutions were lengthy. Here's how we've made it more user-friendly:
1. Paging Functionality: We've introduced paging, allowing you to navigate solutions easily. Now, you can move through the solutions one page at a time, making it less overwhelming.
|
|---|
| 382 - Adding Connect Menu to Each Component View Item for Object-Task Connection | We've successfully enhanced our component view as requested, allowing users to establish connections between objects and tasks easily.
|
|---|
| 371 - Enhance Source Editor in OCTO to Support Editing and Saving of Source Content | Previously, users could only view source code content within the integrated source code editor. You can edit and save modifications directly within OCTO's source code editor.
|
|---|
| 366 - Implement UI for Promote/Checkout Process | You can now conveniently perform promote and checkout processes from both tasks and solutions.
|
|---|
| 58 - Octo - Allow organization ownership edition | The organization admin panel has been revamped to show owners per organization.
|
|---|
| 361 - Add Octo welcome page | As an Octo organization owner or admin, you can let Octo show custom page to welcome new members.
|
|---|
| 380 - Octo client - Add dynamic UI walkthrough | We've added a brief walkthrough steps or tour to introduce new Octo users to main functionalities of Octo and its plugins.
Example of a tour of the main menu and its trigger button:
Example of a tour of the work-management plugin and its trigger button:
|
|---|
| 386 - Octo client - Revamp the URL API page | We've revamped the Octo URL API page for more legibility and ease of use:
|
|---|
| 378 - Octo client - Add the 'About Octo ' page | We've added an About Octo page that will hold core info about the current Octo build instance, info such as current version.
|
|---|
| 339 - Docker image for octo | A Docker image has been created for the Octo server software. The Octoserver Docker image is based on Ubuntu 20.04, Node.js, MongoDB and of course the Octoserver application. The image can be deployed to Windows with support of the Docker Desktop App and any Linux system supporting docker. The Docker image and accompanying documentation will soon be be made on our Octo download page.
|
|---|
GUI issues/enhancements resolved
- 358 - Octo - Allow organization ownership edition
- Make it possible to add/remove organization owners in the Octo admin.
- 359 - Octo client - Only show organizations to members
- In the Octo admin, only a member should be able to see an organization.
- 361 - Add Octo welcome page
- An Octo plugin to edit a welcome page to view per organization.
- 362 - Octo client - The bottom panel of the perspective not showing up
- The bottom panel of the perspective is not showing up correctly. The latter doesn't show up when this bottom tile contains a plugin. Otherwise, the link to install a plugin is not showing up.
- 367 - Allow a plugin to omit itself from the install list
- An Octo plugin can choose not to show up in the install list.
- 368 - Allow a plugin to reject co-install in the same view
- An Octo plugin can require to be the only plugin installed in a given tile/view.
- 369 - Backend Task Programmer Link Overlaps with Clickable Dropdown Menu Area
- When clicking on the dropdown task menu, the backend programmer link appears to be clickable within the dropdown menu area. This results in the backend programmer link overlapping with the dropdown menu, making interacting with the dropdown options difficult. Ideally, the dropdown menu should completely cover the backend programmer link to ensure smooth and intuitive user experience.
- 370 - z-index Issues Encountered When Attempting to Initiate the Transfer Wizard from the Parent Component
- When attempting to initiate the transfer wizard from the parent component, several z-index-related problems arise within the user interface (UI). The transfer wizard UI elements are not displaying as expected in relation to other components and elements on the page.
- 372 - Octo client - Allow a plugin to hide its whole toolbar
- Allow a plugin to instruct the core to hide/show the whole local toolbar (including the plugin name) conditionally.
- 373 - Octo client - Add a 'Save All' menu contribution entry to the core
- Allow a plugin to contribute a 'Save All' action using the core menu contribution mechanism.
- 374 - Enhance Source Editor in VSCODE to Support Editing and Saving of Source Content
- As of the current version of VSCODE, users can view the source code content using the integrated source code editor. However, a significant limitation exists: the source code editor cannot facilitate editing and saving modifications to the source code.
- 378 - Octo client - Add the 'About Octo ' page
- Add a page to the Settings section to show info about Octo
- 379 - Octo VSCode - Give the option to open a file in read-only mode
- When using Octo file system in VSCode, give the option to open a file in read-only mode.
- 380 - Octo client - Add dynamic UI walkthrough
- A dynamically built user tour to introduce main functionalities of Octo core or plugins. Tour steps should be read from declaratively added HTML attributes.
- 381 - Create OCTO Client Service for Connection List API
- This issue aims to develop an OCTO client service for the Connection List API. This client service will enable efficient and seamless communication between the client-side applications and the Connection List API.
- 383 - In a lot of components, the error alert does not show the details of thrown OctoError
- When an OctoError is thrown within various components of our Octo, the error alert message displayed to the user lacks essential details about the error itself. This lack of information hinders both users and developers in understanding the root cause of the problem and resolving it efficiently.
- 384 - The URL Tracker of the Source Editor Does Not Work Anymore Due to the Latest API Changes
- We have successfully addressed the underlying issues that were causing the URL tracker feature within the source editor to malfunction, ensuring that it is now fully operational.
- 385 - Add help tour to the perspective creation wizard
- Add more explanatory help to the perspective creation wizard.
- 386 - Octo client - Revamp the URL API page
- Revisit the URL API UI for more visibility and user-friendliness.
- 387 - Octo client - Add help tour to work-management UI
- Add explanatory help to the work-management plugin UI when needed for a smoother user-experience.
- 388 - Octo client - Organization and perspective info toasts not showing up
- Clicking the organization and perspective info toasts button not functioning.
- 389 - R&D: ANTLR and grammar parsers
- R&D: RPGLE ANTLR grammar/lexer integration with VSCode language server.
- 391 - Integrate the ANTLR4 code with the Octo language server
- Generate the Typescript code from the ANTLR4 parser and lexer. Then integrate the transpiled code in the Octo VSCode language server.
- 392 - Integrate the Octo VSCode file-system with the language server
- Octo VSCode extension uses its own file system implementation to handle files. Octo embedded language server needs this capability of seeing and reading such files while handling requests from the Monaco editor. Hence, the integration of this file system into the Octo embedded language server.
- 395 - Octo - Implement LSP code completion
- Add the first stage of RPGLE code completion implementation of LSP specs.
- 396 - Octo client - tour UI malfunctions
- The tour UI steps don't hide in some conditions.
- 397 - Octo server - strip out the password form mail failure
- When sending a test mail from Octo admin fails, Octo server should strip out the password from the error response.
- 398 - Octo client keeps loading when first installed
- Upon install and first sign-in, Octo client does't show the expected prompting link to create a perspective. It keeps showing a loader instead.
- 403 - Save Menu in Source Editor Remains Disabled After Changing the Source
- The "Save" menu option in the source editor now becomes enabled, as indicated by a green color and blinking, just as expected. The necessary attention and resolution have been applied to ensure the proper functionality of this feature.
- 399 - Source couldn't be open
- We have to either fill the object code or ifs path not both at the same time.
- 400 - Member attribute is not correct.
- Member attribute was not correctly shown.
- 401 - Change the header caption.
- We need to change the login header caption to "IBMi Login" instead of the component name.
- 405 - Action type Promote fails with multiple solutions
- The task with multiple solutions in different environments was not working as expected with action type PROMOTE.
- 406 - Programmer not filled in
- The programmer drop down is not filled in. It should also contain UNASSIGN which should be the value '*PGMR'.
- 407 - Error Alert Doesn't Display API Response as Title
- The current error alert mechanism in our application is not functioning as expected. When an API call returns an error response, the error message retrieved from the response is not being displayed as the title of the error alert. This inconsistency in the alert title can confuse users and hinder their ability to quickly identify and understand the nature of the error.
- 408 - Show the active solutions in the Object component.
- The active solutions are displayed in the Object component.
- 409 - Show the source location in the object component
- The source location is displayed in the Object component.
- 410 - Octo VSCode - Make of the Octo LSP server an extension
- Package the Octo RPG LSP server as a VSCode extension that can be separately published and installed in VSCode Market.
- 411 - The item editor triggered from task-tracked URL does not populate the programmers list
- When an item editor is triggered from a task-tracked URL, it should automatically populate the programmer's list with the relevant information.
- 413 - Promote Task Always Generates a Response, Even if it's an Error, but Response Data Contains Information About Error Status
- When using the "Promote" feature in our application to transition a task to a different state, it appears that a response is generated regardless of whether the action was successful or resulted in an error. However, the response data contains valuable information that allows us to determine if the response indicates an error or not. This behavior could be confusing and less intuitive for users who expect responses only in successful cases.
- 414 - Add Octo VSCode extension pack
- A VSCode pack extension allows the un/install of multiple extensions from the VSCode market in one go. In our current case, a pack would install, both extensions, the TD/OMS work-management and the Octo RPG language server extensions.
- 417 - Octo VSCode - Remove unnecessary files when packaging the VSIX
- To minimize the VSIX file size, ignore the assets that are only relevant when deploying the Octo client to Octo server but are not so when packaging it as a VSCode extension (.vsix).
New and Noteworthy in OCTO V1.1
| 321 - Add TD/OMS components plugin | The Components plugin enables you to view all objects in your application. Ask your Octo Administrator to install the plugin in a convenient location or create your own perspective.
|
|---|
| 330 - TaskAPI Service Integration for Task Creation | It is now possible to create tasks directly from OCTO.
|
|---|
| 334 - Enable Task Editing and Saving Functionality | You can now effortlessly edit and save your tasks.
|
|---|
GUI issues/enhancements resolved
- 284 - Add the save capability to the Octo language server
- Add the changes save LSP capability implementation to the Octo language server. This prepares our engine for saving sources.
- 295 - VSCode - switching between Octo hosts uses the wrong session data
- In the Octo VSCode extension, switching between Octo hosts uses the wrong user session data. We added multi-session support to the Octo VSCode core so that when loading an Octo component, it reads the right user session data depending on the selected Octo server in WorkManagement view.
- 296 - Analytics Tracker URL Not Functioning
- The analytics feature on our Octo is operational. However, we have fixed an issue with the analytics tracker URL, which is now functioning as expected.
- 297 - RPGLE Editor Lacks Edit and Save Functions, Rendering it Read-Only
- Currently, the RPGLE editor within our OCTO lacks essential functionality, specifically the ability to edit and save RPGLE code. As a result, users are unable to make changes or modifications to RPGLE programs within the editor. In order to prevent any unintentional modifications or errors, we have made the RPGLE editor read-only until the necessary edit and save functions are implemented.
- 298 - Add "Open" Status Option to the Task Filter
- Currently, our task filter provides users with the ability to filter tasks based on their status. However, we have identified a need to enhance the existing status filter by adding an "Open" option. This new filter option will allow users to specifically view tasks that are currently open, providing better visibility and control over ongoing work.
- 299 - Add "Current" and "Unassigned" Programmer Options to the Task Filter
- We should add "Current" and "Unassigned" programmer options to the task filter. This will allow users to efficiently track tasks assigned to specific programmers and identify tasks that are yet to be assigned.
- 300 - Enhancing Task Filter Feature to Enable Efficient Reuse and Local Storage of Last Used Filter
- Currently, the task filter feature in our work management system is static and lacks the ability to be reused efficiently. This limitation hinders the productivity and user-friendliness of the system. In order to address this issue and provide a more effective filtering experience, it is essential to implement the capability to store the last used filter locally.
- 301 - Solutions show NAN in the description
- Solutions show NAn in the description. See screenshot
- 302 - Item editor must show details when called from tracking URL
- Item editor must show details when called from tracking URL. See screenshots.
The Octo VScode work management malfunctions when configuring an Octo server with an Org URL such as: https://octodev.remainsoftware.com/org/OpenAPI
Handle, core-centrally, the HTTP 401 (Unauthorized response status code) by returning a customized error type to the calling plugin so that it can easily recognize it and show the login form.
Make it possible for an Octo component to show up in the left or right side of the VSCode. Currently, it's only possible to place it in the editor (middle) area.
- 306 - Task Filter Changes: Do Not Store Search Tab Input and Options
- Currently, the task filter feature in our application stores the input and options entered by users in the search tab. This behavior can cause confusion and may not always reflect the user's intention accurately. This issue aims to address this problem by modifying the task filter functionality to stop storing the search tab input and options.
- 307 - Multiple Requests Sent on Clicking the Task Refresh Button without Button Visibility Update
- When clicking on the tasks "Refresh" button, the button remains visible even after initiating a request. Furthermore, if the button is clicked again before the first request completes, it results in sending multiple requests simultaneously, causing potential synchronization and data integrity issues.
- 308 - Display Login Prompt for Unauthorized Error (401) When Fetching Data
- When attempting to fetch data from the server, it is essential to handle authorization errors properly. In the case of an unauthorized error with a status code of 401, it is necessary to display a login prompt to the user. This issue aims to implement the appropriate logic to detect and handle the 401 error, ensuring that the user is prompted to log in when their current session does not have the required permissions to access the requested data.
- 309 - Error: JSON does not parse undefined taskFilters map in storeTaskFilters and restoreTaskFilters on VSCODE
- The storeTaskFilters and restoreTaskFilters functions in VSCODE are currently not functioning as expected and are throwing an error stating "JSON does not parse undefined taskFilters map." This issue prevents users from properly storing and restoring task filters in VSCODE.
- 310 - Octo VSCode - let Octo components reload upon Octo sign in/out events
- Already open Octo components should reload upon Octo sign in/out events (both from VSCode controls or one of the Octo components ) to reflect their internal states.
- 312 - Display Configuration Selection Menu on Logout
- Currently, our system's logout functionality does not include the display of the configuration selection menu. This creates a suboptimal user experience as users are unable to conveniently switch between different configurations upon logging out. We need to enhance the logout feature by incorporating the display of the configuration selection menu.
- 313 - Kanban move issues
- Organization logo is not always displayed. Deployment Success message must be displayed from user if passed with value. When filtering and moving, the wrong card is offered as move
- 314 - Saving and restoring nested filter maps as JSON strings currently does not function properly in VSCode
- In VSCode, there is a problem when saving and restoring nested filter maps as JSON strings. While a single map works well, attempting to save and parse a nested filter map results in an error. This limitation forces us to use only single maps to save filters with their appropriate configurations.
- 315 - Inconsistent Error Alert Display When Login Error 401 is Thrown
- When encountering a login error with the HTTP status code 401 (Unauthorized), the expected behavior is to prevent the display of an error alert. However, in certain cases, the error alert is still shown despite the intended behavior.
- 316 - Octo VSCode client - Remember the active Octo host
- When restarting or reloading, remember the active Octo server.
- 317 - Octo VSCode client - Add a command to clear user session data
- In some cases, one needs to clear all locally saved user data.
- 318 - Add the Possibility to Track Solution URL from Solution Editor
- Currently, in the Solution Editor, there is no functionality to track the URL of a solution. This poses a limitation for users who want to keep track of the solution's location or reference it externally. To enhance the user experience and provide more flexibility, we should add the ability to track the solution URL directly from the Solution Editor.
- 319 - When a user is added to an organization it is not visible in his profile
- It is not visible to the user after they are added to the organization. CTRL+F5 will not show the organization. They have to log in and log out of octo to see the organization in their profile.
- 320 - We get this error message after we go to Octo the next day
- When I go to Octo in the morning, I get this error. It is probably caused by expired token.
- 324 - Octo client - Moving a Kanban card to an empty column doesn't work
- Trying to drop a card onto an empty column fails.
- 325 - Octo client - Show the move card response message, if any
- Let the user see a more detailed message upon a successful card move/transfer.
- 327 - Octo client - Only show/allow the delete Kanban card operation if allowed by the provider
- A new optional field has been added to the Kanban provider card schema: is_deletable.
- 328 - Octo client - Show the Kanban card description
- A card description may be provided with the initial card data itself. Or will be fetched using a separate request when its initial incoming value is "-1". Kanban provider card schema is updated.
- 329 - Creating Task API Client Model from Existing OpenAPI File
- We need to develop a Task API client model by utilizing the existing OpenAPI file. This client model will serve as an interface between our application and the Task API, allowing us to perform various operations related to tasks.
- 331 - Octo client - Allow user to view less/more Kanban card details
- Enhance reading focus by viewing less details of a Kanban card.
- 332 - Octo client - Refresh doesn't reflect user organization membership status
- Refreshing the browser doesn't reflect the last status of a user being removed from or added to an organization.
- 335 - Wrong analytics message
- Should not say "Source cannot be fetched". See attachment.
- 336 - Octo Terms and Conditions
- Please let the user check the following before signing up to Octo: https://remainsoftware.com/octo-terms-and-conditions.
- 337 - Octo VSCode File system enhancement
- Add support for file saving, change and deletion handling for Octo files opened with native VSCode editor using the Octo virtual file system.
- 338 - Test the Release , Address Small Problems, and Enhance Documentation
- As part of the development process, it is essential to thoroughly test the release workflow and ensure that all components are functioning as expected. This issue aims to identify and address any small problems that may arise during the testing phase. Additionally, it involves enhancing the existing documentation to provide comprehensive instructions and guidelines for future reference.
- 340 - Url without '/' in an org gives a blank page
- For example: https://octodev.remainsoftware.com/org/remainsoftware vs. https://octodev.remainsoftware.com/org/remainsoftware/
- 341 - Change Default Operator in Wormmanagement Filter from OR to AND
- Currently, the Wormmanagement filter, which is used to search for specific words, employs the OR operator as the default. This means that when multiple words are entered, the filter searches for any occurrence of those words individually. However, it has been identified that this default behavior does not always yield precise results and can lead to increased noise in the search output. Therefore, it is recommended to modify the default operator to AND, which will narrow down the search results by requiring all specified words to be present in the content being searched.
- 342 - Disallow perspective addition/deletion in the main Octo domain for non-admin
- Only an Octo admin should be able to add/delete perspectives in the main domain URL (the one without an organization sub-path).
New and Noteworthy in OCTO V1 Milestone 3 (Upcoming May 17, 2023)
| 267 - Enhanced Task Detail Editor with Task Solution Display | We have enhanced the task detail editor by adding the functionality to display task solutions. Previously unavailable, users can now conveniently view solutions associated with a task directly from the task detail view.
|
|---|
| Displaying Task Solution Content on the RPGLE Editor | Now, it is possible to display task solution content on the RPGLE editor. The RPGLE editor offers a user interface for developers to view and, in the future, modify and compile RPGLE programs stored in source files.
|
|---|
GUI issues/enhancements resolved
- 245 - Add extended description to task details
- At the moment, the task details do not include an extended description as it has not yet been added to the FixExtended file. However, we will retrieve the extended description from the FixDetails file. The data is stored in a sequence in FixDetails, with each sequence representing a line of the extended description.
- 246 - Email templates fail to load upon installation
- When signing in the very first time as admin to configure the email (then saving it) , a test mail will be sent with an empty mail template.
- 247 - Octo server - Recheck the DB indexing
- Some schema fields misbehave when updated on DB complaining about the 'unique' indexing property. Should be rechecked on a blank DB.
- 248 - Add Octo configrations as menu selection to workmanagement and item editor plugins
- Switching between different Octo configurations is currently a challenging task. To address this difficulty, it would be helpful to introduce a menu selection for easier configuration switching.
- 249 - Octo VSCode - Octo client assets and non-full web paths fail
- When ruining within VSCode, Octo client's assets and other non-full web paths fail. Mainly because of the local location Octo client is placed in and the custom URL naming VSCode uses.
- 250 - Improve tasks search to accept any search word
- The current search text input for tasks is limited to accepting only specific pairs of field names and values, which restricts its effectiveness. To make it more useful, the search text input should be enhanced to allow any search word to be used.
- 251 - Pagination is not reset after a configuration switch
- After switching a configuration, the pagination should be reset to the first page.
- 252 - Octo VSCode - Add commands execution bridge
- Enable VSCode commands execution from within an Octo component when running in VSCode.
- 254 - Octo client - Page keeps loading after signing in
- The page keeps loading after signing in. Issue reproduction: 1. Sign out. 2. Refresh page once or twice. 3. Sign in
- 255 - Octo - Make the perspective usage scope-based
- Perspective scopes:
- Private: only visible to the creator/owner.
- Organization: visible to all members of the organization the perspective belongs to.
- Public: visible to all Octo users.
- 256 - Add task status filter
- To enhance the task filter, it would be beneficial to incorporate a filtering mechanism for task statuses. A viable solution to achieve this could be to implement a dropdown menu that includes the current task status options, allowing users to filter and display relevant tasks.
- 257 - Octo client - Kanban search malfunctions
- The search box in the Kanban plugin within Octo is not working correctly.
- 258 - Octo client - Remember the selected Kanban board when reloading
- The selected Kanban board is not remembered after clicking the refresh button.
- 260 - Make it possible to clear the search-box dynamically from UI
- To enhance user experience, include a search-box function that informs the user of the current value in the UI input since the value of the search query is only disclosed after clicking on the search button.
- 261 - Octo client - Omit the comments and attachments counts if not provided
- In a Kanban card, don't show the icons for the attachments and comments counts if not provided.
- 262 - Implement dark theme in Work Management and Item Editor
- The dark theme has not been implemented in the work management and item editor. To allow for the use of a dark theme, the HTML component should be modified to accommodate it.
- 263 - Octo - Make the plugin configuration perspective bound
- An Octo plugin configuration visibility should be determined by the scope of the perspective it's installed in.
- I314 - Octo client - Show the organization logo in the active perspective
- Show the organization logo or name on the top left of the active perspective.
- 264 - Octo client - show more info about the active perspective
- Show the perspective info such as the name of the owning organization, the perspective scope, creator and so on.
- 265 - Octo - Perspective permissions
- For now (we'll refine permissions when needed as we go):
- 266 - Integrate the Task Form component into the Item Editor
- To create a new task, users can click the 'New Task' button located in the work management view. This action will open the Task Form Component within the Item Editor, allowing users to input task details.
- 267 - Add functionality to display task solutions on Task Detail Editor
- The task detail editor currently does not display task solutions. We need to add functionality to the editor so that users can view and manage solutions associated with a task directly from the task detail view.
An organization perspective can only be:
- Created by the organization owner or an Octo admin
- Deleted by the organization owner or an Octo admin
- Updated with new plugins addition or removal by the organization owner or an Octo admin.
A private or public perspective can be:
- Created by any Octo user
- Deleted by its creator or an Octo admin
- Updated with new plugins addition or removal by its creator or an Octo admin.
- 268 - Octo server - Open the email transport configuration
- Currently the Octo server only supports the Office365 SMTP transport configuration. Drop this restriction and make it configurable with other transport protocols.
- 269 - Octo client - Avoid HTML elements selection when resizing layout
- When dragging layout edges to resize, random and unnecessary HTML element mouse selections occur.
- 270 - Unable to switch the configuration from Item Editor
- The issue at hand is related to a recent change, which has resulted in the inability to switch between configurations.
- 271 - Upgrade octo models with last version of Database API
- The new Database API has addressed the shortcomings of field-selections, eliminating the need for the where-clause.
- 272 - Octo client - Save the UI state upon reload
- Save user common interaction with Octo UI such as selected perspective, theme, tile widths and visibility.
- 274 - Improve search functionality by making Field Selection case insensitive
- The current search functionality is limiting as it is case sensitive when searching with field selection. This causes a number of issues for users who may be unable to find the desired results due to incorrect capitalization or different letter cases.
- 275 - Octo client - Upgrade Monaco editor
- Upgrade the Monaco editor, we're using within Octo, to the latest version.
- 276 - Octo client - Show organization info when clicking lts logo
- Show more info about the current organization when clicking its logo on the top left of the main page.
- 277 - Add Solution Editor Plugin to Octo
- The proposed solution editor plugin would allow users to view and edit their task solutions within Octo.
- 278 - Octo Client - Upgrade jQuery
- Upgrade jQuery core, UI and theme to 1.13.2. Replace current links with reliable CDN's (as one of the current ones just went offline).
- 279 - Fixing the solutions view resizing issue
- The solutions view is not functioning correctly when the screen is resized.
- 280 - The loading progress is not displayed when fetching solutions
- The Solutions component is a sub-component, and overriding the isLoading flag is ineffective.
- 281 - Add dark mode color highlighting to solutions editor
- The solutions editor would benefit from a dark mode color highlighting option to enhance its usability in low-light environments and for users who prefer darker color schemes. By adding color schemes with sufficient contrast, the text will stand out clearly against the dark background, improving the overall readability of the editor
- 282 - Update database_api to the new version and generate new model
- Our current database_api is using an outdated version and needs to be updated to the new version. This will require updating the codebase and testing. Additionally, we need to generate a new model to take advantage of the latest features and improvements.
- 285 - Integration of OCTO Changes with VSCODE
- Recently, a lot of changes have been made to the OCTO , and it is important that these changes are integrated with our current VSCODE .
- 286 - Octo client - Allow opening text documents from Octo in VSCode
- Extends the Octo event manager to handle opening text documents from an Octo component within VSCode in Monaco editor.
- 287 - Ensuring active applications are always fetched on Logout/Login
- To ensure that the user can easily resume their recent work, it's crucial for the work-management to consistently fetch the user's active applications upon logout/login.
- 288 - Access token not refreshed upon configuration switch
- Currently, when a user switches configuration , the access token is not automatically refreshed, and the old access token continues to be used. This can cause issues with accessing resources in the new configuration.
- 289 - Octo client - Perspective selection doesn't refresh its state
- Selecting a perspective from the Perspectives drop-down doesn't always load and refresh its contained plugins.
- 290 - Octo client - Add user settings to Octo VSCode
- Make the current Octo Angular user settings as plugin and make it available from within VSCode.
- 291 - Octo client - Calling Octo services from within VSCode fails
- Axios, a http client, being used in Octo core services fails to be loaded when directly used from within VSCode
- 292 - Update Dashboard to use dashboard API for data retrieval
- Currently, the Dashboard is using Nodejs to retrieve data from the database. We need to update it to use the Dashboard API for data retrieval instead. This will make the code more modular and easier to maintain.
- 293 - The switch configuration among octo plugins is not functioning properly
- The octo plugins should respond to login, logout, and configuration update through the configuration switch.
New and Noteworthy in OCTO V1.0.2
| 163 - A Kanban card title can also be a link | A card title can link to an external URL.
|
|---|
| The task view of the work management has been added to show the retrieved tasks | The task view enables users to conveniently access their retrieved tasks and obtain the most pertinent information about each task.
|
|---|
| Task details view is add to show more information about a task | If the user wants to view all task details, the task details view now makes it possible.
|
|---|
| 207 - A filtering is implemented in the work management to assist users in retrieving specific tasks that they need | You can now filter specific tasks by typing the field name followed by a colon and its corresponding value in the search bar. Additionally, you can add the field effortlessly by selecting the application and programmer from the dropdown menus.
|
|---|
| 211 - Remote settings changes | We've simplified the remote configuration! You only need to provide the API URL and configuration name to connect with the server.
|
|---|
| Octo Admin. A plugin to manage Octo users, organizations, authentication, email config and templates and more, just in one place. | The first section in Octo admin is the Organizations admin section. Octo now supports the multi-tenancy architecture. As a user/company you can create your own Octo organization for more data isolation and sealing. In this Organizations admin section, you can manage your organization(s) the likes of easily adding, inviting and removing members from your Octo organization.
|
|---|
| Octo Admin / Octo Users Admin | In this Users admin section, you can manage Octo users.
|
|---|
| Octo Admin / Email configuration Admin. | In this Emails configuration admin section, you can manage Octo server mail settings and templates used by Octo to interact with users.
|
|---|
| Octo Admin / Server Logs | In this Logs admin section, you can view the remote on-file-system run-logs of the Octo server.
|
|---|
| Octo Admin / Authentication | In this Authentication admin section, you can search and view users sign-in activities and statues for authentication and security purposes. A settings sub-page in this section is available to configure sign-ins logs periodic purge. And to alert users upon suspicious sign-ins.
|
|---|
| Profile off-page | We've revamped the right-side off-page to show more user info, user organizations and organizations admin links and a link to the new user Settings.
|
|---|
| User Settings | We've added a whole user settings section. A central location for a user to easily manage own stuff. |
|---|
| User Settings / Account | A place to view and edit your own account. We've also added support for 2FA authentication. You can enable/disable 2FA in this section.
|
|---|
| User Settings / Authentication Logs | An additional security support, a place to view your most recent sign-ins to Octo.
|
|---|
| User Settings / Password | you can now reset your Octo password while signed-in. For more security, Octo now requires server side OTP authorization for the password reset.
|
|---|
| User Settings / Profile | We've added a section where you can edit your name, email and avatar. For more security, Octo now requires server side OTP authorization and confirmation for both old and new emails before accepting an email change. The step-by-step UI makes it easy to perform.
|
|---|
GUI issues/enhancements resolved
- 171 - Add Octo user admin UI
- An Octo plugin to admin users, organization, logs and so on.
- 180 - Add tracked URL's to analytics component
- The analytics component does not handle tracked URL's.
- 181 - Handle sign out event on VSCode
- Use the octo handle even to register and handle the sign out event.
- 182 - Add remote configurations to vscode workmanagement viewer
- Fetch all remote configurations and add them to the TdomsTreeDataProvider.
- 183 - Octo - Optionally initialize core services with a target host
- Make it possible to initialize an Octo core service with the host to talk to. Handy in VSCode usage where no address bar.
- 185 - Read the VSCode webview title from the Octo command args
- An Octo URL command expects a human-readable string as the second parameter to be used as the title of the webview to open.
- 186 - Add client request service
- Add the request service, then handles the request REST actions. The service must be added to the Octo TS core.
- 187 - Add sign out to VSCode
- Add sign out button to the TD/MS workmanagement view. The sign out action will delete the user and the session information.
- 188 - Handle source file on VSCode
- Retrieve a source file and display it on the appropriate editor.
- 189 - Add lazy loading to VSCode TD/OMS Workmanagement view
- Add lazy loading to the workmanagement view to display the content of the tasks pages.
- 190 - Add Octo server to Vscode workmanagement
- To start Octo, you have first to add an Octo server to the VSCode workmanagement. The server must be added to the VSCode memento.
- 191 - Add angular reference application workmanagent to display tasks
- Create the angular workmanagement ui to display the tasks and their details.
- 192 - Octo - Add email configuration admin
- Octo email and templates administration.
- 193 - Octo - Add organization logo upload
- Customize the logo of an organization.
- 194 - Octo - Add user avatar upload
- An Octo user can add or edit own avatar.
- 195 - Octo - Add user profile edition
- An Octo user can see and edit own profile.
- 196 - Octo - Make a member invitation link temporary
- A clickable link to invite an organization member should only be valid within a defined period.
- 197 - Octo - Handle organization membership invitation email
- A user can join an Octo organization by following an invitation link.
- 198 - Octo - Add server 2FA support
- Let Octo server support 2FA if the user chooses to.
- 199 - Octo client - Add 2FA service & UI
- Octo support for 2FA authentication.
- 200 - Octo server - Log user sign-ins
- The authentication admin section to handle users sign-ins and related security tracking.
- 201 - Octo server - Add support for 2FA trusted devices
- An Octo user can additionally secure their account by enabling and using a 2FA app from own (mobile) device.
- 203 - Make user settings contribution-based
- Add user global settings and make it contribution-based so that it can be extended easily.
- 204 - Octo - Enable the user to change password in settings page
- An Octo can edit own password from within own profile section.
- 205 - Octo server - Generate admin access token on start-up automatically
- An Octo server security enhancement.
- 206 - Octo client - Allow admin sign-in
- Octo admin plugin is accessible only by users with an admin privilege.
- 208 - Failed to save octo preferences
- Error ater save: Failed to update preference with key: tdoms.configurations.settings.key
- 212 - Octo - show more user info in the admin user search result
- When searching users in the Octo admin, show extra user info such as whether the user email is verified, 2FA is enabled.
- 213 - Octo - Allow an Octo admin to disable a user 2FA
- If an Octo user can no more sign-in while its 2FA is enabled. An Octo admin may disable its 2FA.
- 215 - Octo - Enable a user to change email
- An Octo user may change its email from within Octo settings.
- 219 - Octo - Show server logs in Admin section
- A section in the Octo Admin to view on-file-system server logs.
- 223 - TD/OMS REST API is changed
- Due to API changes the Octo client does not work anymore.
- 227 - Create reference application comment OCTO plugin
- To manage the comment of an task, we need to display the content in a separate view. For this purpose, we need to create an comment OCTO plugin for comments.
- 229 - Update the OCTO database model generator
- The database schemas have been changed, so the database model generator needs to be updated to match the new schemas.
- 220 - Octo client - Unify core and plugins log handling
- An improved and more user-friendly way of showing errors and info in a toast-like UI.
- 231 - Octo - Alert user when signing in from different location
- Octo can now alert users by email if signing in from new locations.
- 232 - Create application info
- We need the application info on the Reference Application Workmanagement.
- 236 - Octo - Require OTP when resetting the password
- For extra security, a user is now required to enter an OTP to edit own password in the profile section.
- 237 - Add pagination to workmanagement
- The work management view shows only the elements of the first page items, a pagination mechanism must be added to show all elements in pages.
- 238 - Octo - Move password recovery UI from server to client
- A revamp of Octo server static pages serving.
- 239 - Initialize task path codes and releases
- Add methods to the application service that can retrieve path codes and releases using the task application. Update the task editor.
- 240 - Octo - Move email confirmation UI building from server to client
- A revamp of Octo server static pages serving.
- 242 - Test, solve small problems and documentation
- Test the workmanagement, solve any small problems and add the documentation.
New and Noteworthy in OCTO V1.0.1
| 163 - A Kanban card title can also be a link | A card title can link to an external URL.
|
|---|
GUI issues/enhancements resolved
- 161 - Update Kanban card attachments and comments count
- Make Kanban card attachments and comments count available either in incoming card data or through separate request calls.
- 162 - Update Kanban card creator and assignee avatars URL
- Make Kanban card creator and assignee avatars URLs available either in incoming card data or through separate request calls.
- 163 - Give Kanban card title the option to be anchor-clickable
- A Kanban card title can also hold a link to an external resource.
- 166 - Make Octo events available to TDOMS VSCode extension
- Event occurring within an Octo component can also be listened to in the VSCode extension using the same Octo event API.
- 168 - Make the Octo user available in the VSCode extension
- The signed-in user in an Octo component that is embedded within VSCodes should also be available from within the embedding extension code.
- 170 - Unify Octo local storage interface for both browser and VSCode
- An Octo component should be able to save local preferences/settings to both browser storage and VSCode memento using the same interface.
- 177 - Kanban board does not clear after selecting it
- The Kanban board was not cleared after it was selected again, resulting in duplicate cards. This has been solved.
- 178 - Octo - Landing page background image showing partially
- The background image shows up cropped from the bottom.
- 179 - Octo - Disable login form fading out when filled in
- Don't fade out the sign-in form if filled in and keep it in focus.
New and Noteworthy in OCTO V1
| 139 - TDOMS Settings | Add REST server and remote system settings.
|
|---|
| 92 -TDOMS dashboard | The TDOMS dashboard plugin displays the predefined reports.
|
|---|
| 149 - Add URL handling Item Editor | Add an item editor that displays the content of an item (task or request) if a URL is entered.
|
|---|
GUI issues/enhancements resolved
- 155 - Add Octo context awareness
- Make Octo aware of the context it is running in. E.g. Normal browser or VS Code.
- 154 - R&D- Octo integration with VS Code webview
- 153 - Add work-management view octo plugin
- 152 - Add task editor
- Display the task editor from the task URL.
- 151 - Octo client - Add sign in callback when no menu contribution is available
- 150 - Octo client - Make the plugin preferences automatically available
- Let Octo automatically fetch a plugin preferences
- 148 - Octo client - Add dark theme
- 147 - Analytics charts do not react to perspective resizing
- Analytics charts do not react to perspective menues
- 146 - Octo client - Enable tile resizing by border dragging
- 145 - Add log in to analytics plugin
- To display the analytics content you have first to log in.
- 144 - Octo client - Make the layout sides and panel toggable
- 143 - Octo client - Refactor collapsible menu contributions
- 142 - Octo client - Enable perspective deletion
- 141 - Octo client - Add incoming URLs handling
- 140 - Octo client - Add services and components error handling
- 138 - Octo client - Encrypt and save Kanban provider JWT to local storage
- Instead of saving a Kanban provider JSON web token (JWT) to the Octo server, encrypt and save it to the local storage.
- 136 - Octo client - Add Kanban provider settings
- 135 - Octo client - Allow a plugin to contribute drop-down menus
- 134 - Generate dashboards using typescript
- Use the axios api to retrieve the dashboards queries from the database and then generate the appropriate charts.
- 133 - Octo client - Enable plugin tile window max/minimization
- 132 - Octo client - Add plugin settings
- 131 - Octo client - Make the plugin tile tabs and toolbar responsive
- The plugin tile header length depends on the number of installed plugins and the toolbar menus being contributed by each plugin which may exceed the available UI space.
- 130 - Display angular google charts on grid layout
- Add an angular component that displays google charts.
- 129 - Make a temporary deploy subdirectory for Octo Angular client
- Deploy the Octo Angular client to a temporary subdirectory (/ts) in the Octo dev site: https://octodev.remainsoftware.com/ts It'll be moved to replace the current Flutter client in due time.
- 128 - Octo client - Add plugin dynamic menu contributions
- Add menu items contributed by an Octo plugin to the local tile toolbar
- 127 - Octo client - Add event manager
- Enable components to listen to each other's events.
- 125 - Octo client - Link the search box with the active plugin
- 124 - Write TDOMS REST API in AXIOS
- AXIOS is compatible with VSCODE and Angular.
- 123 - Add the Octo plugins market to install from
- Show all available Octo plugins to pick and install from.
- 122 - Encrypt Octo data being saved to browser session/local
- 121 - Implement Octo perspectives, layouts and plugins
- 120 - Octo VSCode R&D
- Investigate Octo portability to VSCode
- 119 - Octo Kanban
- Add Kanban implementation to Octo
- 118 - Implement login, registration, password recovery and session in Octo TypeScript
- 117 - Enable possibility to allow multiple servers in plugins
- We can only point to one system in the preferences. It is possible that Octo must point to multiple systems.
- 116 - Add Octo plugins install
- 115 - Octo Typescript project layout
- Divide the Octo typescript project into:Octo Typescript core. Independent from/and used by the following two projects. Octo Angular for both Octo client and server-dashboard -Octo VSCode for VSCode extensions
- 114 - Add perspective layout to Octo typescript