Archive

Archive for the ‘Bug reporting’ Category

Using Brisk to file bug reports with Apple

July 11, 2017 Leave a comment

As part of preparing for macOS High Sierra, I need to file bug reports to report problems that I’m finding with the beta releases. As part of this, I’ve started using a tool named Brisk. It helps streamline the process by filing bug reports via a native app on my Mac, rather than having to go through this process:

  1. Open a web browser.
  2. Go through the process of signing into bugreport.apple.com
  3. File a bug report Apple’s bug reporting web interface

Brisk also makes it easy to cross-post the submission of a bug report to OpenRadar. Since bugreport.apple.com is not publicly searchable and only allows developers to see their own bugs, OpenRadar is a way for developers to share their own bug reports and keep both themselves and their colleagues up-to-date on the status of various bugs filed with Apple. For more details, see below the jump.

Read more…

Categories: Bug reporting

Using QuickRadar to file bug reports with Apple

August 26, 2015 Leave a comment

I’ve started filing bug reports with Apple using a handy tool named QuickRadar. It helps streamline the process by filing bug reports via a native app on my Mac, rather than having to go through this process:

  1. Open a web browser.
  2. Go through the process of signing into bugreport.apple.com
  3. File a bug report using Apple’s bug reporting web interface

QuickRadar also makes it easy to cross-post the submission of a bug report to Open Radar. Since bugreport.apple.com is not publicly searchable and only allows developers to see their own bugs, Open Radar is a way for developers to share their own bug reports and keep both themselves and their colleagues up-to-date on the status of various bugs filed with Apple. For more details, see below the jump.

Read more…

Categories: Bug reporting

Wanted: bugreport.jamfsoftware.com

August 2, 2014 2 comments

In working through various issues with JAMF, I’ve noticed that a variety of issues I’ve reported are themselves tied to JAMF’s internal bug-reporting system of defect numbers. At the moment, the only way I get any visibility into progress on those defect numbers is by asking my account manager. My current account manager is pretty responsive, but this seems like a job that can be offloaded from his list of responsibilities. I also don’t always want to open a support call when I notice a bug, sometimes I just want to report it.

Here’s what I would want from JAMF in a bug reporting solution:

  • I want a way to report bugs that I’ve noticed.
  • I want a way to be able to check for myself the status of the reported bug.
  • I also want to know how many other people are reporting this issue. Not just because I’d like to know if I’m filing a duplicate issue, but stats like that may give me some insight into how soon my bug will get fixed.

For a bug report itself, I want:

  1. The ability to upload screenshots and screen capture movies and be able to attach them to the bug report.
  2. The ability to add additional information to the initial bug report.
  3. Email notifications when my bug’s status has changed.
  4. A way for the developer working on the bug to be able to reach out and get more details from me directly.
  5. The ability to see both open and closed bug reports that I’ve submitted.
  6. If I’ve filed a duplicate issue, read-only access to the original filed bug report.

I file bug reports with Apple, so I know the drill. I know not all bugs get fixed as fast as I want them to. Sometimes, they don’t get fixed at all. What I want is more information, and to be able to access that information myself.

As it happens, there’s an existing Feature Request for this already open at JAMF Nation. Please vote it up. Hopefully one day soon, I’ll see that status change from UNDER REVIEW to IMPLEMENTED.

Filing bugreports with Oracle for Mac OS X’s Java 7

February 23, 2013 1 comment

Want to file a bug report about an issue having to do with Java 7 for OS X? It can be tricky to find the right place to submit it, so here’s some guidance for filing it in the right place.


Update: I’ve been informed that it is necessary to install the current JRE of Java 7 from the Oracle JDK7 test site before Oracle will accept bug reports from you.

JDK7 is available from http://jdk7.java.net/, with the download site being http://jdk7.java.net/download.html.

The reason that Oracle does it this way is that they want customers to use Oracle Java SE Support. This is for-pay support and Oracle’s preferred way for non-developer customers to get support.

All that said, if the issue you’re running into also occurs on the JRE from the Oracle JDK site, file a bug using the procedure below.


For example, here’s how to file a bug report for the Java 7 installer for OS X.

1. Go to http://bugreport.sun.com/bugreport/

2. Scroll down to the Submit a Bug section

3. Check the box for Check this box to indicate that you understand this is not a place to receive support….

4. Click the Start a new Report button.

Screen Shot 2013-02-22 at 7.12.14 PM

5. On the next page, go to the Start A Report: section

6. For an installer bug, select the following:

Type: Bug

Product/Category: Java Platform Standard Edition (JDK/JRE)

Subcategory: JDK/JRE installation (install)

Release: Java Platform Standard Edition 7

Operating System: Mac OS X 10.7 (Oracle VM)

7. When ready to proceed, click the Continue button.

Screen Shot 2013-02-22 at 7.14.19 PM

8. On the next page, provide the information requested to file your bug report and click the Submit button when completed.

Screen Shot 2013-02-22 at 7.20.53 PM

Good luck! Filing bug reports doesn’t guarantee that your problem will be fixed, but it raises the odds that it will be. Not filing it may mean that Oracle is completely unaware of the problem and thus will never fix it.

Categories: Bug reporting, Java
%d bloggers like this: