Vishal Biyani Expert

@Tanya Chaturvedi What is the JQL that you have written? Is this a native JQL or you are using some 3rd add-ons like script runner?

I have not worked on JIRA data center. I am using cloud instance. Having said that, given that issue id is a key value, it should be unique across the projects in the same instance.

in that case can you try setting customfield_10038 like this and see if works for you. "customfield_10038 ": { "version": 1, "type": "doc", "content": [{ "type": "paragraph", "content": [{ "type": "text", "text": "hello" } ] } ] }

@Ankit kharola What is the type of field that you are using for customfield_10038? ADF (Atlassian Document Format) is expected for fields like description. if you are okay to have a simpler use case, I would suggest that you change the type of the field. Else you will need to follow ADF guidelines while updating the field…

@Mariam Mohamed You can create a smart Variable say varEmailAddress and populate it like this {{if(exists(triggerIssue.assignee.emailAddress), triggerIssue.assignee.emailAddress, triggerIssue.reporter.emailAddress)}} Then in email component use {{varEmailAddress}} See the rule below

@Nguyễn Quang Currently it is not feasible to get component lead based on Component added in the issue within an automation rule. However, you can send a web request (REST API call) to get the component lead name based on the component id. There is a feature request that you can vote for. [AUTO-485] Automation support for…

@Dan Spearing if you have JIRA premium or JIRA enterprise, then go to Seetings->IssueType Hierarchy. Click on Create Levels. You can create a Feature and update your hierachy to be Epic -> Feature -> StandardIssueTypes -> subTaskIssueTypes() See if this works for you.

@Ana Folks In the JQL search columns, are you able to see Epic Name? if not see if the custom field is available in your instance and needs to be mapped to a screen. We were using Epic Name. so I can see it in my cloud instance.

@Samuel Imrich Can you try using same project instead of same project as trigger? Also, not sure if creating a Epic first makes a difference. In my cloud instance the rule is executing file and creating the issues

@Samuel Imrich Can you share the screen shot of the automation that you have created so far?

@Chris Smith if what needs to come in Agenda is well defined can be evaluated based on key value pair, in that case you can check lookup tables and it should simplify the automation rules.

not sure why a space will get added. How can you try using trim() to see if removes the leading and trailing spaces. if this does not do the problem, check if there is an extra space added somewhere by mistake?

No. it doesn't. Otherwise, there is no purpose of Advanced fields. You need to select the field as far as i know. Otherwise, automation will give the error that you are seeing. Try it out with one test issue that you may have and see how it goes.

this is the automation that I wrote. In the edit action, assumint you selected fixVersion field, i see the use of json in Additional fields may not be correct. Can you try with what i have in screenshot i.e. additional fields text box should look like { "fields": { "fixVersions": […

can you share the screenshot of the automation that you have? and where it is breaking so, if you have fixVersions like "ABC 2024", "123 2024", "2025 ABC" in the epic then ideally both "ABC 2024" and "2025 ABC" should get copied to child.

varFilteredFixVersions.substringBeforeLast(",") would have something like that. So all the fixVersions in Epic and doesn't contain ABC, will be/should be added in child stories/task if you need to reverse i.e. only copy where ABC is present then change eq to gt and that should work {{#if(name.indexOf("ABC").gt(-1))}}

@Amruta Harale What is the date format you are passing in your csv? Can you share the screenshot of your csv fields mapping to jira fields before the import?

Check this link out Jira Cloud for Excel (official) | Atlassian Marketplace This is a free plug-in by Atlassian. It simplifies getting data from JIRA in excel.

@Ed Sevilleja I don't believe there is a workaround for this. this is how distributed systems work

@jerry.raterman JIRA is flexible and organizations create issuetypes, issue hierarchies based on your business need. You could very well create Action issuetype, create a JQL based on that issuetype and then probably create a kanban board for your team to visualize and prioritize the work. Are there any specific concerns…

@Murali K R Are you on JIRA Cloud? Are you able to uses a plugin like "Get JIRA data" to download the data from JIRA into excel based on the JQL given?

@Patrick Cartier Here is my proposed solution. see if this works for you. As a trigger I have used Manul trigger. You can use as per your use case 1) Create smart variable say varFilteredFixVersions. This creates a json object for matching fixVersions that need to be copied to child issue from epic. {{#issue.fixVersions}}…

in that case take out the JQL from Scheduler. After Scheduler add an action lookup with the JQL that is currently inside scheduler. Then in the email iterate over lookupIssues. This should resolve the problem in my opinion. This is how the automation will look like The email body should have something like this:…

@Annie Kearns How does your board look like? is Dev Complete in the right most column? if not, add it in right most column and you will achieve what you need

Can you describe your problem in some more detail? As per the SS, automation will trigger at scheduled time and send one email. it doesn't look like this will send multiple emails.

@Aleena Umaiir Can you share the screenshot of your automation to better understand where the issue could be?

@Christof Hurst Can you try using below syntax to get linked issue key and its status name {{#issue.issuelinks}} {{outwardIssue.key}} {{outwardIssue.status.name}} {{/}}

@Sebastian Krzewiński Can you share the screen shot of the automation esp. where you are setting attachmentName?

@Stefano Astuti The question is not clear. What web link needs to be added and where (in a custom field)?

@Arpita Solanki The way it needs to be done will be a combination of lookups and advanced branching * As Trigger, use scheduled as per your business need * Add lookup issues action and JQL: target date is empty etc * Then Add Advanced Branching and use {{lookupIssues.assignee.distinct}} in smatValue and give it a name…