Bill Sheboy Expert

Hi @Jesse Ortega Jr Perhaps consider using a Lookup Issues action with JQL rather than the branch: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues Once you have identified the linked issues you may check the resulting count that match your criteria with an advanced issue condition…

Hi @Milena Lopes -- Welcome to the Atlassian Community! You cannot change the project type but you can migrate the information to a new project, as described here: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/ Please read over the limitations and "things…

Please post images of your automation rules and the audit log details, rather than posting links to your company's site instance. What is not working and what do you observe? What have you tried to diagnose the problem? (e.g. review audit log, review the issues, review the workflow, etc.)

Hi @Mohajit Acharya Yes, and...to what Ravi suggests: The other post you linked to is for a team using Kanban methods and not Scrum. If your team is indeed using Scrum, perhaps consider how you are planning sprints and monitoring the progress of work toward the goals (e.g. with burn charts) rather than creating…

Hi @Phillip La -- Welcome to the Atlassian Community! If I understand your question correctly, you appear to be asking if the maximum (leftmost starting point) value for the burn chart should change after the start of the sprint...that is, after sprint planning completes. That would hide valuable information: something…

Hi @Cherrie Lee -- Welcome to the Atlassian Community! Yes, and...to the answer from @Tansu Akdeniz You appear to be using a Team-managed project, so here is the help for the "Custom Filters" feature: https://support.atlassian.com/jira-software-cloud/docs/manage-custom-filters-in-team-managed-projects/ For Company-managed…

Hi @ydai -- Welcome to the Atlassian Community! Reviewing the documentation on the CONTAINS ~ operator: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-operators/#Advancedsearchingoperatorsreference-CONTAINS-CONTAINS-- I wonder if you are encountering two effects related to word…

Hi @Hrag Would you please post an image of the audit log details showing any error which occurred? Just to confirm, the project where this rule exists is company managed AND you are also creating the new issue in the same project, correct? To check on the custom field duplication, as your site admin to navigate to the Jira…

Hi @Dennis lasko -- Welcome to the Atlassian Community! That would be the accountId for the users; to see the display name please use: {{issue.reporter.displayName}} Please look here for more information about user field, smart values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/ Kind…

Hi @siond No, there is no such trigger for automation rules. If your rule maintenance is cumbersome, consider creating three rules: * Trigger on Create Issue, and make an update which can trigger rule #3 * Trigger on Update Issue, and make an update which can trigger rule #3 * Trigger on the condition created by rules #1…

Hi @Hrag -- Welcome to the Atlassian Community! What type of project are you using: company-managed or team-managed? Company-managed projects use the "Story points" field and team-managed use the "Story point estimate" field. Have you confirmed you are using the correct one for your project type? After checking that, if…

Hi @george.guthrie -- Welcome to the Atlassian Community! I do not know why, but some fields are not listed for the basic field condition. Instead please use the advanced compare condition and check the field's smart value. If you have trouble identifying your field's smart value, or custom field ID, please use the…

Hi @benjamin.ugbene Possible solutions depend upon what you mean by "in progress" and if you are using a Company-managed project: 1) If "In Progress" is an actual status value and you are using a company-managed project, you could set a card-color filter with JQL such as: status = "In Progress" AND status CHANGED TO "In…

Hi @Gizem -- Welcome to the Atlassian Community! First thing: please consider creating a new question and linking to existing threads. That will ensure the most number of people see your question to offer ideas. Otherwise only the people following existing threads will see them. Thanks! Regarding what you asked... Are you…

Well done, @Matteo Cristiani One more thing of note: sometimes when Created Issue triggers it occurs so quickly that all of the data is not present yet. The impact is conditions could fail to match on the issue (because the fields the rule sees are empty). The work-around is to add a Re-fetch action immediately after the…

Hi @Sari With an automation rule you can detect the comment was added and find that specific text. The possibility of the next action depends upon what you mean by "next unreleased version": * if you mean the same thing as Jira's definition (i.e. there is a next version to release in the version list page) then you could…

Hi @Randy Simes -- Welcome to the Atlassian Community! I note at least one missing parenthesis to close the match() function...and... Without seeing the remainder of your rule, perhaps try using smart list filtering: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Or, split…

Hi @Oliver Asaah -- Welcome to the Atlassian Community! I do not believe there are any built-in features to support team capacity management. There might be marketplace addons to help manage this, or the team could discuss their capacity at sprint planning. Kind regards, Bill

Hi @Arnav Would you please describe the steps you followed to try to solve this problem/need before posting this "question"? For automation rules, please consider trying to solve the problem yourself and asking the community for help when you run into challenges. One of the better ways to learn about rules which meet your…

Hi @Deepa Narasimhan No, that is not possible with the out-of-the-box gadgets. You could either use the concatenated field approach you describe or investigate marketplace gadget addons to do this. Kind regards, Bill

Looking at the image you posted, the issue edits are outside of the branch. Please try this, noting the nesting of the rule components: * trigger: sprint started * branch: issues in the sprint* if/else condition* condition: End Date is empty * action: edit the End Date to set the field * if/else condition* condition: Start…

Thanks, and I just learned something new: they have apparently removed that feature from the backlog view for team-managed (formerly called nextgen) projects. No idea why they would do that. It does appear the new "issues navigator" on the team-managed (from the left pane) does support bulk change for all the returned…

Bulk edit (change) is available from Filters > Advanced Issue Search > ... > Bulk Change

Hi, Patrick. Please try to stick to one thread in responding; otherwise people may think there are multiple answers to the question. For that error message: cloning issue links is not supported yet for an automation rule. Here is the suggestion to add that: https://codebarrel.atlassian.net/browse/AUT-2133 I believe the…

You may use the function asPercentage to do that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/#asPercentage Please note... Also I noticed that you were clearing fields in a rule with edit, and then editing again. Rules always start an edit from the data values at load time when…

Hi @Patrick Cigana For a question like this, please consider posting images of your complete automation rule and the audit log details showing the execution that doesn't work as you expect. That will provide context for the community to offer ideas. Thanks! Kind regards, Bill

Hi @Guaraci Nakamura That error is telling you something which can sometimes be confusing... Most of the triggers are on issues. But the ones on sprint events may not be as there might not be issues assigned, so they are not automatically provided. Instead please try replacing that if-condition you note with a branch on…

There are two ways to perform most of the math operations with smart values: Inline with dot-expressions: {{issue.myFieldA.multiple(issue.myFieldB).divide(10)}} With the {{#=}}...{{/}} syntax. The equivalent of the above would be: {{#=}} {{issue.myFieldA}} * {{issue.myFieldB}} / 10 {{/}} Please look here for more details…

Thanks for clarifying. Those images are stored as attachments, so the brute-force way to do this is to exclude anything with an attachment: project = myProjectName and description ~ "h1." AND attachments IS EMPTY That might include things you want (like non-image attachment issues), so instead once you have the list loaded…

I recommend submitting a ticket to Atlassian Support for this; perhaps they either do not know it is missing or do not know people want to access it. The benefit of submitting the ticket this way is to get the actual automation team people looking into it.