2.4.1.2 release notes
2.4.1.2
- The migration of the public issue tracker and user guide from Bitbucket Cloud to Github is now complete. The original resources are now in a read-only mode and will no longer be available starting August 20, 2026. The new resources are:
- Issue tracker - All issues have been migrated with as much of the original content as possible. A few items of note:
- Some issue numbers have changed, so if you have external references to the originals, you may need to update those not just for Bitbucket vs GitHub, but also for the new issue numbers. The issue titles are (mostly) unchanged, so you should be able to locate the new one easily by title. I've updated all internal links between issues to accommodate for these changes.
- Unfortunately I wasn't able to attribute migrated issues to the GitHub user IDs corresponding to the original Bitbucket issue creator user IDs, but the original Bitbucket user IDs and creation date/time information are included in the migrated issues for historical purposes.
- Original issue comments are now contained within the main issue details with information about the comment creator user ID (as text, not an actual user ID link), comment creation date/time, etc.
- As much as possible, original images and attachments have been preserved in the migrated issues.
- All migrated issues show as being opened by me as there was no good way to have them be opened by the original user ID, even mapped from Bitbucket to GitHub. Of course, any newly-opened issues will have the correct ownership.
- Bitbucket issue components have been migrated to GitHub labels, and the new labels have a much more fine-grained and organized taxonomy.
- Similarly, Bitbucket issue priorities have been migrated to GitHub labels of the form
priority:<priority>. Newly-opened issues in GitHub will have a first-class priority. - I've added issue templates for bugs and feature requests/enhancements. I may add other templates based on observed needs. When opening new issues, please try to use the existing templates — or let me know that a new template is needed — and please try to provide the information requested by the respective template.
- User guide - All user guide content has been migrated and refreshed, so it should reflect the current product state accurately in terms of content, screenshots, etc. I'm also planning to update my issue resolution process so that any change that has user guide impact results in a proper update to the user guide as part of the acceptance criteria. Finally, I'm planning to add new user guide topics for other features such as the Anonymous Apex/SOQL Query/SOSL Query/Log Analyzer tool windows, etc.
- Discussions - Because GitHub has a very nice, first-class discussions feature, I'm planning to retire the Google disucssion groups in favor of it. The original discussion groups will remain in a read-only mode for historical/reference purposes, but all new discussions should occur in GitHub.
- Issue tracker - All issues have been migrated with as much of the original content as possible. A few items of note:
- I've also updated all external references to Bitbucket content — both issue links and user guide topics — to point to the respective new locations. This includes links in IC itself as well as those in the main IC Web site.
- Added convenient links to the Web Site, Terms and Conditions, Privacy Policy, User Guide, Issues, and Discussions in the Illuminated Cloud | Configure Application | About tab.
- Speaking of the IC Web site, this exercise has motivated me to refresh it as well, though that may not happen immediately. Given the value of the user guide refresh, I'm thinking the Web site is also long-overdue for some attention.
If you find any issues from this migrated content, please let me know so that I can correct them.