Bill Sheboy Expert

Thanks, Esther! I just retried it myself and it triggered the rule. Very curious.

Hi @Zijian Zhu -- Welcome to the Atlassian Community! The gadget you reference is the JavaScript Charts for Jira Cloud, and it can plot many different things over time...for multiple issues. What you describe is using the issue change history to plot the changes in a field value over time. That gadget cannot do that. Two…

No worries; automation requires a lot of self-teaching and experimentation. I am learning stuff daily as I try rules and read community posts. Would you please post images of your current rule and the audit log details showing the execution? That may provide more context to make adjustments. Thanks! For the specific…

Hi @Anna and @Esther Strom I recall there was a defect in the old Code Barrel backlog (now part of Atlassian) that issues created from a roadmap did not generate the Issue Created event for rules. That backlog is no longer publicly visible so I cannot confirm that, and the defect (apparently) was not added to the new AUTO…

Hi @Danny Zaat Now that you have your field copied from the Initiative to the Epic, you may need one or two more rules to cascade down the information, using a divide-and-conquer approach: * one rule approach* triggered on an update to your field * add if/else conditions, one for each issue type level (e.g. epic versus…

No worries; some of the documentation is a bit vague, and so requires a bit of experimentation to learn what works (or doesn't).

I believe the JQL for the lookup issues action would be: "Epic Link" = {{triggerIssue.key}} That should return all issues which are children of the trigger issue, the epic.

In the action to create the issue, have you tried to set the Epic Link field to your specific epic?

Hi @Nagarjuna Busireddypally The "days in column" feature only shows the dots; when you hover over them, the day count is shown. Next...if you regularly improve your workflow/board layout, that is not tracked well in Jira. You may have trouble managing those measures in that case. The built-in Atlassian interpretation of a…

Hi @Antonio Campagna One reason you may find complex solutions for this use case is there are a lot of variables...depending on your situation. One possible basic rule for this could assume it is triggered manually from an epic: * trigger: manual * condition: issue type is Epic * action: lookup issues with JQL to gather…

Thanks for that information. If you want to try automating this, I described a rule earlier that might help. There is a manual way to do this in one step, given some constraints: * let's say most of your items have epics (or you focus on one/few epics at a time) * in the backlog, and before adding the issues to the…

Hi @Bhavik Chauhan Which dashboard gadget are you using, and is it a built-in or marketplace addon one? What is the error being displayed? Perhaps posting images of the chart, the gadget settings, and the error will help provide context for suggestions. Thanks! Kind regards, Bill

Hi @Maroun Maroun First thing: Unless you have only one epic and one story in a release, this may be difficult / not-work-how-you-want-it-to-look in the report. For specific reporting needs like this you may want to investigate the marketplace for better release reporting. There may be free options in the marketplace to do…

Hi @Omri -- Welcome to the Atlassian Community! What problem are you trying to solve by doing that? Or thinking about this another way, how would you work differently if you had that information right now? Knowing this may help the community to offer other approaches to solve that problem. Until that information is…

Hi @rweston What problem are you trying to solve by doing this? Knowing that will help the community to offer suggestions. Until that is described... What do you mean by "moved to the top of an epic"? For example, do you mean the display order of the child issues in the epic view? If you do, Rank is the default, display…

In that case, you may want to contact Atlassian Support to learn if this is possible with a rule. You appear to be the site admin for a paid license level, and so you can do that here: https://support.atlassian.com/contact/#/ Once you hear back from support, please post what you learn to benefit the rest of the community.…

Thanks, and that makes sense. The issue created trigger can fire so quickly that the data is not available when the rule starts. The common work-around is to add the Re-fetch action before any conditions/actions; this will slow down the rule by about a second while the data reloads.

Have you tried to assign it to the epic when you create the task, by selecting the certain one you want?

Hi @Raymond de Ribains -- Welcome to the Atlassian Community! You may use a JQL Condition for that, with: sprint IN openSprints() That will test the specific trigger issue. Kind regards, Bill

What do you mean by "go to epic"? For example, do you mean assign the new Task to an Epic as a child issue? If so, how do you know which epic you want?

Hi @Julia First thing: I am not using ScriptRunner or Jira Server/Data Center; I am using Jira Cloud. So my suggestion is based on what I know about automation rules, in general. That type of field appears to have some structure, and you are trying to give it a text field...rather than an array. So a few things to check…

Thanks for that information, and...FYI I am not using JSM so my suggestions are based on the documentation and what I know about automation rules. Does the Edit Object action have an option with edit with JSON, does it have a ... menu to the right side of a field when you are editing it? If so, there may be a way to add…

If you review that documentation, and the linked Java format reference, you can find how to combine these, such as with this: {{issue.fieldName.asNumber.format("###,###,###.00")}} Please adjust for a format as large as your numeric value can range. 

Hi @Nikita That error message is telling you the rule trigger (i.e., Scheduled) does not supply any issues for the action you want to take (i.e., Add Watchers). The fix for that is to add a branch to access the newly created issue: * trigger: scheduled * action: create the new task * branch: on most recently created issue*…

Hi @Johannes Nyberg What is the type of your field? If it is text, have you tried using the concat() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#concat-String-str- Kind regards, Bill

Hi @Rafael Ibanhez You appear to be asking about formatting a number with an automation rule. Is that correct? If so, please try this: {{issue.fieldName.format("0.00")}} Kind regards, Bill

Hi @[deleted] -- Welcome to the Atlassian Community! That does not appear to be possible yet for Jira Cloud. Here are a couple of suggestions to add that capability, which can be watched/voted for to see progress. (Please note that one is marked as "duplicate" and closed, referring to the other.) *…

The allow rule trigger setting is in the rule details, at the top of the rule.

Hi @Phil Bustin Which specific emails are you asking about, or do you mean *all emails sent by rules"? For the action-based ones for Edit Issue, those can be disabled by the action settings. I am not aware of a generic setting to disable-all-emails, such as to block the outcomes of the Send Email action. I just found a…

Yes, that is the current behavior. I recall seeing a suggestion to make the sprint-related triggers more generic, allowing them to be used in global rules for Premium license customers. (That may not be an option for Free and Standard license users, as the limits of global rule execution would quickly use up their…