Bill Sheboy Expert

Hi @Pearson Fields I suspect this is caused by the problem that the emailAddress attribute is not available for a team-managed project People field yet. (JPD seems based upon team-managed projects.) https://jira.atlassian.com/browse/AUTO-519 If you do not believe that is the cause, please post images of your complete…

Something that may help with that conversation... Discuss what types of work the team does (e.g., planned, unplanned, urgent prod support, etc.), what classes of service the team uses (e.g., how to respond), and how those map to the work item types. For example, if the team and the PM have a shared understanding of "urgent…

I recommend trying the full burndown report for that, as it will show any scope changes and when they happened. For a company-managed project: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-burndown-chart/ For a team-managed…

Hi @Ryan Rayfield Without seeing the details of your rule or fields, I am hypothesizing these are single-select option fields. If so, to use the value of the selection, add the value attribute. Perhaps like this: {{#=}}{{issue.customfield_12345.value}} + {{issue.customfield_67890.value}}{{/}}…

Hi @Bryan.Barr -- Welcome to the Atlassian Community! When you look at the history for an example issue that has been cloned, what do you observe? For example, I wonder if there is another automation rule running which is removing the link information on issue created. If that exists, that other rule is likely in the…

Hi @Varun Modi I respectfully suggest when only tooling is used to prevent changes to a sprint's scope in Jira, there will be unintended consequences, such as: * some work will happen that is not tracked in the sprint * some completed work will be unknown / unsupportable by others on the team * planned work will take…

Hi @Mike Tierney -- Welcome to the Atlassian Community! IMHO, there are no best practices; only better or worse ones for your particular needs / scenario. That being noted... * What problems are your stakeholders trying to solve by having updates? * What do they need to know to achieve that, and with what frequency, level…

Hi @Jason Dunn For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer ideas that may help explain this symptom. Thanks!…

It is possible to add that field to the board and backlog for a Company-managed project. Have you tried to add it?

Hi @anne.gerten -- Welcome to the Atlassian Community! I am unclear if either of those behaviors are documented... The issue search which shows when the JQL runs appears to default to ORDER BY id DESC when no specific sort is provided (and where id is the Issue Id). The order of the issues within that IN () expression is…

Hi @Boyan Angelov _Nemetschek Bulgaria_ You do not post an image of your complete rule, and so I wonder: are those two branches in the same, scheduled trigger rule, one to delete the "user issues" and one to recreate them? If so, have you monitored the rule branching limits and execution time to check for throttling…

That looks correct now. Have you tried testing it yet?

IMHO, these scenarios with empty values are quite the mess in rules: I have not found consistent practices to detect empty / no-value for the various types of selection fields. I recommend creating variables for each selection fields' JSON, and then using conditions to decide when to concatenate them with commas.

Yup, there is a missing branch to most recently created issue above that Link Issue action. Please see some earlier post above for the full context: https://community.atlassian.com/t5/Automation-questions/Re-Re-Jira-Security-Linking-Issues/qaq-p/2616822/comment-id/9491#M9491

Okay, I removed the prior message, as here is the problem: {{issue.comment.last.body.split(" ").match("\[~accountid:(.*)\]").distinct}} The result of that expression is a list...but we stick it into a variable. That then joins the values with commas AND adds spaces to make it more people-friendly for reading. As a result,…

Would you please show the complete audit log details and your full current rule image for context? I suspect there may be a missing / incorrect branch.

Thanks for clarifying, and looking at your revised rule, I note: That error message is likely caused by the different issues (parent and child) have different workflows with different status values. For the issues shown in the log, have you checked their workflows are aligned for the status values: ITSUPPORT-40 and…

That is puzzling... In the change history, please hover your cursor over each date / time entry for those changes at 10:54 AM on 29 January to learn how close together they are in time. If they are the same time, or just a few seconds apart, something automated is definitely performing the change. Do you recall which…

Hi @Sajal Mukherjee -- Welcome to the Atlassian Community! The issue history tracks changes over time, including the transitions. However that is not something that can be queried with out-of-the-box features of JQL. Your work-arounds to see this time duration depend upon how often you need to do this, and willingness to…

Hi @Lee Azahar -- Welcome to the Atlassian Community! First thing, are you trying to perform this status change for Epics and their child issues, Stories and Sub-task, both, or something else? Next, your rule does not match what you described: * Description indicates: when a child issues moves from Done to In Progress,…

Hi @Admin_E3D -- Welcome to the Atlassian Community! Based on what you described, your rule is missing a branch. The Create Sub-tasks action needs an issue to act upon, and so try making this adjustment: * trigger: sprint created * action: create issue for the story * branch: to most recently created issue* action: create…

Hi @Nagaveni Gangaraj -- Welcome to the Atlassian Community! I am glad to learn you were able to find an answer for the query. Please consider looking at this free training and documentation from Atlassian to learn more about writing queries with JQL: *…

Hi @sonu That is not possible. Here is a suggestion to add that capability to Jira Cloud, which you may vote for / watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-67933 The suggestion only notes manually creating the versions as a work-around. Another approach would be to repeatedly call the REST API…

Hi @Chen Qiu -- Welcome to the Atlassian Community! You have posted this question in the automation area, but what you describe is not possible with automation rules. Rules trigger after some action has occurred, not before or during the action. A rule could detect the component change and check fields, notifying the user…

Yes, if that is the correct field name. Again, I recommend testing that JQL stand-alone first to confirm it works as expected.

Hi @Gokaraju gopi Adding to Marc's suggestion: There are several smart values which, for some reason, cannot be used in / with smart value functions directly in rules. Instead they collapse to null values and fail silently. The only way to know this is through experimentation. The suggested work-around to first save the…

Hi @Nick Haller Here is the Jira Cloud version of that article...which was removed recently for several weeks, and now is back. https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Kind regards, Bill

Hi @Rob Parrish Yes, and...to this suggestion: This approach will also show the structure of the smart values within the issue. This can help diagnose problems where values appear empty, but in reality the wrong smart value path was selected in the rule. Kind regards, Bill

When setting the original estimate, the units of measure must be provided. For example: {{issue.subtasks.timetracking.originalEstimateSeconds.sum.divide(60)}}m Adding the "m" on the end to indicate minutes.

Hi @Matt Baillargeon I wonder if this is related to the Modify Reporter permission. You could test that by changing the rule actor to a user who has that permission and see what happens. If it works, that may be a defect that the Automation for Jira user does not have that permission, and you could consider logging it with…