This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

HalCoGen - visibility and public acccess to the CQ database

Other Parts Discussed in Thread: HALCOGEN

Dear HalCoGen team,

I would like to ask you for considering an option to get visible your CQ database for non-TI guys.

Please have a look at another thread where we discussed this topic with your colleague Anthony.

Thanks a lot,

Best regards

Jiri

  • Hi Jiri,Assigning this post to the HalCoGen Team ...
  • Hi Jiri,

    CQ has the provision to expose the ticket info for the outsider ( non-TI ), But it is at every ticket level.

    Let me check with our tools team if there a simple way to consolidate, probably I can add the link to HALCoGen for customers to open the CQ data base.  

  • Hello Prathap,
    yeah, that sounds like a great idea to integrate such a feature directly into the tool IDE. You can imagine that especially for safety relevant project there is a need (a must) to have a clear tool-chain with all (bug, errata, test,...) reports in-time.

    Let me leave this thread still opened - please discuss this possibility with your colleague and insert a conclusion here.

    Best regards,
    Jiri
  • Hello Prathap,

    is there any news regarding this topic?

    Thanks,

    Jiri

  • Jiri,

    I checked with tools team, There are some ways to pull the CQ ticket information's out, but it is not in a way that can be interactive. It is just a static page with information on the ticket, which is more or less like info available in the release note.

    Just wanted to be clear please answer following
    1) Are you looking for feature to view all tickets raised no matter what state there are or just the open ticket only.
    2) Are you expecting to raise a ticket to HALCoGen team through CQ?

    The only project actively using CQ is HALCoGen and all other MCU teams have moved to different tools, so no active support available on CQ, excuse us if there is some delay.
  • Hi Prathap,

    honestly I have not originally stressed my reason for asking about this issue.
    We are forced by the standards and safety & quality requirements to have a clear evidence, reporting, countermeasure and plans regarding 3rd party SW. Of course, we are using HalCoGen as well as Flash F021 library on our project. So my question was driven by the request to get an access to all the information regarding the tool bugtracking, release schedule, etc.
    Yes, there are release notes which contain the list of applied bugfixes and added features - but it would be great to know about already identified but not yet fixed isssues. Sometimes there is a workaround to temporarily fix the existing bug (in an Errata list) or an impact analysis can be performed based on such inputs. Yes, I suppose this kind of information can be accessible just under NDA, no problem.

    So the answers to your questions:
    Ad 1) I would say there is a need to view open (not yet fixed) tickets as well as to get information which tickets have been fixed and closed but not released yet. In other words, to get to know that the issue ABC will be fixed in the release XYZ which is scheduled on yyyy-mm-dd.
    Ad 2) No. The read-only access to the ClearQuest database is sufficient for us. I mean that reporting new issues via this E2E forum is convenient - the place where vendor's and customer's experience is shared.

    Well, there are many bug-tracking systems even cheaper than CQ ;-) Are or will the different tools of another teams be accessible publicly?
    Or, in general, is there another possibility how to get the information I have described above?

    Thanks a lot,
    Cheers, Jiri

  • Hi Jiri,

    I added a Table in HALCoGen WIki Page to captured the issues raised in CQ. I will update it every Monday if there is new CQ's added.  

  • Hi Prathap,
    that is exactly what I have meant - thank you very much for your support!
    Best regards,
    Jiri