Bill Sheboy Expert

Hi @kunal.matharu Would you please explain the problem you are trying to solve? That is, why do this? Knowing that may help the community to offer better suggestions to solve that problem. Thanks! Until we know that... I suggest only updating the issues in the current sprint, updating them based on the Sprint Started…

Hi @Micael Duarte -- Welcome to the Atlassian Community! That does not appear to be supported yet for rules...probably because the REST API functions do not return that data: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-get There is an open suggestion to…

Hi @Rebecca Lewis Please try using {{now}} without the shortDate part. Adding a format to a date converts it to text. Removing it should work to set a date field. Kind regards, Bill

That error seems to indicate whatever is being passed to link the issues is invalid. Would you please show the details of your Issue Link action? If you are trying to link to issues with the same value in a custom field, your rule would need to branch to them with JQL and then link them to the trigger issue.

Thanks; that is useful info for the future. Even though I suggested that approach... When looking at the data for a single issue (to check any available smart values) those fields for the subtasks are not loaded: https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names I recently read a backlog item from…

Hi @Mathias Mohrs In addition to any other answers provided, I recommend learning about JQL and how to answer such questions with it, helping your team be more effective using Jira. For some free training from Atlassian on JQL, please see these linked items: *…

Awesome! Which one did you use, the first or the second one?

Hi @Juan Camilo Gomez -- Welcome to the Atlassian Community! When you note the rule has not worked, what do you observe happening? Would you please post an image of the audit log details? Those may explain what you are observing. Finally, when using the Issue Created trigger, that can fire so quickly that the data is not…

Yes, that should be possible. This is the minimum steps needed, so please add any others you need. * trigger: issue transitioned * action: create issue (for the new epic) * action: edit issue (This will edit the trigger issue.)* select the Epic Link field * enter this smart value {{createdIssue.key}} * when that appears…

Hi @ROUSSEAU Corentin You describe the rule trigger is Issue Created. Where is the rule defined: in a specific project or in the global rules? If the rule is defined for a specific project, it will only trigger when an issue is created in that project. Kind regards, Bill

Hi @Rafael Gonçalves Leal -- Welcome to the Atlassian Community! I do not believe all of the subtask issues' fields are loaded into that smart value. One way to check that is to change your expression to this smart value: {{issue.subtasks.timetracking.originalEstimateSeconds.sum.divide(60)}} The Original Estimate smart…

Hi @Ekaterina Zvereva For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @Stephen Costanzo -- Welcome to the Atlassian Community! Have you tried to chain all of that together, perhaps like this: {{now.plusDays(issue.timeoriginalestimate.multiply(60)).jiraDate}} Kind regards, Bill

Hi @Cyril.Baurand -- Welcome to the Atlassian Community! I believe that is an known issue, as shown in this suggestion (which probably should be a defect): https://jira.atlassian.com/browse/JSWCLOUD-24129 Kind regards, Bill

Hi @Emna Elleuch For your scenario, it seems you have a Story issue with one-or-more QA Story issues linked to it. And, when the time is log for a QA Story, you want to one of these: * also log that time to the "parent" Story * re-calculate the sum of all QA Story issues time tracking in a custom field If you want to do…

Hi @Rahul Are you using a Scrum board? If so, you may try these built-in reports to see the changes for a release: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-release-burndown-report/ https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-version-report/ Kind…

Hi @yirang Im For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Rachel Ang -- Welcome to the Atlassian Community! When using JQL to check the created field, documentation indicates: Search for issues that were created on, before, or after a particular date (or date range). Note that if a time-component is not specified, midnight will be assumed. Please note that the search results…

This is quite odd... Let's try in-lining the entire expression and writing that to the log: {{changelog.Target end.from.toDate("yyyy-MM-dd").diff(changelog.Target end.to.toDate("yyyy-MM-dd")).days}} And...I noted some of your diff() function calls are missing the units of measure at the end. Please look to see if your…

Hi @Phil Bustin Would you please post images of your complete automation rule and the audit log details showing the execution? Those may help provide context for this symptom. Thanks! Kind regards, Bill

Thanks for clarifying, Julie! In which projects will users comment to the bot user: one project, several, all of them? * If to one project, an automation rule could trigger on issue commented, check for the mention of the bot, and then forward that for some action. Or, a scheduled rule could check once per-N-time-units…

My apologies for the detours...After some testing, I found a bit of inconsistency in the date field checks for isEmpty(), and consistency for isNotEmpty(). Thus we can invert the problem and use this form of the if() function: {{if(someBooleanTest, trueValueToReturn, falseValueToReturn)}} Which works out to this for your…

Thanks for that additional information! FYI: I recommend adding a prefix to variable names for rules and not using anything similar to built-in functions and features, such as "Diff". That will avoid errors / confusion from any typos. For example, perhaps name that variable varDiff. Also, please add writes to the audit log…

Hi @Narsha Bac Those smart values / attributes of the sprint are available in automation for the sprints the issue is assigned to. And those may then be compared with conditions or the date / time rule functions. For sprints not assigned and which you want to compare, those would need to be read using the REST API…

Hi @Patrick Kap -- Welcome to the Atlassian Community! That can be done with an automation rule, a calculated field with a marketplace addon, or with one of the specialized measurement addons. (If you wait a minute, multiple vendors will probably respond to your question with suggestions :^) Also note: the lead time…

Hi @Gil I have not used any addons for capacity planning for any teams I've supported...mostly because different teams do this in different ways. And so we have usually done it just-in-time as part of sprint planning and / or with a simple spreadsheet. My recommendation would be to jot down some notes (with examples) of…

Hi @Shawn Oster What version of Jira are you using? If it is Jira Cloud... You could try creating a variable with the list of projects' id values, separated by commas, and then use an advanced branch to loop over those. In the issue create action, use the branch variable as the project key. * action: create variable*…

The specifics of how to do this depend on the details of your rule. You are only showing the branch, so without more context it is difficult to suggest more. Although if inside of the branch looping over the issues, if you know each issue has one-and-only-one link, you refer to that single one in the inwardIssue list. And…

Hi @Mayra Hernandez -- Welcome to the Atlassian Community! To set an issue as the child of an epic, you may set that child issue's parent field to the epic's key. If the "Epic Link" field is still shown you may also use that in the edit issue action. In your rule, you are creating two issues, thus it is unclear which one…

Greetings, community! First thing: I am not a marketplace vendor, employee of one, or selling any products. I am just a Jira automation user sharing some ideas about managing rule usage after the packaging changes. I recommend customers, particularly Jira admins, fully read the changes to the packaging model and to the…