Quality Keeps Moving Forward

Posted by on in Blogs

For quite a long time Quality Central (QC) was our issue tracker. It was first developed as an in-house method of collecting and managing issues. Since its launch the internal teams have moved to JIRA, and a pump was set up to pull bugs from QC and post them to the internal JIRA. Unfortunately it didn't always synchronize data both directions very well. 

A few years ago we started the new Quality Portal which is a public facing JIRA instance. This makes it much easier to synchronize with the internal development process. After the new Quality Portal came on line, we switched QC to readonly and let everyone know it would be retired eventually.

That day has arrived. QC now redirects to the new Quality Portal for the web interface. We still have the database, backend and web services available, but that is no longer publicly facing. Having two issue trackers created confusion, so this simplifies things considerably as now the Quality Portal is the only place to to track issues externally.

Both the old QC and the new Quality Portal feed into the same internal system. But QC and QP were never synchronized. So you will not find the old QC data in QP, but that data is available internally for our bug tracking.

This is part of our process of cleaning up and shutting down some of the old web sites and web services. Some other things to keep an eye on is we are moving from CodeCentral to GitHub and GetIt for most of our code and package sharing (CodeCentral will still be around for a while for registered user downloads, but more and more of that will be through GetIt). We have our new Community site which is replacing the old EDN. And we are slowly rolling out a Slack chat for discussions. 

Quality keeps moving forward.


  • Dave Boltman
    Dave Boltman Thursday, 22 June 2017

    There are thousands of unfixed bug reports in the old QC, thanks to loyal Delphi users (myself included). Many of these are mentioned on StackOverflow and other forums, and although some developers may view it as convenient to have them "disappear", the Delphi community would really start losing their loyalty, as we've been waiting patiently for some of these to be fixed for more than a decade. e.g. this QC and documentation do still not match in Tokyo 10.2. It's ok to WONTFIX a bug, but at least fix the documentation, so we don;'t expect it to work a certain way. See Google Cache here: http://webcache.googleusercontent.com/search?q=cache:z6PmOvKumsAJ:qc.embarcadero.com/wc/qcmain.aspx%3Fd%3D55428+&cd=2&hl=en&ct=clnk&gl=za

  • Larry Hengen
    Larry Hengen Thursday, 8 June 2017

    I also have numerous product enhancement requests, bug entries and automated bug reports in QC. It is not very transparent to your customers to have those reports go into a black hole, and yet still have QC automated error report functionality in the IDE generating QC reports. It could also dramatically skew the statistics Marco blogs about to convince users that EMBT is actually producing better quality software and addressing our concerns.

  • Lars Fosdal
    Lars Fosdal Wednesday, 7 June 2017

    When will the internal error reporting in RAD Studio file reports to QP instead of QC? After QC now being inaccessible, there is no way to see what happens to those reports.

    As Josh Kelley points out - our open reports in QC should be ported to QP.

  • Josh Kelley
    Josh Kelley Tuesday, 6 June 2017

    What happens to the old QC entries now? I had logged quite a few bugs there that were still open. Right now, I don't know their status, if they're going to be work on, or whether I should re-report them on QP. Now that QC is gone, I won't even necessarily remember if I ever reported them to begin with.

  • Jay F9562
    Jay F9562 Tuesday, 6 June 2017

    We are switching over to Atlassian & Jira. Any lessons learned would be useful!

  • Please login first in order for you to submit comments
  • Page :
  • 1

Check out more tips and tricks in this development video: