Stefan Salzl Community Champion

Hi @gouris , all the information (JSON) of your created webhook will be sent to the URL defined in the "URL" field of your webhook. So as I got your requirement right this would be the api of your destination ticket system. For testing purpose there are several possibilities of API listeners to fetch data of your webhook:…

Hi @[deleted] I have to add 2 things: * even though I was able to manage to import test results I´m a dev/technical rookie. So it´s not my daily business to read xml but I try to find information with documentation * I mainly use cloud version so I could not directly test things on server =S In reference to your xml:…

Hi @[deleted] , it seems your call is missing the method (POST). This is a call I used succeessfully in the past: curl -H "Content-Type: text/xml" -X POST \ -H "Authorization: Bearer ${{ secrets.XRAY_TOKEN }}" \ --data @"./cypress/test-results.xml"…

Hi @[deleted] and welcome to the community, multipart import takes an xml with a json. Did you try to use „Content-Type: text/xml“? Best Stefan

@Viktoryia Uladzimirauna in case this solves the problem please consider to hit the „Accept answer“ button in order to mark this question as resolved. Best Stefan

Hi @Viktoryia Uladzimirauna Please read my last answer carefully and use {{issue.customfield_11201}} instead of customFieldId. It´s just customfield_xxx (where xxx is the ID) --> no capital letter in customfield --> smart values are case sensitive. Best Stefan

Could you please share a screenshot of your automation rule? I´m not quite sure if we are on the same page and if we are talking about a webhook (which in jira automation is a trigger) - it´s a call from outside that would trigger the rule to run. sending a webRequest (which is an action) which sends a call out of jira.…

Hi @Vitali Fedarau you are welcome my friend. hahaha.....and would enjoy to raise our glasses on this effort with you ;) Really great to know you got that working 💪 AND: It was my pleasure. You owe me nothing haha.....that´s what the community is meant for. We love to seek for solutions and even learn new things :) I…

Would the epic keys for the if condition need to be generated "dynamically" or do you have a fix list of epics and can the be hardcoded?

ooouh sorry.....my bad :/ I did a copy-paste-error. As we are already iterating over lookupIssues we do not neet this information in the if-condition. Here is the correct one: {{#lookupIssues}} {{#if(equals(epic Link.key, "TESA-4"))}} <{{url}}|{{key}} {{summary}}> {{/}} {{/}} iterating over a list is (as far as I know) not…

oh....sorry for the confusion. Guess I found the issue: If you are doing math expressions with smart values it needs to be closed with {{/}}. From your screenshot it looks like this is missing. so try the following: {{#=}} 1.1 * {{issue.customfield_11201}} {{/}} Best Stefan

Hi @adam_quinn as far as i got your requirement right the following automation rule should do the work. (just exchange my date field with your corresponding field). Best Stefan

@Viktoryia Uladzimirauna this still doesn´t explain your use case and the problem you are trying to solve. What exactly does not work? could you please send a screenshot of the whole automation rule/how far you´ve come so far as well as the result of the audit log report. Best Stefan

Could you please add my previous suggestion to a "Log action" and send me a screenshot of the audit log of the activation? {{#lookupIssues}} {{#if(equals(lookupIssues.epic Link.key, "TESA-4"))}} <{{url}}|{{key}} {{summary}}> {{/}} {{/}} Best Stefan

Hi @Viktoryia Uladzimirauna and welcome to the community Could you please further specify your use case in more details? I can´t follow your description. This would make it easier for the community to provide you with a suitable solution. Thanks in advance. Best Stefan

Hi @Vitali Fedarau please try the following: {{#lookupIssues}} {{#if(equals(lookupIssues.epic Link.key, "TESA-4"))}} <{{url}}|{{key}} {{summary}}> {{/}} {{/}} Best Stefan

I just gave it a shot: epic from lookup: {{lookupIssues.epic Link}} delivered the epic keys:

Hi @gouris Could you please explain what you are trying to achieve from a use case perspective as well as how far you´ve come/what you created so far? Best Stefan

I tried to test as far as I understood your requirement correctly. so here is my action in the automation rule: which delivered following result in the email: Of course this needs to be configured according to your JQL. Hope this was helpful. Best Stefan

@Pramodh M forget my last post. Using the accountID DID solve the problem. I just had a weird sorting of my comments....my bad :/ sorry for the confusion. Best Stefan

Hi @Pramodh M I got the same problem and simply adding the accountID doesn´t solve it. Any further ideas? Best Stefan

Hi @Vitali Fedarau , let´s take one step back. Could you please explain the problem you are trying to solve from a functional/use case perspective? So I kinda understand what you are technically doing. I´m not quite sure if I can follow what exactly it should solve. With knowing this it would be easier to follow the steps…

Hmmm.....that sounds really weird 🙄 Unfortunately I‘m not familiar with python and the library „only“ some API stuff. So I‘m sorry I don‘t have any further ideas 🙈

Are you trying to retrieve the payload from the parent and extract the subtask‘s description from that payload?

Hi @Vitali Fedarau , How does your rule look like? What does your filter/query in the lookupIssues actions look like? Could you please provide a screenshot of your automation rule/how far you´ve come so far? Best Stefan

Hi @Vitali Fedarau and welcome to the community, as far as I know variables are stored as string. Using ".asNumber"-method should solve the problem. See the documentation below: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#asNumber I tested the following in my environment successfully…

@[deleted] Thanks for the hint. My bad....I just had the link in my bookmarks that was pointing to v2 🙈

Hi @William Briere , Do I assume correctly that you get the information via Rest API? If so and you calling the issue endpoint it´s not delivering ALL fields by default. There is a query parameter to retreive all fields of the issue. See the link below to the documentation:…

@William Briere The relevant point is that an automation rule´s context/scope depends on the entry point/trigger. Without knowing the whole setting the situation cannot be analyzed accurately. Nevertheless the behaviour you described is about the same field but seems to happen in another context. What exactly do you mean…

Hi @Mallory Sydnor and welcome to the community, an automation rule follows a defined path so to say there is a dedicated event/use case when the rule is expected to run. Could you describe your use case? Which problem are you solving with your automation rule? What is the trigger of your event? Furthermore could you…