2 results found

1. Support for Assignees at individual Test Steps, instead of the full Test Run
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   received  ·  AdminAlan Roberts (Product Management, qTest, Tricentis) responded

   
   

2. Make enable these events defect_submited, defect_modified of webhook for external defect system (JIRA)

   We are creating automated CI loop with Jenkins and qTest tools. Currently we create a feature to auto tracking JIRA (external defect system) tickets. The feature should automatically put JIRA tickets to repeated failed steps (in qTest, execution part), for new failed steps test engineer create a new JIRA ticket after analyzing an issue. When the new ticket is created and linked to the test step, we expect to get response from qTest webhook with data: PID, ticket summary, ticket status, test step name, test case name, test cycle name/id. Also, we expect to get the webhook request when the JIRA ticket is modified, in particular the ticket status. So could you make enable these events defectsubmited, defectmodified for external defect tracking (JIRA) and add the data to webhook response (PID, ticket summary, ticket status, test step name, test case name, test cycle name/id).

   Thanks in advance.

   We are creating automated CI loop with Jenkins and qTest tools. Currently we create a feature to auto tracking JIRA (external defect system) tickets. The feature should automatically put JIRA tickets to repeated failed steps (in qTest, execution part), for new failed steps test engineer create a new JIRA ticket after analyzing an issue. When the new ticket is created and linked to the test step, we expect to get response from qTest webhook with data: PID, ticket summary, ticket status, test step name, test case name, test cycle name/id. Also, we expect to get the webhook request when the… more

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   received  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close