Bill Sheboy Expert

Hi @Jorge When the trigger is Work Logged for the child issue and you also want to log that same work to the Epic parent, use this smart value and not the issue's worklog with the Log Work action: {{worklog.timeSpentSeconds}} Kind regards, Bill

Hi @Mari Pervushina You appear to be calling the Jira REST API endpoint for Find Users. Is that correct? https://docs.atlassian.com/software/jira/docs/api/REST/9.13.0/#api/2/user-findUsers If so, please try passing the query parameters on the URL rather than using custom data. This one worked for me with Jira Cloud and I…

Hi @cynthiapaola.murillosalazar -- Welcome to the Atlassian Community! Before changing any issues, I recommend pausing to understand how a Story could be assigned to 21 different sprints, perhaps using an RCA (root cause analysis) or retrospective discussion with the team(s) involved. This symptom may indicate challenges…

I have observed that situation when releasing is independent of building a feature. Some solutions for that are smaller release chunks (to reduce bundling), and / or the use of feature toggles so code can release but not be accessible to customers yet...allowing enabling the component parts of the feature all at once, etc.

Have you tried the community feature to Bookmark posts under the ... menu next to post heading? Bookmarks will store them in a list accessible from your profile avatar at the top-right of the page. That may help when tracking useful smart value expressions to provide context and explanation for them.

Awesome; I am glad to learn that helped! Please consider marking this question as answered to help others with a similar need find solutions faster. Thanks!

Thanks, Trudy! Here is another post where a customer got Atlassian Support to turn them off for their site: https://community.atlassian.com/t5/Jira-questions/How-can-I-turn-off-these-comment-presets/qaq-p/2766137

Hi @StepwithSJ -- Welcome to the Atlassian Community! Based on your statement that your team doesn't close sprints, I recommend pausing and... * meet with your entire team, scrum master / agile coach, and product owner to review fundamentals of methods such as Scrum * discuss the purpose / value of a team measuring…

Hi @Rania Haddadin There are two steps to building a rule like this: * confirm the issue was in the open / active sprint * confirm the issue is no longer in the open / active sprint The first part is required to prevent updating issues which are modified in the backlog, and not in the current sprint. It may be done by…

Hi @Bruce Fint Here is a suggestion to add a configuration option to hide / show the quick comments for issues. You may vote for / watch it to see progress. https://jira.atlassian.com/browse/JSWCLOUD-23563 Kind regards, Bill

Hi @Hayk Tadevosyan You could create an automation rule with a scheduled trigger, gathering issues which do not have your comment yet, and then use the date diff() function to check the number of elapsed business days, such as between {{now}} and…

Hi @Michał Short answer: This is not possible using rules with version date filtering for an iterator. If you explain how your variable PPDdate is defined, the community may offer other approaches, such as using JQL or calling the REST API to gather the versions for examination. For more on why that type of filtering is…

Hi @[deleted] -- Welcome to the Atlassian Community! Please post an image of what you observe for the Velocity Chart. That may provide context to explain this symptom. Until we see that... One reason the "commitment" may be empty for a Sprint with Jira boards is the issues did not have an estimate value until after the…

To help with context, please post an image of the entire rule in one picture and of the entire audit log details showing the rule run in one picture. You can get those into one image using either an app or a browser extension which supports scrolling page image capture. Next, if you view the audit log and compare to the…

Hi @Steve Nguyen Are you just trying to count the issues or do something else with them? If just counting, you could call the REST API issue search with JQL using the Send Web Request action. Even though it will only return up to 100 issues, the total count will be returned in the message. If you are trying other…

Hmmm...okay. I could understand dependency between the fields in this trigger, however... Recently I noticed the first field selected by the UX when a Scheduled Trigger is selected has some latency behaviors. What I observed was, with the latest Chrome browser: * create a new rule * add the scheduled trigger * click on the…

This data works for me for a Company-managed project, importing from the admin function, External System Import:

Thanks for that information, and I am unclear how this could work with automation rules... * Issues such as Story, Task, and Bug can "link" to zero-or-one parent Epic. This leads to a one-directional path of linkage. * Using issue-linking, there is a many-to-many, bi-directional relationship. (Until recently, I believe the…

Sorry I was not more clear, as I am only using the JSON plugin to help check formatting but not the automation syntax. It appears you are getting better highlighting results with VS Code than I was with Notepad++. I have seen others in internet posts describe using other language plugins which support mustache syntax to…

Well done, and two things for your rules: There is a Set Entity Property action which could be used for rule #1 without directly calling the REST API endpoint. Your rules rely upon execution timing for when rule #2 expects things are ready for processing: * If you are using the new Delay action in your rules, I recommend…

Hi @Marlon Tafur_NDO -- Welcome to the Atlassian Community! Customers may only submit tickets to Atlassian Support if they are on a paid license, such as Standard or higher. In that case, your Jira Site Admin may submit a ticket here: https://support.atlassian.com/contact/#/ For Free license users, the Atlassian Community…

Hi @Sura Al-Jailawi Those changes are not possible with the built-in features of the releases page / list. There are several open suggestions to add such features, such as the ones below. You may watch / vote for them to see any progress. One of those is marked as "fixed" but you could use it to recommend additional…

Hi @Inna S How are you calling the Get Project Versions Paginated one: automation rule, external app, something else? https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-project-projectidorkey-version-get Regardless of the approach, the documentation only describes the…

Hi @Brandon Kidd Short answer: do you want one Slack message per Epic? If so, this is possible by branching over the found-parent Epics, and then using Lookup Issues to gather their child issues' data. However, if you want one single message for all of the Epics, I do not believe this can be done with one rule. I…

Date / time comparisons in rules can be challenging, particularly when time zones are involved. I recommend writing the values to the audit log before the comparisons to ensure they are what you expect to help with rule testing. It appears you are comparing values in two different formats: jiraDate and jiraDateTime. Please…

Hi @kalaimani I am unclear if you are asking a question about creating / updating an automation rule or are making statements about what you have already implemented. If you are asking about implementing a rule, please review the date / time functions, particularly for time zone management, to…

Hi @visby8em -- Welcome to the Atlassian Community! That is a known defect, which you may watch / follow to see any progress: https://jira.atlassian.com/browse/JRACLOUD-71136 There are a couple of workarounds listed with the defect. Kind regards, Bill

Hi @Rob Duff -- Welcome to the Atlassian Community! First thing, the Epic Name and Epic Link field are some of the fields that have been sunsetting for company-managed projects since late 2022. Epics will use the Summary and the link in the child issues is Parent. I do not believe that has been updated for external system…

Please show your entire in one image for context. For longer rules, you may capture the image with an app or browser addon to scroll the page. Please also show an image of the audit log details for the rule execution. That will show which rule steps happened, and allow comparison to what you expected.

Hi @Charisse Robison -- Welcome to the Atlassian Community! For a team-managed project, "quick filters" are called "custom filters". And, those filters are based on a JQL filter. They do not allow creating a selection list of checkboxes, as does the Issues view with Basic options. Kind regards, Bill