Bill Sheboy Expert

Thanks for that information, and I am still confused by what your trigger is: You describe wanting to trigger on a change to your custom field ("Scheduled Date and Time") and then show a trigger apparently on the comment being added. Which do you want to do? If you want what you show in the rule image, your condition would…

This is awesome! Thanks to you and the team, @Sam Harding !! Does this close out this suggestion I made, or are there still some unavailable fields? https://jira.atlassian.com/browse/JRACLOUD-75018 Kind regards, Bill

Thanks for the image of your rule. I believe that {{issue.issuelinks}} only contains the keys and not the rest of the data (such as story points). You could confirm this by writing the following to the log in that branch to learn if any values are shown: {{#issue.issuelinks}} {{Story points}} {{/}} And even if that did…

Hi @Sandra Kabamba You may do what you ask with a scheduled trigger (perhaps checking daily) and a JQL statement to find the relevant issues. For example: project = myProject AND NOT status CHANGED AFTER -2d AND status IN ("Blocked", "Code Review") Kind regards, Bill

Hi @John Ricard Given the reporting needs you describe for your use case, you could try a couple of ways to solve this: * investigate marketplace reporting options, or scripting addons to increment a field * add a custom field for the counter, and use an automation rule to increment the field If you are interested in the…

Hi @박보은 The rule you posted appears to do that, using a JQL branch to iterate on some specific issues, triggered manually. What happens when you run that rule that does not work as you expect? Kind regards, Bill

Hi @Warda Basta What problem are you trying to solve doing this? Why not just copy all of the labels to the children? The use case you describe is not that simple, as you would need to parse each label to determine if it contains your text, such as "_anything". In addition, what do you want to happen if that label is…

Hi @Ori Lazar I recommend trying a couple of things: * Try the generic issue updated trigger instead, and check the changelog to see if your field changes. If that trigger also does not fire... * Contact the vendor in the marketplace to learn if their fields can support automation rules. There appear to be two different…

Hi @SHANAVASH MOHAMED There is a known problem with the issue created trigger (and perhaps others) where the rule can fire before all data is available. This results in your conditions not being met. The work-around for this symptom is to add a Re-fetch action immediately after the trigger and before the conditions. This…

For a company-managed project, please check with the project admin.

Hi @Randy McLaurin -- Welcome to the Atlassian Community! Are you using a company-managed or a team-managed project? * If company-managed, you may want to consider using swim lanes by Assignee rather than changing the board filter's sort order * If team-managed, you may group-by assignee to have the same result Kind…

We are not using delete, so you would need to try that to see if the change to the links triggers the rule. We disabled delete and instead use a custom field, Abandoned. There is no "undo" with Jira Cloud, so it saves a lot of "oops" situations.

Hi @Anne Dietz -- Welcome to the Atlassian Community! I wonder if you could change to just use the issue updated trigger and update your count unconditionally. This would cause a few unnecessary updates due to changes from unrelated fields (e.g. description comments, etc.). You might mitigate that by using the changelog…

Hi @Apoorva Pahuja -- Welcome to the Atlassian Community! Please post images of your complete rule and the audit log show details where the rule does not work as you expect. That may provide context for what is happening. Thanks! In the mean time, consider adding some log statements in your rule to confirm the values you…

Hi @venkatakrishanan r Please take a look at the scheduled trigger documentation to learn if it will provide what you need: https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/#Automationtriggers-Scheduled Kind regards, Bill

Hi @Denis Perhaps you could do this with repeated or chained replaceAll() functions on the values -> labels, and then use an advanced edit with JSON to add the values from a stored created variable. Kind regards, Bill

Perhaps try replaceAll() as I suggested using a simple expression which looks for the common elements between the exclamation points: {{issue.comment.body.replaceAll("(!.*width=.*height=.*!)", "")}} You may need to experiment with this as I am not familiar with all possible formats of images in the markup.

Please try to use the linkedIssues() function: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-linkedIssueslinkedIssues-- For example, to find the linked stories for the trigger issue: issue IN linkedIssues( {{triggerIssue.key}} ) AND…

Thanks, Joe! Limiting scope for dropdowns, etc. has been an ongoing challenge for Jira. And some of the design choices for team-managed definitely make that worse (e.g. cloning all the status values for each project). __Bill

Hi @Steven Sanyal You may try this how-to article to learn if there is a smart value for your field. Essentially you identify an issue with the data and call the REST API from a browser to find the field. https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/ Once you have that smart value…

Hi @Louise de Melo Macedo I do not believe that is possible yet, and here is a suggestion to add epics to that report. You may vote for/watch it to see progress...although this one is several years old: https://jira.atlassian.com/browse/JSWCLOUD-14688 Kind regards, Bill

Hi @Henry Min Yes, and...to what Nic notes: Here are the suggestions to allow different subtask types for team-managed projects, which you may vote for/watch to see progress: * https://jira.atlassian.com/browse/JSWCLOUD-18117 * https://jira.atlassian.com/browse/JSWCLOUD-20901 Kind regards, Bill

Hi @Dominik Trunk -- Welcome to the Atlassian Community! You *could* create a rule, triggered on sprint creation which checks for any issues with due dates during the sprint timeframe, and take action. Rather than adding such issues automatically to the sprint, you may instead want to notify the team to consider their…

Agreed, and...In those backlogs only the support staff can add defects (I believe). So unless your site admin submitted a ticket leading to a defect, many customers just create "suggestions" to at least make the symptom visible. __Bill

Hi @Javanshir Mustafayev _ HIT Nic was describing how to do this technically, and I was noting this may not solve the root issues...and in fact could cause new challenges for your teams. Please see Nic's post for his solution ideas. Thanks, Bill

Patrick, let's go back to your original question to confirm what you need, as I may be overcomplicating this. Your use case is quite unique, and different from what teams often do for backlog refinement with Scrum. * It appears your team is pre-defining multiple sprints in advance. Correct? * And that issues are…

Sounds good, David. If you have issues creating your rule, please post the rule and audit log images so the community can help. Thanks!

Hi David, I am wondering if I misunderstood your use case. Let's try some specific questions to get back on track: * What do you want the pie chart to indicate? (i.e. What problem are you trying to solve?) * What statistic type are you using for the pie chart? * For the sprint, are the epics and stories/tasks both in it,…

Hi @zzalowitz Yes, and...to what Mykenna suggests: Are you using Jira Cloud or Server/Data Center? * Cloud:* You may use JQL with the Lookup Issues action Mykenna's notes to send one email/message for the batch. Please look here for more…

Hi @Liubov Dudnyk -- Welcome to the Atlassian Community! That is a known issue for custom fields, as described in the documentation on migrating projects: https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/ One work-around that may work for moving from…