Bill Sheboy Expert

Hi @Pfohl Jason What is the hierarchy of your issue types? The out-of-the-box hierarchy is: * Epic* Story, Task, or Bug types* Sub-task types So the built-in Bug type can be linked to an Epic using either the "Epic link" or "parent" fields in an automation rule. If you have a different hierarchy, or issue linkage path,…

Hi, @Jack Brickey -- Variables created inside a branch which could-contain-more-than-one-issue are not available outside of the branch. This is due to the parallel processing of the branched-to items. The variables go out of scope and vanish after the branch...and there is no guarantee when the branch will finish, up to…

Hi @Vineela AK What do you mean by a "report"? You can use JQL to list issues including the fields you noted. And the results could be reviewed on the page, exported to a spreadsheet, shown in a dashboard, etc. To get you started using JQL, please review this documentation and free training: *…

Hi @Adilet Seit What problem are you trying to solve? Knowing that may help the community to offer better suggestions. And, what do you mean by "task goes to the desired page in Confluence"? Kind regards, Bill

Just to confirm, is the rule working now? A work-around for that challenge with capitalization is to force the text to lower (or upper) case before the comparison/filter. Although that is not always what is desired for matches.

Hi @Andrew As a reminder...When recommending a marketplace vendor product, please ensure 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…

Would you please post images of: * your current, complete rule * the details of the create variable action(s) * the details of your use of that variable in the mention And...did you confirm the exact names of your sub-task types? If the names are not correct the created variable results will be empty. You can confirm that…

Yes, that is possible using the format() function for date fields. Please look here to learn more about that: https://confluence.atlassian.com/automation/jira-smart-values-date-and-time-993924864.html

There are several community posts on this scenario, including this one: https://community.atlassian.com/t5/Automation-questions/mentions-in-automation-smart-values-shows-accountid-instead-of/qaq-p/2188200 For more details / actions: * call the REST API function to get the user (or all users), pausing until the results…

Oops, my mistake! The created variable expression was incorrect as I left off the assignee field! I fixed the earlier post and here it is also: {{#issue.subtasks}}{{#if(equals(issuetype.name,"Sub-Task"))}}{{assignee.accountId}}{{^last}},{{/}}{{/}}{{/}}

Hi @Shubham Gupta As a reminder...When recommending a marketplace vendor product, please ensure 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…

This makes me wonder... There are date fields in Jira which are not date or date/time type; instead they are text! Let's try to force the date type first: { "fields": { "customfield_14684": "{{lookupIssues.customfield_14684.toDate.max.jiraDate}}" } }

A suggestion on regular expressions and automation rules: try the simplest thing which could work and test it. The documentation for match() indicates the regular expression implementation is based upon the one for Java's Pattern class, but nowhere is it fully documented what does and does not work in rules. Several…

Yes, the created variable needs to be inside the condition (and branch) to do this for each issue type case. Sorry, I left off some details on doing the mentions... This produces a list of accountId values: {{varAssigneesForSubTasks.split(",").distinct}} And that must still be parsed into mentions, like this:…

First, the "Parent link" field has been deprecated, so please consider no longer using that. Please look here to learn more: https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/#Updates-to-automation Next, when the Issue Deleted trigger fires, the issue is captured for use…

Awesome! I am glad to learn it is working.

Awesome; I am glad to learn it is working!

Hi @Vikas Sharma -- Welcome to the Atlassian Community! Yes, that is possible. I recommend looking at the example rules (or posts in the community) to doing this for story points, and then change the rule to meet your needs for summing estimates. Here is an example…

Hi @Casper I believe you would need to do this in two steps, for each issue type involved: filter by type and then use distinct: * inside one of your conditions on type for the trigger issue, create a variable which filters by type and only save the assignees' accountId* name: varAssigneesForSubTasks * smart value:*…

Hi @koutarou ishibashi When you want a rule to trigger after an issue is deleted, try using the Issue Deleted trigger. If that is not what you asked, please try this: * Post an image of your complete automation rule * Post an image of the audit log details showing the execution of your rule * Explain what in the rule is…

Regarding that expression collapsing to always true, I believe that is because after the remove() happens, you are left with an empty string, rather than null...and that would always exist. And so another method must be used... Instead we can use not(equals(yourTestString,"")) for the comparison to an empty string rather…

In that case, perhaps leave it as-is and test using it for entry, and the automation rule to calculate your measure. If people have difficulty understanding the field options consider how to improve it.

No problem; glad to try to help. And as you note, the info you shared will help others who try to investigate these fields/scenarios.

Is that on the form "template" approach that JPD uses from the Create button? If so, I have not used that yet so I'm unclear if/how those headings are used.

Hi @Kristian Cassimire -- Welcome to the Atlassian Community! Do you mean a single field, Red/Amber/Green (RAG) indicator which somehow evaluates and displays the status for a project at a glance? If so, I believe the answer is, "no, there is nothing built-in which can do this." There are most likely marketplace addons…

Hi @Blake Falanga Would you please clarify a couple of things to help focus any community suggestions? What do you mean by the "Delivery button"? There is what appears to be a button labeled "Delivery" when viewing an idea in the right-side of the page, and that is a mechanism to link other, existing issues to the idea. It…

Hi @Tomislav Tobijas First thing, I am using Jira Cloud and not Server or Data Center. And so please confirm my ideas by checking if you have these smart values available using this how-to: https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html Next thing: for the hierarchy you…

No worries, as we are all learning. And, great progress! For your earlier question, the {{#=}} {{x}}+{{y}} {{/}} syntax is one of the ways to perform math expressions. The other way, for simpler operations would be this: {{x.plus(y}}} Please look here to learn more about the math…

As those represent the field names, aren't they shown already on the page and then allowing the person to select a value from a drop-down? If so, I recommend removing them. When JPD eventually improves custom formulas you may be able to turn off the rule and having the extra entry as a "title" might break the way weights…

Thanks for that information, as when I check business projects they appear as Team-managed (TMP). That work-around I suggested helps whenever a rule cannot resolve the fields, or they are not listed in the drop-down fields. The TMP defect/symptom is just one example. So it might help or not. At this point, I suggest…