You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
In our story workflow status we have some status values that reflect the stage of testing.
When it comes to testing the story, we create a test execution for each story containing all the tests associated with the story.
We now like to automate the transition of the story workflow status triggered by the test run status of the linked test issues.
So e.g. we have the story status "Ready for functional testing". Once the test execution has been created for the story and the test status of the test issues = To Do, the story status should be updated to "In functional testing".
Once the test run status for the execution is "Passed", the story status should be updated to "Story accepted - Sprint Review".
I didn't find any way to access any x-ray related field / status values in the Jira Automation Builder. Even not when using JQL filters, as they are quite limited for Jira / X-Ray Cloud.
Could you please let me know if my requirement can be achieved with the current tools X-Ray/ Jira Cloud offers? Thanks a lot in advance!
from my point of view this could through "issue transition" trigger, condition "issue type = Sub TestExecution".
It would be helpful if the execution is created as a Sub-TestExecution in the story. This will help create a parent branch and transition the story to another status (see screenshot).
Hope I got your instruction right and this was helpful.
(btw: as your name seems German or Austrian you could also answer me in German :) I am from Austria)
Hallo @Stefan Salzl , vielen Dank für deine Antwort! Wir verwenden den Issue Type Test Execution (und nicht Sub-Test Execution) da wir in einem team-managed Projekt arbeiten - gibt es unter den Voraussetzungen auch eine Möglichkeit? :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @katharina_rott ,
Da gibt es die Möglichkeit, mit Links zu arbeiten. Setzt jedoch voraus, dass die TestExecutions richtig und immer gleich in den Stories verlinkt werden. Auf linkedIssues kann die automation rule reagieren.
XRAY-interne values (zB passed oder failed) können mittels der internen automation oder JQL nicht abgefangen werden. Jedoch hat ja auch das Issue "TestExecution" die ganz normalen status wie alle Jira issues. Den Status der einzelnen Testruns in der Testexecution muss ja auch von jemandem gesetzt werden. Im Zuge dessen kann der Status des issues "TestExecution" dann auch gesetzt werden, woraufhin eine automation rule dann schon reagieren kann.
Hoffe das war verständlich und hilfreich erklärt. Gib Bescheid, falls etwas unklar ist bzw. es noch Fragen gibt
LG
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Stefan Salzl ,
vielen Dank für die Erklärung! Sprich mit linkedIssues würde es nur funktionieren, wenn neben dem Setzen des Test Run Status (Passed, Failed) auch der Workflow Status der TestExecution manuell gesetzt wird, richtig?
Viele Grüße
Katharina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @katharina_rott ,
Ja genau. Auf den Workflow-/Issue-Status des linkedIssues kann eine Automation-Rule dann getriggered werden.
(So weit ich gelesen habe kann in Jira Server/DC der Workflow-Status über das Execution-Result geändert werden, aber bei der Cloud-Version funktioniert das meines Wissens nicht)
LG
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.