Stefan Salzl Community Champion

Ok got that. So still if you import a test execution file xray will create a test issue for each of the 1000 unit tests in jira (where it will reference the test run in the test execution) - if not exist already. So.... 1) you run your unit tests the first time (cycle1). when you import the first cycle (unit test run)…

Hi @Ajay Taneja let‘s wrap this up to make sure we are on the same page: you imported a result file that covers 1000 testcases —> which means there is a test execution issue created with a test run for each of those tests? is that correct? You said the tests ran several times. does that mean you imported several result…

That would have been my main guess ;) Good to know you got that working and thanks for your feedback

Hi @Christopher Dick Vielen Dank für dein Feedback. Welche Credentials/wie verwendest du diese? Jetzt möchte ich auch dazu lernen. Das kenne ich nämlich nicht :) Wäre es möglich, dass du deine Lösung (evntl. mit Screenshot) hier teilst? (credentials/daten natürlich geschwärzt). Das würde sowohl mir als auch vielen anderen…

Hi @Christopher Dick Gibts hierzu any news? Konntest du das Thema mit deinen Admins besprechen/klären? Falls dies hier hilfreich war/zu einer Lösung geführt hat bitte den "Accept" Button drücken, damit dieser Post als gelöst markiert wird. Das erleichtert es anderen Usern mit ähnlichen/gleichen Problemen eine Lösung zu…

Hi @Flummiboy any feedback on this? could you test the provided solution? Best Stefan

Hi @Elizabeth_Johnson Did you already try to create a rule? If so could you please share your current result and where you got stuck? To add to your post: If you are able to do it for 1 you could repeat this step. see the following screenshot. The marked area could be repeated as often as needed in your rule: Best Stefan

Hi @jvantrease and welcome to the community, Some questions: * In your screenshot it seems your action is in another "line" (like it would be if there is a branch in between). Is that the whole automation rule? If not please provide complete material for the community to be able to do a propper analyze. * you mentioned…

Hi @Jess C could you test the provided solution? any feedback? In case you could test the solution successfully please consider to hit the "Accept" button next to the given answer. This will mark the question as solved and makes it easier for other users to find propper solutions to their problems. Thanks in advance. Best…

Hi @Bo Schlichting I couldn´t stop trying and found out it´s really a timing problem. With adding several "re-fetch" actions and 2 "current issue" branches it worked. So I´m not 100% satisfied with it but if the rule can be delayed in any way (like re-fetch, branching, calling a jql or a webservice just for the reason of…

Hi @Bo Schlichting got your point and got stuck at the same point. Unfortunately and obviously it‘s technically built that the change of the field „Time to resolve“ fires when the action of priority change is completly done therefore it‘s not detected correctly and always refers to thw previous sla. Also tried with several…

Hi @Bo Schlichting ok let‘s wrap this up: The rule should fire/be triggered when the priority changes (as SLA is connected to priority)? And if so it should (of course) return the SLA of the current (changed_TO) priority? Is that correct? So does the rule always return the value of the previous priority? Or only if you use…

Hi @Bo Schlichting https://usemover.atlassian.net/rest/api/2/issue/Time To Resolution?expand=names But get this feedback: {"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}} Same if I try and remove the " " (Space) in Time To Resolution. to call the issue endpoint of the api this…

Hi @Flummiboy it´s kinda awkward and really annoying. That is indeed not working. I kinda got a workaround with the following query: project = <yourProject> and issue not in testRepositoryFolderTests("<yourProjectKEY>", "") Hope this solves your problem. Best Stefan

Hi @Jess C I tested the following rule and as far as I got your requirement right it should provide the expected result: Hope this is helpful. Best Stefan

Hi @Bo Schlichting just tried it with the field name and it worked in my system. You could try the following (case sensitive): {{issue.Time to resolution.ongoingCycle.breachTime.jira.minusDays(1)}} For test reasons I always add a "log action" action in my automation rule to see if my smart value works. this looks as…

Hi @Nareg Karamanoukian I can´t talk for Atlassian and don´t know what they are planning. I just can´t imagine how this should be implemented so in my opinion chances are not very high there will be an out of the box solution. To clarify my thoughts: imho this is more a question of the process. Why would the destination…

Hi @Bo Schlichting Could you please share screenshots of your current automation rule as well as from the audit log. Is there any error shown? Further question: Does the rule operate within the same project or would you like to set the due date in an issue within another project? (I´m asking becase Time to resolution is a…

Hi @Jess C and welcome to the community, what field type is the Reviewers field in your epic? Best Stefan

@Bo Schlichting furthermore: check the correct field_ID in your system ;) not 100% sure if this is always the same. Best Stefan

Hi @Bo Schlichting huuuuuu......that was tricky. But the trickier the more fun trying to solve ;) Found out that time to resolution is stored in objects. so printing the smart value of that field looks like: TimeToResolution: SlaCycleBean{startTime=SlaDateTimeBean{iso8601=Tue Jun 28 08:11:16 UTC 2022, jira=Tue Jun 28…

Got it ;) A kinda tricky solution that would also need some deeper configuration would be to work with webhooks inside your git solution. so eg. to send a webhook from github whenever a pull request is edited and an automation rule in jira grabs this webhook and updates your custom field with the information. see a docu…

Hi @Nareg Karamanoukian General question: What would be the requirement/use case behind that? as already mentioned this information is linked to the special event of a PR. In case it is this important to grab that information later you could create a custom field and fill in the needed information (eg. destination branch)…

You are welcome ;) Thanks for that great feedback @Bo Schlichting I really feel honored. That means a lot to me 🙌🏼 Great to know it‘s working. Wish you a great day. Best Stefan

Hi @Bo Schlichting You can use smart value manipulation for dates. See the following link: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#-- In your case it would be: (if I got your requirement correctly) {{triggerIssue.duedate.minusDays(1)}} Just set your "Edit issue" action to that…

Hi @Hila Ben Halevi - welcome to the community the simpliest way that comes to my mind would be to call the jira api (search endpoint) with the „send web request“ action. see the link below: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get You could then use the…

Hi @Christel Gray first of all and tbh: I´m not that familiar with templates and the confluence automation but I would be happy to try to help wherever I can. If I understand that correctly that "site" is an option that could be changed at any time. right? so what would be the exact trigger? whenever this field gets…

Hi @Dylewski,Rafal - welcome to the community, this be done with confluence API. There was a similar post here in the community: https://community.atlassian.com/t5/Confluence-questions/how-to-get-full-content-body-html-using-confluence-REST-API/qaq-p/710532 Best Stefan

Awesome. You are welcome ;) great to know you got that working. Best Stefan

As your triggerIssue is the epic itself you can´t say "copy from triggerIssue" in your clone action. The triggerIssue (Epic) is the one you would like to have in this field. As the trigger is already on Epic-Level it doesn´t have a field "Epic Link" therefore it cannot be copied from there. Other issues like stories are…