Issue tracker not fully functional: "An unexpected error occurred."

Issue #8857 invalid
Derek Hohls
created an issue

When trying to alter the workflow status of any issue on my project, I continually get a "An unexpected error occurred" error in the pop-up window. A colleague reports the same problem. I am running Firefx 26.0.

Comments (15)

  1. Brian Nguyen

    Hi Derek,

    We haven't been seeing this problem on our issue tracker, so I suspect it is something specific to your repository.

    Could you tell us what repository this problem is occurring on? Also if possible could you open the developer console and copy and paste the response of the broken endpoint?

    If you are not comfortable posting this information here, you can contact us privately at

    Cheers, Brian

  2. Brian Nguyen

    Hi Derek,

    Thanks for the information. Unfortunately, I haven't been able to find anything wrong with your repository. So we'll need to see the error that Bitbucket is actually throwing. To do this:

    1. Open the web developer window. This is available under the Tools >> Web Developer >> Web Console
    2. Select the Network tab
    3. Try transition an issue
    4. You should notice an entry show up in the network list.
    5. Select that entry and click on the response tab.
    6. Copy and paste the content of that response.

    I've added some screenshots to assist you.

    Cheers, Brian

  3. Brian Nguyen

    That is very strange, thanks for letting us know. What browser are you using and does that browser have any add-ons enabled?

    Do you have this problem on all repositories or only on a specific one?

    Cheers, Brian

  4. Derek Hohls reporter

    Just a comment. This morning I was able to put an issue "On Hold" without any problems. Same machine, same browser, same repo. I will do some more checks on previous problems.

  5. Jonathan Mooring

    I'm closing this issue for now to remove it from our queue. If you are able to reproduce this problem in a vanilla install of Firefox, please re-open the ticket with more details.


  6. Log in to comment