Illuminated Cloud Announcements

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 histo...

2.3.9.7 NOTE:  In the next few months, Atlassian will be  sunsetting  the Bitbucket Cloud issue tracker and wiki features. As a result, I will be migrating the IC  public issue tracker  and  user guide  content into GitHub (using this as a long overdue opportunity to refresh the user guide as I do so). As much as possible, I would like to retain user associations in the migrated issues. If you have logged or commented on issues in the IC public issue tracker and would like to have your migrated issues and comments attributed to your GitHub username, please send both your Bitbucket name and GitHub username via  email  so that I can include them in the mappings used by the issue migration script. No worries if you'd prefer not to provide that information. All other issues and comments will be attributed either to me or to an anonymous/unspecified user, and I will try to include the original Bitbucket username in the issue summary or comment tex...

  2.2.6.1 IcApexDoc integration improvements Updated the  IcApexDoc  integration to support all new options added in  1.0.0.2 : IcApexDoc command-line options can now be read from an options file. ApexDoc can now be generated for a namespace, either specified in the project's  sfdx-project.json  file or explicitly as a command-line argument. Alternatively, if the  sfdx-project.json  file specifies a namespace that should not be used, IcApexDoc can be instructed to ignore it. Org-only Apex types can be retrieved and included in the IcApexDoc run alongside local and standard Apex types so that inheritance relationships from local Apex types to org-only types are properly reflected in the generated ApexDoc. Retrieved org-only Apex types can also be included in the generated ApexDoc if desired. The parent directory of the  sfdx  executable used by IC2 is now explicitly added to the beginning of the  PATH  environment variable befor...

Just under a month ago, many of the Bitbucket Cloud public issue trackers--including IC2's--were the target of a broad spam attack . In response, I changed the IC2 issue tracker from public to private and have kept it that way  ever since per-guidance from Atlassian/Bitbucket support. Today I'm testing the waters by moving it back to public, though the change may be short-lived if I see any new signs of an attack. It looks like there are at least some new features for management of spam issues, and I know Bitbucket is working on a more comprehensive solution to this problem. Again, if I begin to see even a trickle of new spam issues, I'll revert the issue tracker to a private state until Bitbucket support gives the all-clear. Hopefully that won't be necessary, though.

  2.2.5.9 Public issue tracker offline  - I wanted to make everyone aware that the public issue tracker for IC2 is currently  unavailable  due to a  broad spam attack on Bitbucket public issue trackers . As I posted in a recent  update , Atlassian/Bitbucket support is still requesting that affected issue trackers be kept private while they implement measures to mitigate the impact of this attack. In the meantime, please feel free to send any bug reports, enhancement requests, etc., directly to me via  email  or in the  public discussion groups . I have been transcribing these requests into the issue tracker so that they're concretely on my working backlog and available for community feedback once the issue tracker is restored to a public state. I appreciate your patience and understanding while this valuable resource is offline. Issue 1419  - The IDE's browser configuration is now used even for URLs opened via the Salesforce CLI. This al...

A little shy of two weeks ago I posted that the IC2 public issue tracker has been changed to private temporarily due to a broad spam attack on Bitbucket Cloud public issue trackers including IC2's. As a quick update, I have been in active discussion with the Atlassian/Bitbucket Cloud support team (including engineers) who are actively working to address this problem, but as it continues to be a problem, they have recommended keeping affected issue trackers private until they say otherwise. In the interim, I have been conveying bugs and enhancement requests provided by users via email, public discussion groups, and even direct chat into the issue tracker so that they will be concretely on my working backlog for IC2 and available for broader group input once the issue tracker is restored to public status. My hope is that this is resolved very soon, but if it drags on too long, I'll likely look into some alternative host for a public issue tracker. Hopefully that won't be nec...

Someone has decided to start a spam attack on a number of BitBucket-based public issue trackers. This started mid-day yesterday with a slow trickle of spam-type new issues, but overnight the pace increased to a point where I'll be spending quite a bit of the morning cleaning up spam issues. Unfortunately the only mitigation is to change the issue tracker from public to private. I have contacted BitBucket about this but haven't yet received any useful response. I am currently investigating options for a new public issue tracker that can be used to log bugs, enhancement requests, etc. In the interim, feel free to use support@illuminatedcloud.com  to report issues. I apologize for the temporary inconvenience. I will report any further updates here as they become available.