Stefan Salzl Community Champion

Very much appreciate this mindset. Thanks so much. That´s the community mindset 💪🙌 ooooh.....another austrian enthisiast. very cool. I am based in Vienna and we just started to host community event yesterday. If you´d like to I would be happy to connect on linkedin (link is in my profile) for some atlassian and…

AWESOME job 💪 Good to know you got that working and thanks for sharing your solution with the community. This can be very helpful for other users with similar problems. (side note: as an austrian community leader it´s always a pleasure to read some German terminology ;) ) Best Stefan

Hi @Jonathan , I´m not sure if I can follow your requirements 100% but the following community post seems similar to your question: https://community.atlassian.com/t5/Jira-Service-Management/smart-value-for-cascading-select-field/qaq-p/1482635 Please let me know if this was helpful. Otherwise could you please describe your…

to the answer of of @Patrik Korovsky i‘d like to add: The reviewer of a PR could be another person than the assignee. The reviewer is something living within the repository and is not connected to any increment in Jira (not even a user —> could be at least it doesn‘t have to). Furthermore there is no smart value to…

AWESOME!!! sooo good to know you got that working. It´s my pleasure ;)

Hi @Marcin Łukaszewski yes the automation actions need the fields on the create screen. Did you consider to try an API call? Not quite sure if this needs the create screen scheme too but would give it a shot (calling a web request action in your automation rule). Furthermore if you have scriptrunner in place this could…

Hi @Adam Hasselgren could you try to just use lookupIssues.PdM or lookupIssues.PdM.value in your edit action? The displayName is mainly meant for user picker fields. As far as I got your description you are getting the information/value from a select field (single choice). So in this case the result is already the expected…

It looks like your issues are located in different projets. is this correct? In this case the rule must be configured as a multi-project or global rule. You can add another project to the scope in your rule details. All projects that are in the scope of your automation rule (so to say that are part of the processing) needs…

Hi @Adam Hasselgren , yeah as I mentioned before try to use the smart value directly in your lookupIssues. so instead of your variable name (as shown in your last screenshot) use {{issue.Customer.value}}. The JQL cant be validated as it uses a smart value which is resolved during runtime. This depends on the issue the rule…

It seems your JQL doesn‘t even deliver any results. I would suggest the following: * before your lookupIssue action add a „audit log“ action for debugging and let it just wright the value for customer field in your issue —> {{issue.Customer.value}} * it should not be necessary to store this value in a variable —> try to…

YEEEEAAAAH!!!! Great job dear Atlassians!! Keep it up!! 🙌🏼💪🏼🎉

Hi @Villarasan The JQL branch moves issue scope to the issue(s) that are the result of your jql. Hence: everything within the branch will be processed on these issues. It looks like you are running on Server/DC. Unfortunately the lookupIssue action is not available there (as far as I know). In cloud I would use this action…

Hi @Villarasan , could you please share a screenshot of your rule or how far you got so far? Furthermore: you could also choose the description field from the dropdown in your edit issue action and use a smart value to copy the description of your template issue. Best Stefan

Hi @Adam Hasselgren , First thing: smart values are case sensitive. So try to change to {{lookupIssues...}} (capital „i“) in your esit action. furthermore (as the field is still a list) could you try the following in your edit action: {{lookupIssues.PdM.value}} see the documentation below:…

Ok. Thanks for your input. The edit issue fields action looks different now to your initial post as it now only shows "advanced" option (formerly: Story Points). Let´s do a live example for investigation. If possible please try to reproduce as follows: * create a story in your project * within the story create Subtask 1…

AWESOME!!! Happy to know you got that working 💪🏼

Hi @Adam Hasselgren , How far did you come so far? Could you show your current automation rule? That would help the community to better understand the problem. Best Stefan

Further question: Which issue type is the issue "PORTAL-485" that should be edited in your audit log screenshot? From your former screenshot of issue types settings I can see that there is a field "Story point estimate" in issue type "Story". Best Stefan

@Michael WANG Could you please share a screenshot of your edit issue field action? Best Stefan

Hi @Michael WANG Thanks for the information and the screenshot. As the screenshot looks like it´s a team-managed project. I already assumed this. Please find the description and solution in my last answer above ;)

Guess I´ve got the problem already: There is a different field for the estimation in team-managed and company-managed projects. Within team-managed projects this field is called "Story point estimation". Unfortunately (as you already pointed out correctly) this cannot be chosen in the dropdown field so the advanced edit…

Is your project team-managed or company-managed? Could you please also share a screenshot of the configuration of your "edit issue fields" action? Best Stefan

Hi @Michael WANG for better understanding and further investigation: could you please explain what you are trying to solve with your automation rule from a use case perspective? What is your setting? when should the rule be triggered? which issues do you have in place? which story points from where would you like to sum…

Hi @Erik George you can use if condition within smart value so you could check if a comment is internal or not and only include the information if it´s not. see following link: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ tested in my environment with following line:…

hi @csuc , got it. I think the dependency between versions still exists. Which versions (both: Jira + Plugin) did you/would you like to install?

Hi @csuc This could be due to some changes that automation for jira is now native functionality in Jira DC (like it is in Jira Cloud). Maybe the following link could help: https://confluence.atlassian.com/automation/understand-versions-licenses-upgrades-1141480571.html Best Stefan

May I ask why the standard notification is turned off? It gives exatly the information you would like to have (status and comment via email, excluding internal comments). imho I would rethink the idea of turning off native functionality and try to implement exactly the same thing with automation. furthermore: what does…

Hi @Erik George , I‘m sorry but can‘t follow your description. Isn‘t that the main functionality of jira seevice management that the reporter is notified via email about a new comment and furthermore the main functionality of internal comments that they are not sent to the customer and only shared between agents? There…

Hi @Raju Mandapaka , as @Nic Brough -Adaptavist- already mentioned: the general automation rule actions are only capable dealing issue related data. AND... one thing that came to my mind would be calling a web-request in your automation rule. I‘m not an API specialist but the following approach might be worth giving it a…

Hi @Evan Smith OK. got it. Thanks for the further information. The branch refers to "all issues that have been created before" in this rule. In your case this is the newly created task. So it takes all issues created before in this rule into scope and executes whatever is set within the rule on all those issues. eg. if you…