Vishal Biyani Expert

@Mohamed Eid Formula looks correct. Could you add {{#debug}} {{/}} when you are creating the variables? Let's see with that additional check to isolate where the problems could be

@Loic To add a link in the email you can add this line. Invoice will show the hyperlink when you hover over it. [Invoice|https://drive.google.com/{{triggerIssue.custom field name}}] i am not sure if you can attach the file added to an issue in an email via automation

@Hannes Obweger - JXL for Jira You are right. JQL does not support regex like this. I should have tried it. But got mislead by the article that I have added as a reference in my reply. Thanks for highlighting this.

@Berat Altunhan have you looked at scheduled trigger? in the occurence section you can define days when it should trigger

@Mohamed Eid can you add debug message for each step where you are creating the smart variable? share the audit log message in one screen shot

@Bhavikaa this will be tricky to implement. Can you refer to this article and see if this helps you get started?

have you tried ~ operator in jql? summary ~ 'TASKS101\d{4}' For issues under an epic, can you try parent = <epic number> and summary ~ 'TASKS101\d{4}' This will return all standard Issues that are linked to an epic and contains summary TASKS101XXXX You can refer to this article…

@Bhavikaa How do you define the sequence of sub-tasks? is that stored in some custom field?

@Mohamed Eid Share the screen shot of your automation and of the audit log by expanding each action. 

@Loic There is a delete attachment action that you can use

@ANA Siurana PEREZ There are few reasons, why you may not see the next status * It is possible that your userid may not have permission to transition the issue to next status * Some conditions are not meeting due to which transition remains hidden. Ask your jira admin what restrictions they have placed on the transition…

Yes. this is my audit log Can you share the screen shot of your rule to check if you have fixed the rule?

thank you for the update. Looking forward to AI leaders sharing their insight.

@Nick Binos Your ask is not clear. Can you elaborate where are action items stored? is it a custom field available against each issue?

@Yi Liang if you have access to JIRA Automation, then you can use it to get details in an email. Example rule 1. Trigger You could define a trigger based on your need. I have used Manual Trigger for demo purpose. 2. In the Lookup issues, add the JQL as per your requirement. Let me know if this is something that works for…

@Archana have you explored the option of using JIRA REST APIs to extract the worklogs and then do the reporting on the data? Check the link for details on how to use a rest API for this purpose.

@권구희 404 means resource not found. Looks like this is a configuration issue. You may need JIRA Admin permissions to check the configuration and fix the issue.

@Dhivya Raghuraman I doubt there is a JQL that exists which allows you to retrieve user list. What you can do is in automation, use "Send web request" and specify url like this https://your-domain.atlassian.net//rest/api/3/users?startAt=0&maxResults=1000 if there are more than 1000 users, then you will have to send…

@Maurice B. There was slight error in the above. use this and you will get the required issue keys. {{#lookupIssues}} {{ if (due date.isAfter(parent.due Date), key) }} {{/}} If this helps you, please accept the answer so that others can also benefit

adding this condition {{#lookupIssues}} {{ if( due date.isAfter(parent.due Date) ) }} {{key}} {{parent.key}} {{/}} gives True if issues due date is after parent due Date otherwise it does not print anything. This logic you can build in email template to send issues that match the condition

@Olie Ryan-George Try below and see which you like between noformat and code {noformat} sudo npm install vsoagent-installer -g {noformat} Example Text {code:title=example.py|borderStyle=solid} issue = jira.issue("TEST-123") comments = issue.fields.comment.comments for comment in comments: print(f"Author:…

@Maurice B. I wrote this sample rule. See if this gets you going. Assumption is if any of the child issue has a due date > than parent, then it needs to be flagged. Therefore, I used max to simplify the logic.

@Digvijay Singh Gehlot Below is a pseudo code that you could use Use below jql and narrow it down as much possible say by adding condition like statusCategory != Done then use below rest end point url = "<a href="https://your-domain.atlassian.net/rest/api/3/search/jql" target="_blank" rel="nofollow noopener…

As suggested on the other post, .toDate is missing try with this corrected statement: {{#debug}} {{ startdate.toDate("yyyy-MM-dd").plusDays(remainingdays.asNumber)}} {{/}}

.toDate is missing try with this corrected statement: {{#debug}} {{ startdate.toDate("yyyy-MM-dd").plusDays(remainingdays.asNumber)}} {{/}}

@Madhur Ramachandruni To trigger rule2 and ensure that it proceeds only if issues created from Rule 1 are in Done status, what is the condition that can be used to safely identify issue is created from Rule 1? * Is there a specific issue type that is created by Rule 1? * Is there any custom field that can be leveraged to…

@Kaladin Stormblessed Labels don't take spaces. With that caveat one possible way is below 1. Have below Trigger 2. While using Edit Issue field, add below is the advanced section { "fields": { "labels": [ "{{fieldChange.fromString.replace(" ", "") }}" ] } } Let me know if this works for you

@Mohamed Eid You can create two smart variables and stored the values that you have parsed. Let's say 1. CertificateIssueDate = {{issue.description.substringAfter("This started at ").substringBefore(" ")}} 2. CertificateExpiringInDays = {{issue.description.substringAfter("is expiring in ").substringBefore(" days")}} Now…

@Lee Cash in Scheduled trigger, You can specify start Date and End date, and occurrence. Does that not work for you?

@Mohamed Eid Look at this link that gives you details about how to add date and number Examples of using smart values with dates | Cloud automation Cloud | Atlassian Support Try this out and see if it works for you