Stefan Salzl Community Champion

Hi @Hanna Rybina what kind of issues are created in relation with the checkbox? Do they have any relation to the original issue (where the checkboxes are set) like parent-chil or issue link? Fuethermore: Could you please post a screenshot of your current rules/how far you‘ve come to get a better understanding of your…

Hi @Ajay Taneja , AWESOME!!! So great to hear you got that working. Please consider to hit the "Accept answer" button in order to mark this issue as solved. This will make it easier for other users to find a solution in case they are faced with the same/similar problem. Best Stefan

Hi @Ajay Taneja I mentioned this 2 posts before: * set the condition in your field configuration to "optional" globally or If the configuration "required" is set in the custom field settings (global settings) it IS required (even if it doesn´t appear on your screen). The system says: it is required therefore it asks for…

Hi @Ajay Taneja 1. --header 'Authorization: Basic ${{ secrets.TOKEN}}' --> is for the JIRA REST API (as u can see the API call calls the JIRA API 2 lines later). 2. no you don´t have to define those. This is a script I use in my githubAction so it´s out of a yaml script where I had to declare some variables to use later in…

Hi @Ajay Taneja but I will have 100 test executions Even if the import would work it would create 1 test execution including all test runs. May I ask what the reason for that might be to have a test execution for each test case? Mainly the test execution is "just" a container of test runs. A test run is an instance of a…

Ok. Let´s take a step back. first: As I mentioned "create issue" is a native Jira action. Therefore you have to call the Jira Rest API not the XRAY Rest API. Usually when you import a result file it creates a test execution automatically and (if not exist) a test case issue for each test contained in the test result file…

Hi @Ajay Taneja What exactly do you mean with the "Test Plan" page is create? When you import test results it creates a test execution. This is another issue by itself (like test plan or bug or story etc...). The import invokes a create action for a test execution issue. So if the field "components" configured in the…

Hi @Ajay Taneja As far as my knowledge reaches there is no way to set a field directly during xml import (especially as this is a native Jira entity and not xray relevant). 2 things coming to my mind: either: * change conditions for the field (or if you running scriptrunner you could also change the required condition for…

Hi @Ajay Taneja first of all an most important: Please avoid posting with your real token in plain text here. some more questions to further specify your problem: - which framework are you using? - which reporter? - is the components field a required field in your instance? Best Stefan

Hi @Meghana Mallineni as far as I know: the testExecKey is not mandatory (as long as there is the projectKey provided). If the project key is provided a new test execution is created with the results. Nevertheless you could give it a shot if this works in your case. Best Stefan

@Meghana Mallineni Did the quotes solve the problem? Best Stefan

I´m not sure about the different formats of reporters. Xray documentation mainly pointing out the one that are supported but I couldn´t find surefire. In case it doesn´t work I could imagine this has something to with the reporter´s format. If so I would suggest to rather change the reporter (TestNG standard or JUnit) or…

I just checked against my yml file where I import JUnit-xml. There is a difference that I then also checked and found in the docu: The docu has the file part in quotes but not the URL. In your call it´s exactly the other way round. So I would suggest to try the following: curl -H "Content-Type: text/xml" -X POST -H…

Of course.....my bad :o Please appologize 🙏

Hi @Meghana Mallineni Did you check these docs: https://docs.getxray.app/display/XRAY/Import+Execution+Results+-+REST#ImportExecutionResultsREST-TestNGXMLresults https://docs.getxray.app/display/XRAY/Taking+advantage+of+TestNG+XML+reports Don´t ask me why but the docu says to use "Content-Type: multipart/form-data": curl…

It works now. Scriptrunner didn´t like the name of my field as I used the getFieldByName() =S Thanks for your time and input. Best Stefan

Hi @Florian Bonniec Thanks for your input. I need to "rebuild" the out of the box functionality of scriptrunner but I need both conditions to be checked. So normally a behaviour fires whenever I open an issue in edit mode. How can the same behaviour done with script? I need the field to occur required when issue opens in…

btw: Hab im Screenshot gesehen, dass deine Screens auf Deutsch sind :) Du kannst mir gerne auch auf Deutsch antworten ;) LG Stefan

Hi @Christopher Dick Just to make sure I´m on the same page: You already have a Test and created a test execution out of this test? --> there is already a test run for the test within your test execution. And you would like to add a jira standard issue link between those issues? is that right? Just a personal question:…

Amazing @Bill Sheboy 🙌🏼 Even if I‘m not the one who asked the question: Thanks for your great answers and letting me/us learn so much from you 🙏🏼 Best Stefan

I see. tbh: I‘m more familiar with importing test results with built in API. I did a quick research and found this: https://github.com/mikepenz/xray-action according to this documentation the call requires an testExec parameter which I could not find in your yml. Please try to add this option and let us know the result.…

Hi @Meghana Mallineni and welcome to the community, Could you please share your API call from your yml that should do the import? Best Stefan

Hi @Andreas Hedlund , please try the following smart value: {{issue.Producer.emailAddress}} As your automation rule already starting from an epic (so the context of {{issue}} already is the epic) you would not need to add "epic" additionally. Best Stefan

Hi @Jonathan Smith , In order to mention users in fields you have to use the user´s accountID. See a detailed description below: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/#Mention-a-user-in-a-field Best Stefan

Hi @Iain Johnson and welcome to the community, to catch a branch created trigger natively the answer (from my point of view) is: yes, the branch needs to have a jira reference. This is the only connection between gut and jira. Otherwise the branch is created within your git system but how should jira detect when the link…

Hi @Darryl Lee Oh sorry for the confusion and thanks for clarifying this here. Always happy to learn things in more details :) Best Stefan

Hi @Neil Taylor thanks for your detailed description. Tbh. I‘m not very familiar with regex so I just did a quick „crash research“ as I‘m having a hard time following your search pattern. Could you explain why it is \".*(crash).*\" Wouldn‘t that take the () around the string „crash“ into your search? Best Stefan

Hi @Neil Taylor the # in using smart values is eigher used for iterating over a number of results or for calculation. In case it‘s an if that checks 1 result this is not needed. see conditions for smart values here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ Try to leave out…

Hi @Mani , Guess the trigger would be „field value change“. Then you could use the following smart values in a „send mail“ action: * {fieldChange.fromString}} - Returns the previous value as displayed. * {fieldChange.toString}} - Returns the new value as displayed. see the detailled description here:…

🤣🙈 ooouh....well...in this case I couldn‘t share any news I guess 🤷🏻‍♂️ Thanks for letting me know.