Bill Sheboy Expert

Hi @Madar, Andrew Yes, and...to Kalyan's ideas: Context is important for automation rules, and so let's look at an example rule to see which issue is "current" at different locations. trigger: some trigger At this point, "current issue", {{issue}}, and {{triggerIssue}} refer to the same thing.action: some actionsame as…

Hi @Doug Bass I just found this note on the webhooks, known issues documentation. The page shows updated as of yesterday, 21 May 2024, but does not indicate when the issue started: * Attachments added on create issue dialog don’t trigger attachment_created webhooks, but they are listed in attachment field in…

Hi @Eric J Trumbull Without seeing the specifics of your automation rule(s)... Team-managed project's People fields are often not shown in the field dropdown lists of rule actions. However, they can be accessed / set using advanced edit with JSON and their custom field ids. To learn more about using JSON for edits, please…

It is not possible to log work on behalf of another user, as the REST API does not support that. Here is a suggestion from over 10 years ago and the last Atlassian updates are from 2015 so little progress noted: https://jira.atlassian.com/browse/JRACLOUD-30197 I also looked in the developer community for this need and only…

Hi, and no worries, Darryl. I updated my post to indicate "I recall..." as without evidence there is no way for me to confirm my recollections. Ideally I would delete my entire question from the community to avoid confusion to others. Kind regards, Bill

Hi @Doug Levitt I have been watching this thread to observe what others find. My thoughts are: There is no information in the article about changes to any automation text functions or math functions / operations to know how they are impacted by the change from no-break space characters to narrow, no-break space characters.…

Thanks for that information, @Doug Bass I removed my suggested workaround as that may no longer work based on what you observed. Perhaps there was a change to the REST API for issue create when an attachment is added at the same time.

Thanks for confirming that information, and so the rule will need to branch to the parent to make the update: * trigger: value changes for your field * condition: issue type is Feature * branch: to parent* action: edit issue. copying the field from the trigger issue

Awesome; I am glad to learn that helped! There are at least three math expression formats I know of for rules. Learning these can help when operations do not seem to work as expected. * the inline one works for number fields and static fields (not stored in lists or from rule calls outward) * the longer form of {{#=}} math…

If you use the JQL standalone with an issue search, do you find issues from all of the people? If "yes", when you look at the user display names for the other people, are they all lowercase, matching the comparisons in your email body?

Thanks for that information, Shaun! Your rule needs a few adjustments; the tricky parts of a rule like this are it is multiple-project and the links are directional. Here is an outline I believe will work: * the rule is multiple project in scope, declared at the global admin level * trigger: field value changes for Story…

Hi @Rosana Casilli 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 @Rhea Gupta -- Welcome to the Atlassian Community! 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…

Hi @David Tieman I agree, and here is a suggestion along those lines which has some comments recommending that addition: https://jira.atlassian.com/browse/AUTO-74 I recommend adding a comment to that suggestion and / or adding some feedback from the rule editor for your ideas. Kind regards, Bill

Hi @Alessio Bilardo -- Welcome to the Atlassian Community! First thing, that plusBusinessHours() function is not in the documentation, and so we may need to guess at the defined behavior until it is documented. When the rule date / time functions access date / times, they default to the UTC time zone. Have you tried…

Hi @Fouad El-Gendy Adding to Kalyan's suggestions: Not all issue changes trigger the Field Value Changed trigger (or the generic Issue Updated trigger) and so not all of them are detected in the {{fieldChange}} smart value for Jira Cloud...even though those changes appear in the issue change history when viewing an issue.…

Hi @Rudy Holtkamp When using the Issue Created trigger, a Re-fetch Issue action is usually needed immediately after it to prevent racetrack / timing errors. This trigger can fire so quickly that the issue data is not yet complete, leading to unexpected behaviors from empty fields in the best case, and unusual errors in the…

Hi @Neeta Dubey How are the issues for the Objective and Feature related: parent / child, issue links, etc.? Is there only one Feature for each Objective? The relationship will determine how to access the Objective, using a branch when the field changes in the Feature, and then the field can be copied from the trigger…

Are you trying to update a custom field named "Story Point Estimate RMP" or the built-in field for team-managed projects, "Story point estimate"? Please post an image of your current, complete rule for context to go along with that audit log image? Also please include an image of the Edit Issue action.

Moving post, as I added it in the wrong thread :^)

Smart values are name, spacing, and case-sensitive, and often they do not exactly match the displayed name for fields on issue views. When an incorrect smart value is used, it is substituted with null, often failing to work as expected. I believe the smart value for that field in Jira Cloud is: {{issue.Start date}} When…

Thanks for the follow-up, Linda. Did you contact the Atlassian Support team to learn what they think about this symptom?

That part looks correct for the filtering by display name values...assuming they exactly match the case of the display names (as they all appear to be lowercase). Have you updated the JQL for your lookup issues action and retested yet? The JQL suggestion I offered should work standalone if you want to test that first from…

Hi @Madar, Andrew 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.…

Sorry if I caused confusion with so many edits to my post! For the Lookup Issues JQL, select the issues you need, filtered by your assignees. That can only filter by display name or account id values. For your user display names, that might be this: project = "IT Service Desk" AND assignee IN ("cyepez", "mwing", "slien",…

Certainly: adjust your JQL to limit the assignees: project = myProject AND assignee IN ("User 1", "User 2", "User 3", "User 4", "User 5") ...and the rest of your JQL I just saw your additional question about email; to match on that change to this, substituting in Bob's actual email address:…

Hi @Bobby Williams I do not have an answer why those reports are not present for team-managed projects (TMP). My hypothesis is the target audience of TMP was believed to use fewer Jira features...with a suggestion to switch to a company-managed project (CMP) when more was needed. Here is a feature suggestion to add them…

Hi @Christopher Yepez -- Welcome to the Atlassian Community! Adding to John's suggestions: After you add the missing Lookup Issues action, you want your email to list the issues for two different assignees. One way to do that is with list filtering, adding a section for each help desk technician. For example: Alice's…

Thank you for clarifying with those images! Those appear to be from the built-in, time-based estimation and not the addon. And...you appear to be on the Free license level. Some of those documentation pages you reviewed are for the Advanced Roadmaps feature, which is for Jira Premium, and above, licenses. It is not part of…

Please check with your site admin as it seems the plugin is disabled.