Bill Sheboy Expert

Thanks for explaining your use case! You are on the right track, using the trigger to detect the epic create, as you have done, and then create each task and its sub-tasks, one by one. That will ensure they are linked as you expect. There are two ways to do this: one rule or two rules. One rule: pros are one-rule; and con…

Thanks for posting the image of your rule. As I suspected, with this rule layout you would need to: * capture and save the key as you create each of the tasks, storing them in a created variable * use the created variables to set the links using the advanced edit JSON information I provided. But before you try that, would…

Hi @wendt279 As soon as you add those extra creates and branches, the rule can no longer do what you note, as the only built-in options for linking are to the trigger issue or the "most recently created issue". Please consider posting an image of your rule, as that will help confirm this is what is happening. In that case,…

Hi @wendt279 Are your sub-tasks on the trigger issue or on the newly created one? If it is the newly created one, your rule probably looks more like this, with a branch, right? * trigger: issued created with component "X" * action: create new task * branch: most recently created issue* action: add sub-tasks If so, in the…

Hi @Muhammad Guntur -- Welcome to the Atlassian Community! You may want to try the Lookup Issues action with JQL. After your trigger, you could use the action to gather the issues and sent them in one email. Please look here for more information on Lookup…

Hi @Alex Wrobel You could do that with custom fields to maintain the amounts (e.g. Values you note), and either Automation for Jira or a marketplace scripting adding to compute the fields. Please talk this over with your Jira admin to see what they think about the approach which works well for your use case. Best regards,…

Okay, that is odd. For a user field the ID attribute should be present for setting. Have you tried to just use the field name "Developer" from the drop-down list? The custom fields I am using are listed as available fields for the edit issue action.

That's curious... would you please post an image of the component where you create the {{inProgressSiblings}} variable? And, would you please explain why in some cases you are adding spaces around smart values and in other cases you are not? For example: parent = {{ inProgressSiblings }} AND status = "In progress" I…

Daniel, here is a specific example which is listed in that template library link I provided above: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/140671 This one uses issues and sub-tasks, but the approach is the same for parent/child synchronization.

Thanks for clarifying! If you are specifically trying that product, I recommend emailing the vendor directly to ask...they will be able to give you the best answer: https://marketplace.atlassian.com/apps/1220574/agile-docs-estimate-tree-for-jira?hosting=cloud&tab=support

Hi @Kojo Usually, a product is in the marketplace to provide features not available in out-of-the-box Jira. And, I know of no similar report in Jira. There are related reports in dashboards, roadmaps, and the built-in time reports. As a work-around, you could export your data to a spreadsheet or other reporting tool and…

HI @Daniel Johnson Yes, that is possible with Automation for Jira. There is a free (Lite) version and a paid (Pro) version in the marketplace. Please look here for more information: * https://www.atlassian.com/software/jira/features/automation *…

Hi @Victor Tobon Yes, and...to what Trudy suggests, please look here for more information and examples on the automation math operators: https://support.atlassian.com/jira-software-cloud/docs/smart-values-math-expressions/ Best regards, Bill

Hi @e_shakalov Yes, and...to what Trudy noted: here is the suggestion to add quick filters for team-managed projects, which you may watch or vote for to see progress. https://jira.atlassian.com/browse/JSWCLOUD-17446 Best regards, Bill

Hi @Christine Coenen I do not know of a way to query that with out-of-the-box JQL. The closest thing to it is the built-in sprint report information. There are marketplace scripting addons which might support this with extensions of JQL. Another option would be to use a custom field and an Automation for Jira rule to mark…

Hi @Simmo Thanks for your response! Apologies for my wordy answer... ;^) I understand about the performance issues you note for lookup issues, and any fields that could be added would be appreciated. I often note people asking about synchronizing things like start/due date and custom fields for parent/children...and…

Thanks, Janez. To help my understanding, what is not working/happening when you do this in one rule? I believe using {{createdIssue}} should work, and if there are multiple issues you could instead use {{createdIssues}} (note the plural) with a branch.

I believe created variables are strings, so please try this in your comparison condition: {{inProgressSiblings.asNumber}}

Thanks, Shannon...but I do not work for that company. ;^) Did you mean to use Lenny's name as an example. Best regards, Bill

Hi @Lenny Emmerton When recommending a marketplace vendor product, please ensure that you disclosure your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @Brandon Mahan Please look at this post for ideas on how to solve this using regular expressions and advanced compare conditions. https://community.atlassian.com/t5/Automation-questions/Assigning-round-robin-according-to-the-hour-of-the-day/qaq-p/1651142 Best regards, Bill

Hi @Ryan Yes, that is a known issue that changing the epic link/parent doesn't trigger yet, so the work-arounds are still needed. * https://jira.atlassian.com/browse/JIRAAUTOSERVER-15 * https://codebarrel.atlassian.net/browse/AUT-1987 Best regards, Bill

Hi @Mark Cartwright Adding on to what Tom suggests, for Jira Server/Data Center automation, the equivalent to Cloud's Lookup Issues is to use a scheduled rule and change the settings to treat the issues as a batch. Then you can use the {{issues}} (note the plural) the same way as Lookup Issues. Best regards, Bill

Hi @Chris Carpenter If you can write a JQL statement for the issues you care about, you could use the Lookup Issues action, and then average the story points (or story point estimate for a team-managed project): {{lookupIssues.Story Points.average}} Please look here for more information:…

Hi Jennifer, I am unclear what you mean by a "commitment metric". For each project type, those are the relative-sizing measures supported. When team-managed (formerly next-gen) got added, the Atlassian team apparently did backend improvements leading to the need for the new field. And, for each respective project type,…

Hi @Jakub Sławiński When recommending a marketplace vendor product, please ensure that you disclosure your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @janez_m Is your rule trying to do the following: * trigger: scheduled rule running JQL to gather some issues * action: create issue (I am assuming using some data from the each issue found by the trigger, one by one * action: assign the newly created issue round-robin If so, and the challenge is selecting the newly…

Hi @Jennifer Dragan -- Welcome to the Atlassian Community! What type of project are you using: team-managed or company-managed? Team-managed projects use the Story Point Estimate field and company-managed used the Story Points field. Best regards, Bill

Hi! It is a bit hard to see the details, but it appears you have extra spacing in the smart values, such as {{ myfield }} so perhaps try removing those first: {{myfield}} Next, I suggest that as you create each variable, add it to the audit log. That will confirm it has an expected (or unexpected) value for your testing.…

Yes, and...here is a related suggestion for the Cloud version: https://jira.atlassian.com/browse/JSWCLOUD-17698