Contributions
Re: JIRA Intregration with QAComplete - Why/How
Hi Kim, A typical situation is a QA team working with QAC for test plans management, opening bugs from QAC and these issues are synchronized directly with JIRAand assigned to developers. Once the bug closed, the status is reflected and testers can do some sanity checks on the corresponding build. The other way around, a typical integration is JIRA user stories getting synchronized with QAC. The QA team writes test cases, links these test cases to user stories, and you get the test case coverage for a specific story / epic, ...1.7KViews0likes0CommentsRe: QA Complete - JIRA Synchronization
Hi Padma, Thank you for having shared your experience, we are facing something equivalent, see here: https://community.smartbear.com/t5/QAComplete-and-ALMComplete/QA-Complete-JIRA-synchronization-your-experience/m-p/148649#M1946 We are in touch with Smartbear's support digging into the issue and I will keep you appraised of the evolution. Quick question: do you have technical plugins such as smart grid, ... in your JIRA implementation or is it a basic JIRA deployment? Thank you, Patrick4.5KViews0likes1CommentQA Complete - JIRA synchronization (your experience)
Hello, We are struggling for some time now with the QAC / JIRA synchronization process and the purpose of this goal is to share your experience on this topic and potentially get some ideas to fix our issue. The environment: - We have JIRA on premise (behind the firewall) and QAC hosted in the cloud - We have a similar JIRA / Zendesk integration in place working smoothly so no issues with firewalls, ... - Several JIRA technical plugins (iDalko Table Grid plugin,Adaptavist ScriptRunner for JIRA,Database Custom Field). Mentioning these as Smartbear support is expecting a conflict with some of them. The use case: - Bidirectional synchronization of stories in JIRA with requirements in QAC (only standards fields such as summary, priority, assignee) -Bidirectional synchronization of bugs in JIRA with defectsin QAC (only standards fields such as summary, severity, assignee) We managed to get some information from Smartbear as to how the integration process is working, namelly: "When an issue change (including creating, updating, deleting of an issue and creating, updating and deleting of comment added to the issue) takes place, an internal jira event is raised. We add a listener for this event that prepare changed data in some way and then send it via POST request to QAComplete Connector service that applies given change to a QAComplete system. The problem: Basically, the synchronization process from JIRA to QAC is not working, the other way around is generally working well. The suspicion from the Smartbear support is a conflict with a JIRA plugin, namely: During a usual routine our listener entry point is called within a thread that has additional metadata, current user's authentication data among it. Since we can't reproduce the problem on our side, we assumed that some of the client’s plugins override the event raising logic and thus our listener entry point is called within a thread that does not have current user's authentication data (and, possibly, some other metadata). Question: Are you facing similar issues with the synchronization process? And in case, any tips / directions to help you fixing this problem. Thank you so much for your inputs. Patrick1.8KViews0likes2CommentsRe: QA Complete - JIRA Synchronization
Hello, We are facing a similar issue with the JIRA / QAC synchronization process. Although the required fields and only standards fields are mapped, the JIRA to QAC synchronization process is not working. Was the problem fixed in your situation and in case, what was the root cause? Thank you so much, Patrick4.6KViews0likes1Comment