Bill Sheboy Expert

Hi @Heather Ronnebeck Short answer: the rule will need to use the REST API endpoint (with the Send Web Request action) to find the version to add, filtering by the name prefix and the status, and then add it using JSON. Kind regards, Bill

Hi @Nur Fatin Do you expect both fields to always contain selected values? If so, you may merge them, remove duplicates, and use that in the email address; no branching is required. For example, if these are global, company-managed multiple-select user fields:…

Greetings, community! After no responses to my above question about what Page Content information will work with the new action, I experimented and observed the following: * the field accepts plain text * the field accepts bullet / list markup, such as with * a bullet here * table markup does not work; for example:…

Hi @Gary Spross My understanding about that special, custom field type is it only displays in the work item (formerly called "issue") search results, but not on any other view types. That is likely because it is dynamically populated from the change history. Here are the suggestions to allow adding it to Jira and…

Please post images of the version of the rule where you use the Branch on JQL and the audit log details showing the rule execution. Those may help to explain why it did not work. Thanks!

Hi, community! Should problems in the community site, groups, notifications, etc. appear as incidents or outages on the support tracking: https://support.status.atlassian.com/ There is an area for "Community" and I do not recall ever seeing a problem noted there. Thanks! Update 2025-04-28 1050 PT: for the last few days, I…

Hi @Pravin.Gumgaonkar Adding to John's suggestions... Moving work items (formerly called "issues") from one project or type to another can be challenging due to differences in types, fields, workflows, etc. This is why Jira has a dedicated UX feature to help: Move. The move can interact with a person, asking clarifying…

Hi @Vera Valshonok What problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer better suggestions. Until we know that... Moving work items (formerly called "issues") from one project to another can be challenging due to differences in types, fields, workflows, etc. This is why…

Hi @jodywhite The description of that endpoint seems to indicate it only applies for Scrum boards, and not for Kanban ones: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-backlog-get As a workaround, you could either hardcode the board's filter / column…

Hi @K Rahul There is nothing built-in to help with such counting as JQL is not a SQL, such as with features to help count things. For workarounds... You could investigate marketplace addons / gadgets for dynamic counting fields or display of rollup counts. Another approach is using automation rules, as you noted. This…

Hi @Rostum Tampor -- Welcome to the Atlassian Community! I have not tried this with the mobile app, and... Have you tested using a mention to the user on the issue from the rule to see if they get the notification? Kind regards, Bill

Hi community managers / champions, Please move this product marketing content from the vendor to the App Central group: https://community.atlassian.com/forums/App-Central/gh-p/app-central Hi @Ala _Wisary_ Please review the community guidelines for vendors / partners regarding marketing content and the guidelines for…

Hi @Lalith Motay Context is important to help resolve automation-related questions. Please provide the following so the community can better understand your rule: * an image of the complete rule, in a single image for continuity * an image of the rule action where you are adding / creating the issue * an image of the audit…

Hi @Mahdi Alikhani -- Welcome to the Atlassian Community! Is the issue to which you want to add the comment the IT-69 one (from the webhook data)? If so, please replace your Lookup Issues action with a branch using the same JQL as from the lookup, moving your Add Comment to Issue action inside the branch. That will make…

Hi @Danny Have you tried using AQL to branch to the object(s) and then using the Edit Object action to make the changes? Kind regards, Bill

Well done solving this, particularly the part of using the Send Web Request action to trigger the manual rule! I recommend monitoring that one to ensure it does not trip the 10 loop limit due to repeated calls from the Scheduled Trigger rule. Regarding open suggestions and defects, you may search the public backlog for…

Hi @Omkar Rajale First, it seems unusual to me having over 100 child issues for a single Epic. I recommend pausing to understand why there are so many child issues to identify if there is another structure that would help: multiple Epics, add a level to the hierarchy, evaluate how Epics are used, etc. Next, adding to…

Yup, it is a list of values. Please try adding the .first to get the value.

Yes, I would also expect the results to be the same (when the same form instance is selected, regardless of trigger). Let's try figuring out what is in that field... In your current rule, and near where you are logging that value which is bracketed, add two more writes to the log: field size assuming a list value:…

Hi @Bonnie Barron There was an active incident today where the Sprint field was not displaying correctly, and it has since been resolved: https://jira-software.status.atlassian.com/incidents/twcldb43nbzd Is the issue still happening for you? If so, I recommend working with your Site Admin to submit a defect to Atlassian…

Interesting...I just did a quick test and did get AFTER to work with hours, such as: project = ABC AND status CHANGED TO "In Progress" AFTER -24h This was for a clean, Jira Cloud, Free License site which was never converted (i.e., such as from Server or Data Center). Perhaps try that version, adjusting the hours value to…

Hi @Jared Bessette-Kirton -- Welcome to the Atlassian Community! What do you mean by "Text after is left off"? Do you mean the " - B" after the {{issue.summary}} is not in the new, cloned issue? Also, is what you are showing the entire rule, or are there more steps in it? Kind regards, Bill

Hi @Samuel James There are two design problems with your rule: it is branching over all of the linked issues (potentially adding several issues), and the JQL used in the Lookup Issues action does not account for the link type. For a scenario like this, I recommend first writing the JQL you would use to identify that…

Hi @Melbrin NGOUILOU When posting bot / AI-generated content, ensure you disclose the source in your post text. For more information, please carefully review the community guidelines: https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @Samuel James You are using Jira Data Center, and with that version only a limited number of fields are supported with the Lookup Issues action. (There is an open suggestion to improve that.) There are two possible workarounds, but for your case you want to update another field with the sum, and thus the REST API must…

Hi @Marc -Devoteam- Well done! FYI -- There is a small typo in your step 3.2. where the "j" is missing from "jira". https://<Cloud site URL>/rest/api/jira-metadata/1.0/metadata?pageId={{pageid}} Kind regards, Bill

Hi @Christoph Schötz Short answer: I do not believe your scenario can be solved with automation rules, although it might be possible using the REST API endpoints and called from a custom application with better looping options. You may want to investigate if there are marketplace apps to help manage / query pages this way.…

Hi @Piyush Annadate _ACE Pune_ When posting bot / AI-generated content, ensure you disclose the source in your post text. For more information, please carefully review the community guidelines: https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @gabriel_moraes Within Jira Product Discovery (JPD) have you tried creating a board view with columns based on Status? https://support.atlassian.com/jira-product-discovery/docs/create-a-board-view/ Kind regards, Bill

Please see my earlier post above ^^^ * remove the JQL condition you have * and instead use the Branch rule / related issues* select the type as JQL * use the JQL you currently have in that condition * disable the option to "Only include work items that have changed since the last time this rule executed" * ensure the…