Is there a way to create automation rules that are connected to the Zephyr side of issues? I am new to JIRA automation and I was trying to create a rule that would be triggered when a test execution status is changed to fail. I only see options to create a rule when the issue status is changed but the issue status is not what we want to use as the issue status does not get updated during testing. We want to use the test execution status as it is the only place that indicates whether a test has passed or failed. Hope that makes sense. Thanks in advance for your answers!
Were you able to find a solution for this? I think we are looking for something similar.
Is the Zephyr status information stored with each issue, such as with a custom field? If so, you probably can do this using the Field Value Changed trigger and selecting your Zephyr field, followed by a Condition to test what you want to detect.
I suggest trying it to see what happens, and then post an image of the rule if you need more help. Thanks!
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our test execution status is not stored with each issue and we aren't able to add that to the issue because there are several executions of each one. The Field Value Changed trigger is not pulling the information I need it to. Thanks though!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Gotcha... have you tried to ping SmartBear to see if they have a work-around / approach to use with automation:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.