Bill Sheboy Expert

Hi @Chasovskikh Kirill Adding onto John's answers and questions... What problem are you trying to solve with fractional months? The fractional values are not comparable for months with differing numbers of days 28, 29, 30, or 31, right? For your question about just days-differences, do you mean you have two literal date…

Hi @Esteban Borja Lopez The information you need to answer the questions in your use case with custom fields are in the issue history, and that information is neither easily consumable by automation nor easily reportable by Jira with out-of-the-box features. The specifics of your use case will determine how complex this is…

Hi @Deepa Narasimhan The answer depends upon the type of checkbox fields you are using: * With a built-in checkbox fields, you could either trigger on a change to the field and save old value from {{changelog.myCheckboxField.fromString}} or call the REST API to check the issue history * With a checkbox field from a…

Here are the open suggestions and defects on the public board, which you may add to. Some of the questions I noted above are already open suggestions:…

Good question, Spencer. Probably a design choice for simple-over-complex implementation. As John noted, there are marketplace addons to close some gaps. Other questions/challenges for Kanban features are: * Why is the "control chart" not an actual control chart? * Why is the "CFD" not an actual CFD? * Why aren't basic…

Thanks for that suggestion, John!

Hi @Brenda Strong Yes, and...to Trudy's answer: The linked suggestion to add this capability describes a work-around of an automation rule calling the REST API to move the new issue to the board. That work-around lists the wrong function to move issues to the board, so if you want to try this technique the correct one…

Hi @Spencer Offenbacker -- Welcome to the Atlassian Community! No, and yes-ish... No: there is no built-in Jira feature to visualize this very common way of showing items on a Kanban board. Yes-ish: one work-around is to create different status values for each, such as Build, Doing and Build, Done. One advantage of this…

Joe, I am glad to learn that helped. Global/multi-project rules may be created by a site admin, and they can reference all or specific projects. Some things to note if you use such rules: * There are limits on the number of rule executions per month for global/multi-project rules. (Executions are essentially unlimited for…

Hi @Joe Miller Please post an image of your complete rule and the audit log showing the details where the rule did not work as expected. That will provide context for the community to comment. Without that information, I can hypothesize, either: * You are using Lookup Issues but did not first call the Lookup Issues action…

Just to confirm did you recreate the rule in the other project, or change the rule to be global/multi-project in scope? That is important if one of the projects is team-managed, as they have separate instances of status values for each project...even though they may have the same status names.

Hi @Ifteqar Ahmed Yes, and...to Tessa's ideas: The visibility information is only available with the smart values from the comment-related triggers. However it does appear the visibility information is available from the REST API functions for issues in case you want to try that route with a web request. Kind regards, Bill

Hi @Sasika Nanayakkara -- Welcome to the Atlassian Community! You noted this: How Calculated: Duration of a task/issue will be calculated by counting the amount of active working time (business days) between the scheduled start and end of the task. This is generally the time from task start to finish, not counting time…

Awesome! The REST API can be used to solve several gaps/limits in automation...even if it is a bit slower for the rule. I am still waiting to hear back from the Atlassian team if the smart value list filtering should work with smart value parameters. If that ever works it will solve a lot of use cases. Perhaps watch that…

If this rule is running as a global/multi-project scope, I believe that would still work. If the most-recently-created branch does not work, a global/multi-project rule could still use JQL for your created issue key for the branch. Please note, that there are execution limits per month for global/multi-project rules, so…

Hi @Stephen C Hauer Following up this thread... Short version: There is a bug/design issue here, and I recommend working with your site admin to submit a ticket to Atlassian Support to take a look. Longer version: I found my complicated example rule which uses smart values as a parameter to rightPad() and it still works.…

After the issue is created, you may branch to it and then use the Comment Issue action. For example: * trigger: whatever you are using * action: create issue * branch: on most recently created issue* action: comment on issue... adding information from the trigger issue to the new one {{#triggerIssue.comments}} Comment by:…

To use a smart value expression like that in an edit, please try: * typing (or pasting) in the expression * it will then appear below the field * select the value which appears... * and then it will save for usage

Hi, Ro! Although you could use a custom field to store the copy, you could also add them as comments, either as one giant comment to the new issue or one-by-one (with an advanced branch). If you take a look at those links I provided they show examples of how to iterate over the comments list for an issue. For example:…

Hi @Even -- Welcome to the Atlassian Community! This question comes up periodically, and the easiest answer is to use Sprint Names which always sort alphanumerically later when they occur later...Then your technique would work with {{issue.sprint.name.max}} But if they do not... First, and to save you some time, there is…

Hi @mbrandel -- Welcome to the Atlassian Community! Two ways I can think to do this are: * Identify the sprint ID (not the name) and query on that. The ID will be unique for each sprint. * Query and the name and add other criteria that includes date information, such as updated, created, resolved. Kind regards, Bill

Hi @Jonathan Nogueira Such nested queries are not possible with out-of-the-box JQL features of Jira Cloud: JQL is not a SQL. If you need such queries often, please investigate marketplace addons, such as @Jorge Martinez has suggested. If you need this once/a few times, I recommend doing this in one of two ways: * Use a…

Hi @Rosana Casilli The issue comments are a list smart value, and so you could iterate over them to add to the new issue. Please look here for information about the field: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.comments-- Next, you asked about filtering to only copy the…

Hi @Christy Small No, not with exactly that filter with a list of versions. Here is the suggestion to add the feature: https://jira.atlassian.com/browse/JRACLOUD-74470 As a work-around, you could use "Custom Filters" for a team-managed project to add specific filters by version, or more generically something like this:…

Hi @Milan Šalka To do what you ask would most likely require a stand-alone application independent of Jira built-in-features. Accessing Jira issues uses a browser or some other application connected to Jira Cloud, such as by the REST API. Please investigate the Atlassian Marketplace to learn if such an application to meet…

I agree it may be time to ping Atlassian Support. They have access to logs users cannot see and so may notice something we are missing. When you hear back from them, please post what you learn so the community can benefit. Thanks!

I am glad to learn you got it to work. Remember to check the field types when using automation rules; as you noted a "text" field needs to be converted with asNumber to be used in math operations.

Sarah, would you please post an image of your edit action details? The image above seems to indicate you put in the format() information without the quotation marks that John suggested, and that could be the cause.

Hi @Sameer Bansal Are you asking, "how can a count the distinct pull requests related to a specific issue from an automation rule"? If so, that does not appear to be possible with built-in features. The {{pullRequest}} smart value is only available/relevant when there is a pull request trigger (created, declined, or…

Hi @Randy Knight Although nested smart values for functions do not work yet, and created variables as function inputs do not work consistently, there may be another approach... You appear to want some piece of the description, so perhaps using a regular expression with match() to extract text and the parsing further would…