Introducing the Embarcadero Quality Portal (QC replacement):

-
Introducing the Embarcadero Quality Portal (QC replacement):
http://blog.marcocantu.com/blog/2014-october-rad-studio-quality-portal.html
http://blog.marcocantu.com/blog/2014-october-rad-studio-quality-portal.html

Comments

  1. Lars FosdalOctober 29, 2014 at 9:28 AM

    Will my open issues from the existing QC be migrated to QP, or do I have to track two systems?  Would you prefer if any issues that I still think is relevant, be reentered in QP?

    ReplyDelete
  2. Dalija PrasnikarOctober 29, 2014 at 10:20 AM

    Marco Cantù I know I have mentioned it before but it doesn't hurt to repeat.

    There are still only two available issue types "Bug" and "Documentation Bug". That is not enough. If nothing more "New Feature" is needed.

    Also, currently there is no way of differentiating between C++ and Object Pascal issues, as well as VCL and FMX related ones. I suggest adding those as separate components, since issue can have multiple components assigned.

    ReplyDelete
  3. Marco CantùOctober 29, 2014 at 10:25 AM

    No, we don't plan doing an automatic migration. I guess for some time this will mean tracking two systems. Re-entering bugs would only cause duplicates, not sure if ideal. We can try to figure out a solution and let you know...

    ReplyDelete
  4. Dorin DuminicaOctober 29, 2014 at 11:20 AM

    hopefully quality starts kicking in soon

    ReplyDelete
  5. Nicholas RingOctober 29, 2014 at 12:11 PM

    Marco Cantù Is QC actually working? For the last month of so, QC Plus hasn't been able to connect, or is the plan to move people over to QP?

    ReplyDelete
  6. Marco CantùOctober 29, 2014 at 2:24 PM

    Nicholas Ring    There is a login timeout issue with the QC client, I think the web interface works. This is something we are trying to get fixed, it is unrelated with the new portal.

    ReplyDelete
  7. Nicholas RingOctober 29, 2014 at 2:32 PM

    Marco Cantù Thanks for the explanation

    ReplyDelete
  8. Dalija PrasnikarOctober 31, 2014 at 5:20 AM

    Marco Cantù How about publishing all currently opened reports from internal JIRA?

    ReplyDelete
  9. Marjan VenemaOctober 31, 2014 at 10:32 AM

    Marco Cantù Not migrating? What do you think that is gonna do to your duplicate count?

    ReplyDelete
  10. Dalija PrasnikarOctober 31, 2014 at 12:37 PM

    Marjan Venema If you file duplicate report it will be closed. Problem is if original report is not available in public, or if it exists in different QC system. 

    I do hope that from now on duplicate reports that do not yet exist in new Quality Portal will get different treatment.

    ReplyDelete
  11. Marjan VenemaOctober 31, 2014 at 1:13 PM

    Dalija Prasnikar Of course it would be closed. My point was that not migrating QC means that EMBA will have a lot more closing to do because many people will not check "the other system" (the old QC) to see if their issue was already reported.

    ReplyDelete
  12. Dalija PrasnikarNovember 1, 2014 at 7:00 AM

    Marco Cantù I can see that people are still adding reports to old QC. Having link to new Quality Portal on QC web pages might be good idea.

    ReplyDelete
  13. Lars FosdalNovember 1, 2014 at 3:25 PM

    You should perhaps also ensure that autosubmitted reports from the IDEs are routed to QP instead of QC.

    ReplyDelete
  14. Marco CantùNovember 2, 2014 at 12:34 AM

    I think some of the comments here are really valuable, and we can consider. This is a transition in progress and we certainly need to get to the point we phase out QC (something that will happen in stages).

    ReplyDelete

Post a Comment