Bill Sheboy Expert

Hi @Troy Sorry this thread is splitting/scattering. This is one of the reasons why it is better to create your own question and link back to other, related ones: less chance of other questions getting asked in the middle of the discussion :^) Okay, it appears to me that {{changelog}} is one of those smart values which…

No worries; writing automation rules is a lot about learning and experimentation, and we are all doing both of those things :^) For your scenario, I would recommend using one edit to add the labels, rather than use branching, as I described earlier in this thread. The difference is that rather than starting with a…

Without seeing your complete rule, I suspect another problem is there is no split of the variable before it is used in the advanced branch.

Hi, Phil. Sorry if I misunderstood your scenario...I got the impression you were trying to create default field values and then have them just-in-time filled in dynamically at issue create. That is why I suggested the tokenization technique. You are correct that you could just have the rule do this at issue-create. I seem…

Please try using the JQL branch, not the advanced branch with smart values. What you are trying would only work if you referenced the {{key}} variable in the branch logic. And also, it is generally a good idea not to use variable names which could match any smart value names, like {{key}}, as those may cause confusion and…

Hi @Peter D The answer is "yes": admins will need a JPD license to do creator functions, as Atlassian answered in the other thread on the licensing changes: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/A-big-update-on-Jira-Product-Discovery-pricing-creators-and/bc-p/2308389#M1122

Yes, and...I hypothesize this new feature is going to waste some Jira admins time to undo unplanned changes, explain things, etc.

Hi @Phil Bustin That is an interesting idea, and I also expect the answer is "no"...and... A work-around could be to use some token/keyword other than smart values, and on issue create (edit, etc.), trigger a rule to parse the field and substitute in the smart values just-in-time. Kind regards, Bill

Hi @aman grewal -- Welcome to the Atlassian Community! An automation rule could use a web request to call the Jira REST API to edit the name of a sprint, provided you know the sprint id value. However, I am unclear from your described scenario why you would do this. You seem to describe a flow where stories are refined…

Hi @Martha Evert The Atlassian interpretation of a "control chart" is based on Jira board columns, and so the chart's selected time range is based on the issue history for the status values mapped to the columns. This means the report could be based on create date (when the first possible status is in a column), or another…

Yup...there are no issues from the trigger...from which to copy the project or type. In your issue create, if you select the project and issue type from the dropdowns the error will be fixed.

Gotcha, and thanks for clarifying. When a rule triggers with an issue, the data remains in the as-triggered state even when issues are written out to the cloud/server. When you want to refresh after an edit, add a Re-fetch action before proceeding. This works for rules with a simple flow...branches that could be on more…

Hi @Inna S In your images, you are showing multiple different variable names for the smart value expressions, and they do not seem to match. For example, the Advanced Branch is showing {{TargetVersionsList}} and you do not show what that contains. Normally the branch is where the split occurs on an object or string. Would…

That should run it immediately...unless the trigger has JQL (which I believe you removed). What does the audit log show now?

Hi @Andy McCormick I do not believe you can use fieldChange or changelog that way in an issues field condition with JQL. Would you explain what your JQL is trying to test? In the meantime, this would test if the triggering issue had a previously * advanced compare condition* first…

After the change, did the issue create work as you expected?

Hi @Jason M_ I am not quite following what you are trying to test...is it: * you want to check for a label value named "newTrunks", or * you want to check for a label matching the contents of the created variable {{newTrunks}} And one more thing...When using basic conditions, the rule only continues if the test passes. If…

Would you please post images of your complete current rule, including details of any created variable actions or edits with JSON, and the details of the audit log showing the rule execution? That may help provide context for what you are seeing. Thanks!

Smart values are name, spacing, and case-sensitive...including the built-in ones. And I noticed you have the case incorrect for the lookup ones, which would return empty values. Please try following this template, noting that lookup is lowercase and Issues is uppercase: {{lookupIssues.first.summary}}

No idea, as just parent should have worked. Would you please post images of your current rule and of the audit log details showing the execution? Perhaps we are missing some context by only looking at part of it. And just to confirm, you are using Jira Server (or Data Center), correct?

Thanks, @carolina One basic rule would be this, for when a new issue is created and added to the epic: * trigger: issue created * action: re-fetch issues * condition: issue type is story, task, bug (i.e., not an epic) * branch: on JQL with key = {{triggerIssue.parent}}* action: lookup issues with JQL of project =…

Awesome! I am glad that worked :^)

Hi Alan, and welcome to the Atlassian Community! Many of the advanced roadmap fields are not supported by the built-in automation actions yet. Instead you must use JSON to access them, as described in this suggestion: https://jira.atlassian.com/browse/JIRAAUTOSERVER-159 A few things to investigate... (1) First, smart…

What is the type of your project: company-managed or team-managed? You may find that at the bottom of the left-side expand panel on the page. What is the type of that custom field: text, single-select option, etc.? Knowing that information may help explain what you are observing, as that field appears to contain something…

Thanks for that information. As the current value is the one not working, perhaps just use the current value and conditional logic, like this: Current value: {{issue.NBIP Release}}{{#if(issue.NBIP Release.isEmpty)}}None{{/}} Both parts appear to be needed when a field has ever contained a value, as it will not be null for…

Ah...something is different with this one, as that "value" may be an object and not a text value. Otherwise it could not possibly display those icons with the data... Or do your drop-down values contain icons at the front of each value? If they have the icons, you may want to try endsWith() instead of startsWith()

First, three things to consider for implementation of this approach: * Identify the precision you want. I recommend going no lower than hours, as that will give you about 0.05 days resolution. * identify your starting and ending time per day (e.g., 8am to 5pm). If you do not care, assume 0000 to 2359 every day. * identify…

Hi @Cyril James One way to do this is to add a related issues condition to exclude cloned issues, as below: * trigger: issue created * action: re-fetch issue (Including this is a good idea when using the issue created trigger, as it can occur so quickly that the data is not available yet.) * related issues condition:*…

Let's pause for a minute to confirm some things: Are you using a Company-Managed or Team-Managed project for this rule? Is your scenario to edit an Epic, setting a custom field to the count of child issues in the epic? If so, how are you using that custom field? (Knowing that will determine the accuracy needed and the…

Okay, let's confirm the custom field contains what you expect first. Please add an action to write this to the audit log after your lookup issues action: {{#lookupIssues}}{{customfield_16276.value}}{{^last}}; {{/}}{{/}} That should produce a list of your custom field values, separated by semicolons. If you see anything…