Stefan Salzl Community Champion

Hi @Vikas S , Could you define your requirement in more details and from a use case perspective? What would you like to accomplish? That would make it easier to understand what you tried already and finding a helpful and fitting solution. Best Stefan

Hi @Gail If this follows a standardized process and the subtask does have any special configuration to be detected then it might be possible. Without specifying the subtask into more details the automation rule just sees "subtasks". The Question is: How does the automation rule know which one of the subtasks to notify?…

Hi @Megha Debnath As far as I know you could just do this by knowing which test cases and selecting/adding them manually. In the sub test execution you could say "add tests" and then choose "existing tests". There is also a JQL option but I guess "tests within a certain sub test execution" cannot be resolved. My question…

Hi @Derrick Robinson Some time ago I built something that sounds similar to your mentioned requirement. Please see the attached screenshot (statuses might be updated according to your settings): Please keep in mind: this rule triggers everytime an issue is transitioned to done (in regard of some limits of rule executions…

Unfortunately as it seems this is not possible: But as mentioned before you could use the log work action and add the value from your custom field via smart value. Best Stefan

do you mean: <a href="http://..../.../{{any.smart value}}/andSoOn.html">Release</a> As far as I know this should work. Best Stefan

Hi @Marvin Brand I´m not quite sure about the possibilities with Automation Lite but please check if there is an action that logs work (see screenshot - from cloud): Best Stefan

AWESOME work man 🥰💪🏼🎉

Hi @Harald der folgende Link erklärt die Workflows in Team Managed Projekten sehr gut: https://support.atlassian.com/jira-software-cloud/docs/manage-how-work-flows-in-your-team-managed-project/ Gib Bescheid falls noch Fragen offen bleiben. LG Stefan

As far as I got it right the url shown when opening a version is built something like: <your_jira_domain>/<version_ID>/.... As the versionID could be generated via smart value from the automation rule I guess it could worl to concatenate a string to generate the url. (didn‘t test this, that‘s just an approach I would give…

Not directly. The release/version doesn‘t have a dedicated smart value „url“. Best Stefan

Hi @Andrzej Hull , Here is a more detailed description of valid smart values for versions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--version-- The version itself is not an issue in jira. There is no link provided (according to the documentation). As it looks for me the "url" is kinda…

Hi @Lavern Dowsley according to jira feature request this is not possible currently. You could upvote for the mentioned issue: https://jira.atlassian.com/browse/JRACLOUD-74035 Hope this helps. Best Stefan

Hi @Derrick Robinson I would suggest starting with an "issue transitioned" trigger and then checking for linked issue (with "linked issue" branch) for the required link type. Could look like similar to following: Please let me know if this works. Best Stefan

Guess that‘s then a jenkins specific question.

Hi @Ritik Banga and welcome to the community, I found something similar here in the community (see following link): https://community.atlassian.com/t5/Jira-Software-questions/Jira-Automation-gt-Error-403-every-time/qaq-p/1583535 Please let me know if this goes in the same direction and might solve your problem. Best Stefan

Hallo @Harald , bewegst du dich in einem Team-Managed Projekt oder einem Company-Managed Projekt? LG Stefan

Hi @ian , as far as I get the documentation right the smart values within the if/equal are without {{}}. Please try the following approach and let me know if this works: {{#if(equals(webResponse.body.id, 10060))}} "hello"{{/}} Best Stefan

I also got the conditional smart value working. Please try following and let me know if it works for you too: {{#if(dueInDays.asNumber.gt(0))}} Hello {{/}} Best Stefan

Hi @Andreas Eichert Could you describe your use case from a functional perspective? As this could maybe be resolved with a condition component in automation rather than within smart value condition. So condition could be checked up front and only in case of fullfillment mail is sent. Please let me know what exactly should…

Hi @Martha Sanchez the settings in your screenshot are the project related xray settings. API tokens are set in the xray app administration (as far as I know this needs admin permission). if you click the jira settings/admin button (in cloud this is in the upper right corner) and then choose „apps“ there should be a…

As far as I know the issue hierarchy is not extended through advanced roadmap which means the created „structure“ is not detected as parent known from standard issues. To be honest I‘m not that proficient with advanced roadmaps but I think I remember a question here in the community where this was discussed. Best Stefan

Hi @Daniel Hamann , As I interprete your description it seems you are working with advanced roadmap. Is that right? Best Stefan

Hi @Jayaprakash , wanted to reach out to you if there is any further feedback on this? In case your question is answered please consider to click the "Accept" button so that this question appears solved for other users dealing with similar question. Best Stefan

Hi @David Backup Any updates on this case? Best Stefan

AWESOME!!! glad this was helpful and could give some valuable input. That was the intention 🎉😊 In case there are any further questions: Just let the community know and we will try to get things working. Best Stefan

Hi @Martha Sanchez and welcome to the community, as you mentioned that it works with jira API: did you create the specific xray token in jira administration? Jira and Xray APIs are using different tokens and also different types of authentication. Unfortunately I‘m not familiar with axios. I‘m working with curl calls.…

Hi @Matthew Risch , guess this could be solved with Automation for Jira. Try to use devops trigger „deployment successfull“ then generate current date with smart value {{now}} If the smart value needs to be converted to special dateformat the following link might be helpful:…

Hi @Wade H and welcome to the community, The feature „create branch“ only works with bitbucket. This needs to be done within gitlab/github. As soon as the branch is created with the prefix of the issue (eg Story) it is shown in the development section of your issue (whether in github or gitlab as soon as the repo is…