Bill Sheboy Expert

Hi @John Funk Thanks for your article, and... For readers trying use Lookup Issues with a custom field this way, it will only work with Jira Cloud at this time. For Jira Data Center, the Lookup Issues action only supports a limited number of fields. Here is a suggestion to add more fields to…

Hi @Atlassian User The rule's scope and in which project the issues exist determine if / when a rule will trigger with Issue Linked. That is, when the rule is defined in one project as single-project scope and issues in other projects are linked, the rule will not be able to access the other issues. Are your issues all in…

Hi @llewis -- Welcome to the Atlassian Community! When you have multiple "teams" using one Sprint / Scrum board, you actually have one large team and not individual ones. Merging them this way prevents teams from making individual improvements (such as to their team practices and workflow), tracking progress, planning,…

Hi @Shardul Bhisikar -- Welcome to the Atlassian Community! The field may be set using automation rules, formatting the Date Reported field using the date / time functions to get the short text field. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- The keys for your…

Hi @Youssef fawzi -- Welcome to the Atlassian Community! What behaviors does your company want to foster in people, and why those behaviors? I recommend starting with those things, communicating them to people, provide timely feedback to progress toward the behaviors, and collaborating to adjust as conditions at the…

For the rule you show, you do not want the Scheduled Trigger to use the option to "Process all issues produced by this trigger in bulk", so disable that option. You want the rule to process each Epic found, lookup their children, and then perform the update. Using the "bulk" option will prevent that from happening. Two…

Hi @Andrei Alexandru Hoszu -- Welcome to the Atlassian Community! Regarding submitting a support ticket...Are you on a Jira Free License? If so, you cannot submit support requests to Atlassian and the community posts are the only option for…

Hi @_Bbckhd52bb_ -- Welcome to the Atlassian Community! Adding to the suggestions from @Florian Bonniec ... I recommend not having the field "Story Point Remaining" or even splitting the stories at the end of the sprints. Using those practices may cause unintended consequences, where the team does not learn "why did work…

Hi @Sunil Mistry -- Welcome to the Atlassian Community! What do you mean by "not working at all"? What are you observing? Are you trying to do this: for a JPD Idea workflow, added a transition validator rule which checks for a value in the field...and that is not preventing the transition? Kind regards, Bill

I am certain that rule may have problems with collisions in the future, and strongly suggest changing it. The log may not show errors; instead some component values will either not save or will be "walked over" during later saves. To learn more about such branch behavior, please see this note in the…

For your scenario, the Lookup Issues action is no longer needed and instead the {{issues}} smart value is used. In the linked documentation I provided, it shows an example rule which exactly matches your case:…

Hi @Mike Buma and @Trudy P Claspill This feature of highlighting the Due Date in the backlog / list views: * was originally only present in Jira Work Management (JWM) projects, * was then added to Team-managed projects (TMP), and * has been intermittently appearing / disappearing for Company-managed ones (CMP). I recall…

Hi @Gilad Waldman If you want to run this for each Epic, please consider: * the Scheduled Trigger should supply only Epics to the rule with its JQL * the JQL of the Lookup Issues action could add the trigger issue's key to limit the scope of returned children by adding this to the end AND parent={{issue.key}} Kind regards,…

Thank you for the additional information, as that confirms the expression used to set the date is incorrect. Please see the linked documentation I provided to correctly perform the math and then increment the date value: * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ *…

Hi @A_ Boehme _Communardo_ First thing: for the piece of the rule you show, there is an Edit on the Components field and then they are apparently updated again later, but without first using the Re-fetch Issue action. As a result, the later edits may not work as expected. Next, using an advanced branch over the values may…

Yes, I believe that is a known problem / behavior with the built-in Automation for Jira user and JPD projects...the built-in user normally has enough elevated permissions to do anything, but not for always for JPD.

That makes sense as JPD requires the user to have Creator permissions to make most changes. Which user was the actor originally?

Which rule does not trigger as you have posted several images? Please post an image showing the audit log details for that rule. What is the type of field you are changing? How are you changing the field: entering a value manually, or some other method? Please post an image of an example issue with these fields.

Hi @Bar Azgad Do you want to update the Software Project issues which are linked to Jira Product Discovery (JPD) Idea issue as "delivery tickets": GIVEN a JPD Idea exists AND it has linked delivery tickets in a Software Project WHEN the Customers field changes in the JPD Idea THEN update the linked delivery tickets to have…

Hi @Pedro Celdrán -- Welcome to the Atlassian Community! Adding to the other suggestions... The automation usage limits by products, license types, and number of customers may be found here: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits That is only one of the…

Hi @Lindsey Dobson -- Welcome to the Atlassian Community! First thing, you may want to use Lookup Tables to perform the translation of values to numbers. That will make your expression much simpler, such as creating a table for each translation and then summing without conditions. Please look here to learn…

Hi @Igor Fernandes -- Welcome to the Atlassian Community! You are describing a very specific scenario. What have you tried thus far to solve this need? If you have an automation rule that is not working as expected, please post images of the complete rule and the audit log details, and explain what is not working as…

Please post images of the condition, and your current complete rule. As Marc notes, the smart values are case-sensitive, and the values you posted do not seem to match the rule's Create Variable actions in the rule image. The correct ones would likely be: * smart value condition:* first value:…

Hi @Tyagi, Abhilasha Yes, and...to Marc's suggestions: When using rule conditions to compare dates / times, I recommend using a known and defined format, such as jiraDate: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- You could add date formatting to the smart values in…

If you want to try the REST API approach, here are some references to help set that up: How-to article for calling using the Send Web Request action: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 REST API endpoint to search for issues with JQL:…

The rule you are showing is in Jira Data Center, not Cloud. This is indicated by the icons in the rule editor and that the audit log shows side-by-side with the rule. Please see my first post about the limitations of the Lookup Issues action for the Data Center version and workarounds. As you are only sending an email with…

Awesome; I am glad to learn that helped! Thanks for following up as this will help others reviewing this thread in the future confirm the behavior.

@Rita Arellano -- I am puzzled what you are describing...I thought you had two scenarios (although, actually there are more): #1) GIVEN an issue with an Epic parent WHEN the issue's Story Points field changes THEN update the Epic parent to sum the Story Points for all child issues to set the Size Estimate field #2) GIVEN…

Hi @Vasu -- Welcome to the Atlassian Community! As this is an older thread, I recommend creating a new question, perhaps including a link back to this one, to ensure the maximum number of people see it to offer suggestions. Until we see your new question... Are your issues in multiple projects? If so, the rule scope is…

If you selected to move them, and they did not move, and both projects (source and destination) are team-managed, this seems like a defect. I checked and did not see an open defect for this in the public backlog, so if you did observe this symptom I suggest working with your Jira Site Admin to submit a defect…