Bill Sheboy Expert

Huh...I just tried this in both a Team-managed project (TMP) and a JPD project (which is based on TMP) and both worked for that lookup. Please add this to the audit log after those first writes: the lookup table: {{tblBusinessValue.entries}} That should list the table, keys and values, so we can identify any differences.

Your lookup table has dollar signs in front of the numbers, and it appears you field configuration does not. We can see this from the values that were written to the log. Please change them to be the same for this field and try again. If that works, we may have identified the issue for the different fields in the…

Progress! That indicates the lookup from the table is not working: either the key is incorrect or the value is somehow converting to a number (i.e., removing the comma before the lookup attempt). Would you please show an image of the action which creates the table for Business Value?

Hi @Peter M -- Welcome to the Atlassian Community! Have you tried the CONTAINS ~ operator with wildcards: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CONTAINS---- Perhaps like this: fixVersion ~ "Release - 1.1.*" Kind regards, Bill

Hi @Peter Sauer -- Welcome to the Atlassian Community! Based on this open suggestion, I do not believe it is possible to update a board's configuration using the REST API: https://jira.atlassian.com/browse/JSWCLOUD-20535 If these personal views are treated as read-only, have you instead considered creating a shared…

Hi @Collin Roberts -- Welcome to the Atlassian Community! As David described, you will need the accountId value for each of those users. As you note they are not associated to the issue in any way, such as an issue field, you will need to hard-code the values. Kind regards, Bill

Thank you for clarifying the alternative you are suggesting as it seemed you were recommending the product and then stating it could not be used.

Hi @Alex Waugh Is the only thing different the recipient email addresses with the email body the same for all? If so, you can make a simple and easy to maintain rule using the new Lookup Table action automation rules. Perhaps like this: * trigger: issue created * action: re-fetch issue (I always add this after the issue…

Hi @bkillpack -- Welcome to the Atlassian Community! You note using Jira Server, and that does not have the Lookup Issues action. Instead you would use the bulk-processing option for the branch, and reference the {{issues}} smart value. Please note that is plural as it refers to the issues as a batch. In the linked…

Wow; that says all the values collapsed to empty! After all of your table creates, let's write this to the audit log: The field= "{{issue.customfield_10298}}" and the field value= "{{issue.customfield_10298.value}}" and the table lookup= "{{tblBusinessValue.get(issue.customfield_10298.value)}}" If those first two are…

Hi @Chloe Allison -- Welcome to the Atlassian Community! You may also want to post your question in the developer community: https://community.developer.atlassian.com/ I looked around in the other version endpoints documentation and did not see them in there…

Tom, what do you mean by "child ticket" in this context where you are using links? Do you meant that every single issue would have the custom field and show how many of the linked issues are "open" for that 7 days window of time? If so, I suspect that would be a risky rule to run given the upcoming changes in rule…

That looks better. Would you please show the error message as I cannot see it in the screen image? And have you confirmed that each of the fields you are using has a value selected?

Hi @Sara Silva -- Welcome to the Atlassian Community! For a question like this, please post images of your complete rule, including the details of the action/condition not working as expected, and of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks! Kind…

Hi @Manmohan Anand This is a known defect, and here is an example issue for it that you can watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-23833 Suggested work-arounds are to remove some card fields, disable some features, change the browsers zoom, etc. Kind regards, Bill

Some of your get() function calls are missing the closing parenthesis. Specifically the ones for Risk Mitigation, Opportunity Enablement, and Business Readiness. If you look at the first one for Business Value that is a good example.

Hi @Kara Nadarajah What if after the trigger, you write to the audit log the value of {{pullRequest.state}} to confirm the value? That may help you identify what needs to be tested in the condition. I wonder if that is an enumeration, and there is a lower attribute that could be checked. Kind regards, Bill

Awesome! And regarding this in your post... I also am trying to figure out why using the Create Variable action didn't carry through in my email script plus one or two other mysteries I can't resolve for now because I am tired of this problem and need a break from it. My hypothesis is you are trying to use a created…

Please confirm your table names match the calculations, as the two versions you are showing appear to be different. For example, {{tblBalancedScorecard}} versus {{tblBalancedScorecardValue}}

Sorry, I am unable to do that currently, but I think you are quite close... Once you have the tables set up, you can use your fields to get() the values to use in the calculations. This is the example I gave for the Business Value: {{tblBusinessValue.get(issue.customfield_10298.value)}} And so please do the same thing for…

Hi @Deepika Dandala -- Welcome to the Atlassian Community! I respectfully suggest you experiment to learn how the Atlassian interpretation of a control chart works when you make adjustments to the non-working days, particularly anything more complex than what a "weekend" is for the team. My reasons include this report…

Hi @Jason I thought we already covered that topic in this question: branches on more than one thing are executed in parallel and asynchronously. And so we have no control over the order of processing. In fact, there is no guarantee of when the branch will complete...up to the very last step of rule execution. I suspect…

Hi @Tom Goode Where would someone look to see this count you describe? As I expect you can write JQL to count those for a specific epic, you have several options: * add the custom field, and set it with an automation rule and the Lookup Issues action (with the JQL above), making it visible with the issue (Epic) * create a…

My mistake: I left off the conversion back to numbers after use of format() as that function leads to a text value. Please try this: {{triggerIssue.customfield_13403.format("ww").asNumber.minus(triggerIssue.customfield_13403.format("ww").asNumber.divide(2).floor).format("00")}}

Hi @Yuri Lapin _Release Management_ As the original poster is using Jira Server (or Data Center), and the product you are recommending from your employer is only available for Jira Cloud, would you please clarify what you are suggesting? Thank you. Kind regards, Bill

Thanks for those images! The most likely cause of this symptom is you have an incorrect smart value for your Reopen Count field. And so the value in the edit is null + 1 which always yields 1. Smart values are name, spacing, and case-sensitive; when an invalid one is used, it only returns null rather than showing an…

Hey @Simmo -- It appears there are several defects/suggestions for this symptom and most are either marked as duplicate or won't do: https://jira.atlassian.com/issues/?jql=project%20IN%20(%20%22Automation%20for%20Cloud%22)%20%20and%20(summary%20~%20%22iterator%22%20or%20summary%20~%20%22iteration%22)%20ORDER%20BY%20Key

First, let's simplify/shorten your rule to see how that helps... The action to Create Subtask can add multiple subtasks at a time, so try collapsing your 5 subtask actions into 1. Next, where you branch to All Created Issues, please change that to Most Recently Created Issue, as there will only be one. Then retest to see…

Thanks, @Åse Nordberg That seems to suggest that the underlying implementation of that branch type changed after those changes for epic fields went live. Good to know!

David, sorry if I was unclear as the work-around I was describing (for searching) is not a good fit for your scenario. What you seem to be trying is: For the entries in a list (addFieldChange), replace an attribute (name), with a value looked up from a table (orgmap). The replacement is the challenge, and so I think you…