Recently an MVP brought up that they don’t like the policy of automatically closing Issues when there is no action for 2 years; they explained that if a case was verified it should stay open. All of the other MVPs agreed and threw out possible solutions, which led to a productive discussion. The ideal solution was that Xojo would re-verify the case and close it if it is no longer relevant. We continued evaluating the matter internally and going forward – at the suggestion of the MVPs – cases will no longer auto-close. Instead they will get the “Needs Review” label, we will review them and close them if they are no longer reproducible.

We appreciate the time everyone puts in to let us know if they encounter issues in Xojo, this helps us continue to improve Xojo. If you ever have anything you want to discuss or offer feedback on please reach out to any of us, including the Xojo staff or the MVPs, via PM on the Xojo Forum.

William Yu grew up in Canada learning to program BASIC on a Vic-20. He is Xojo’s resident Windows and Linux engineer, among his many other skills. Some may say he has joined the dark side here in the USA, but he will always be a Canadian at heart.

• Facebook
• X
• LinkedIn
• GitHub
• YouTube

The system brings a lot of improvements and more visibility, but there are some changes. Some users have asked “how do I find the bugs I have reported” or “how do I search for an issue number” and if you haven’t used this system, those may not be obvious.

Here are some tips for using Issues:

When do I use Issues?

Use Issues to let us know you have a bug or feature request for Xojo, the Xojo documentation, our website, or an example project. Discussing these things on the forum can be helpful but in order to officially let us know about a problem, please create a new issue.

For Customer Support, please contact us via email at hello@xojo.com. Contact Customer Support for general questions about licensing, questions about your account, technical support, etc. If you’re not sure, write us, we are here to help and usually respond very quickly.

How do I search for a specific issue?

If you are trying to find an issue by the issue number make sure you put “#” before it. For example, if you’re looking for issue 69360, make sure to type it in the search bar like this:

If you forget to type in the #, your search will not return any results.

To link to a specific issue, use https://www.xojo.com/issue/<issuenumber>.

How do I create an issue?

Click “New Issue” to create an issue. When you start typing in the title field, you’ll see a list of possible matches populate as you are typing which is helpful to see if your issue already exists.

How do I find the issues I have created?

There are many options for searching. If you click inside the search field, you’ll see a pop-up menu with criteria you can choose from like Author, Label, My-Reaction, etc.

To find the issues you created, perform this search using the popup menu: Author = [Your Username]. For example, the search below will find the issues I have created.

You can search for your issues or those created by other users. Keep in mind that Issues uses the same username as the Xojo Forum.

What do I do if my issue already exists?

If you are searching for a problem that you’re experiencing and find that an issue already exists, please add a thumbs up. If you have additional information, you can add a comment by scrolling to the bottom of the issue.

If your information should be kept private please check the checkbox at the bottom: This note should only be visible to Xojo.

How do I bring more attention to an issue?

If there’s an issue you feel needs more attention than others, you can click the thumbs up button to upvote it. Conversely, if you feel there’s an issue that should get less attention, you can downvote it.

Be aware that the more you upvote issues, the less your votes matter. The same is true of downvoting issues though upvoting and downvoting have independent impact. In other words, upvoting several issues doesn’t change the impact you have when you downvote issues and vice-versa.

How do I find the issues I have added a to?

To see what issues you have added a to, search for: My-Reaction = 👍

How do I see the top feature requests from users?

You can search by Popularity using the dropdown menu to the right of the search field to sort your results. It is important to remember that the Popularity list is not our Roadmap.

Note: If you do a search that you like, add a Bookmark to quickly go back to it in the future.

How do I view my recent searches?

Click the icon to the left of the search bar to see a list of your recent searches:

How do I reopen a closed issue?

If you are the original author of an issue you can close and re-open it yourself. You do not have to ask Xojo to do it. If you are not the author and want to re-open it, just leave a comment on the issue to let us know that it still affects you and you’d like it re-opened. Then either Xojo or the original author will re-open it for you.

Does Milestone mean a feature will be coming in that specific milestone?

Just because something has a Milestone listed, that is not a guarantee that it will be fixed or added in that milestone. It means that it is an issue we are considering for that release.

If you want to read more about issues, check out this page in the documentation. Do you have other tips for using Issues? Please share on the Xojo Forum.

The Xojo MVPs give us regular feedback on issues affecting the community at large – sometimes that is about a new feature, early testing of a release or more general matters. Recently the MVPs emphasized to us that bugs that don’t affect a lot of users, but can be really annoying to a small group of users, don’t get much attention. We talked about how to best address some of these issues and since we haven’t done a Bug Bash in a while, we decided it was time to do one.

Nominating a Bug for the Bug Bash

Starting now, each user can nominate up to 10 bugs to be fixed during the Bug Bash. You don’t have to nominate them all at once, we will accept nominations through August 31st. To nominate a bug, post this exact language as a comment on the case(s) you wish to nominate in Issues: [BugBash2022Nominee]. Starting in August, our system will add a Bug Bash label to make it easy to find them.

If you find that a case is already nominated with the Bug Bash label, do not add it again. Per usual, if the case affects you, add a “thumbs up” so we have some idea of how many users are affected by a particular bug. Please note that Feature Requests will not be considered for the Bug Bash.

Not every case that is nominated will be fixed. There are a multitude of reasons for this, but each case nominated will be evaluated and we’ll let you know the outcome.

We hope you’ll participate in the Bug Bash. No case is too old, too small or too esoteric! Submit your nominations today!