Bill Sheboy Expert

Hi @LJ Yes, and...to the other answers posted: You do not show the details of your scheduled trigger, so I am assuming it does not have JQL as you are also using Lookup Issues. But, your Send Email action references {{issue}} fields, which do not exist. When you use Lookup Issues, you instead reference the {{lookupIssues}}…

Hi @Ludvig Hede I do not believe there is a way to filter that project REST API call. One possible work-around is to: * iterate over the projects, * call Lookup Issues with JQL ordered by updated DESC, and * check the latest one (or if there are no issues) to decide if the project may be archived. Kind regards, Bill

Hi @Hassan Rachid I recall from other community posts there are several different things in Jira Cloud called "Team". Which one do you mean: advanced roadmaps, project scope, something else? Knowing that may help the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Christian Delgado Without a marketplace addon to do this, I agree you will need to use pagination to get all the users with the REST API. To watch for just the changes, you could set up a webhook to push the audit log events related to users, and then parse that in another tool. It will not have the group change…

Hi @daniel.kirchhof -- Welcome to the Atlassian Community! What problem are you trying to solve by implementing an issue search outside of Jira Cloud? If you describe that problem it may provide context for the community to offer suggestions. Thanks! Next, JQL is not a SQL, and so has a narrower set of capabilities focused…

Perhaps I misunderstood your question... I thought you had a Jira issue with a field that contained markup, and that you were then using an Automation for Jira rule to send an email. Is this what you are doing?

Let's check some things to see where the problem may be... First thing, with this technique, you would have a single issue edit using JSON and no branch in the rule. Is that what you have currently? If not, please post image of your latest rule. Next, please try writing just the created variable {{LabelTest}} to the audit…

Hi @Yogesh Ranjitkar You note that the "payload is similar to..." but does it exactly match what you are expecting? One way to check this is to write the entire response to the audit log after the webrequest to learn what is happening. And...have you selected the option to wait for the webrequest return before continuing…

Hi @Sari Kachorovsky -- Welcome to the Atlassian Community! I do not believe all of the supported fields are listed in those dropdowns. Instead you may need to use and advanced compare condition using the field smart value. To learn the smart value (or if your field is supported by automation rules) please use the…

Hi @Eddie -- Welcome to the Atlassian Community! For a question like this, I recommend posting images of your complete automation rule and the audit log details showing the rule execution. Those may provide context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Tory Dennis I believe you can remove the field editor markup from the fields using the text format, such as with: {{issue.description.text}} However, if you have actual HTML in the field that is not going to be removed using this method. Kind regards, Bill

Hi @Melanie Plourde -- Welcome to the Atlassian Community! What part are you looking for help with: * creating automation to add the checklist item * the smart value for the date adjustment from Due Date * something else? If you already have a rule and it is not working as you expect, please post images of the complete…

Thanks for clarifying, as your post indicated you were using Cloud but you are actually using Server/Data Center. The Server/Data Center version has an option for bulk-issue processing. This is a setting you select either with the Scheduled Trigger with JQL or with a Branch. After enabling the setting, you would use the…

Hi @Cedric Jimenez I do not know if all of the data for the subtasks is stored with the parent, or just a subset. And so you could try a couple of things: 1) Iterate over the subtasks, wrapped in a math expression, to add them: {{#=}}0{{#issue.subtasks}}{{#if(your condition here)}}+ {{Story points}}{{/}}{{/}}{{/}} 2) Use…

It is a rule action to reload the data for a trigger issue: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Re-fetch-issue-data

Hi @Dhiren Notani_Exalate_ When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @Adam Dulberg First thing, I am using Jira Cloud, and not the Server/Data Center version. With that disclaimer out of the way... Have you tried just doing this with the concat() function to see what happens? Perhaps like this: {{issue.customfield_xxx.value.concat("_").concat(issue.customfield_xxxx.child.value)}} Kind…

That is interesting and useful information; thanks!

Does this always work for you and fail to make the edit for the other user? Well, it does not appear to be permissions-related as something in the rule would fail otherwise. I wonder if this was a timing issue; the issue created trigger can fire faster than the data is available, and so perhaps there is some collision…

Hi @Chad Vernon You can use the conditional handling to test for the empty value, and only include/use the JSON when needed. This could also be done with a rule condition. Kind regards, Bill

Hi @Kunal Kumar To use the {{lookupIssues}} smart value, you need to first call the Lookup Issues action. Please try this change to your rule: * trigger: scheduled with no JQL * action: lookup issues with the JQL you previously had in the trigger * action: send your email Kind regards, Bill

I will post a response with your new question: https://community.atlassian.com/t5/Automation-questions/lookupIssues-not-returning-any-values/qaq-p/2319022

Would you please post images of the current rule and audit log details showing that execution? Thanks!

That seems to indicate a problem with the related issues condition, or its JQL. Have you tried to use the JQL with an example epic to get it to work how you want, and then try that in the rule for the condition?

Thanks, Tory. Is there a JQL statement you can write that can return what you need? If not, you could investigate either creating an automation rule, or using a webhook on specific changes, and build another application which adds to your information store.

I am glad to learn that is working! Smart values are name, spacing, and case-sensitive, so perhaps there was something the rule didn't like. When something looks like it should work, but it does not, here are a few things to try: * Use this how-to article to confirm the smart values are…

It appears the first condition is failing, and so I wonder if you have the correct smart values for your fields. Smart values are name, spacing, and case-sensitive. Please try using the how-to article below to confirm the smart values in your rule. Basically you identify an example issue with your fields, call the REST API…

Hi @Jurgen Desmedt Please consider checking with your site admin to add/access this. For my employer's Standard Jira license, we had to add this early in the beta period. However when I just checked a free instance I use for testing, I found JPD was already there, even though I did not add it. I am guessing this may be the…

Hi @Irith Trietsch Bloom I wonder if whatever tool you were using before, supported some form of "macros", where you pre-defined the values you describe for new tasks/items, or even rules to do so. If you can pre-define such things, there may be features of Jira to help. For example: * You could create automation rules,…

Hi @Daniel Lizik Without seeing your entire rule for context, I wonder if the @ symbol is leading to an attempted match on a Jira user, as in a mention. When I try just the text "<@slack-id>" in such a condition, it works with no match attempt, and does not show that error. You could try removing the @ and storing the…