Bill Sheboy Expert

Hi @William Tanner Please check your Create Issue action in the rule to see if you selected both the field from the dropdown list and tried to set it with JSON. That can cause that symptom as only one may be used at a time. If that is not the cause, please post images of your complete automation rule, the Create Issue…

That is interesting...I tried both: released: false and true. As long has you have it working now, that is great!

I just tried using Postman and the version create was correctly detected to trigger a rule, so it does not seem to an active problem / incident. Perhaps try the same thing as that would eliminate an issue with your call.

Please this article on a dynamically looping rule using an incoming webhook trigger for an example of passing and consuming custom data: https://community.atlassian.com/t5/Jira-Service-Management-articles/How-to-create-dynamic-looping-in-Automation-for-Jira/ba-p/2293077

Hi Annie@DevSamurai As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Maggie Tokarzewska -- Welcome to the Atlassian Community! First thing, I am not currently using ScriptRunner and so my suggestions will focus on your Jira Automation rule shown. You note there are challenges with your solutions, but you do not describe what they are. What is not working as you expect with your rule?…

Hi @Harvinder kaur As others have posted, this symptom is an unfortunate consequence of the design choices for team-managed projects. Here is one of the many suggestions (i.e., defects) for that symptom: https://jira.atlassian.com/browse/JRACLOUD-72282 A couple of workarounds for this both have "costs": * cost: more money…

Hi @Tibi Ionescu -- Welcome to the Atlassian Community! A Jira board is a view of issues in a project based on a saved filter. You describe having two boards, and so it is likely the saved filters are different for each board. For example: project = myProject AND labels = A-Label ORDER BY Rank ASC project = myProject AND…

Hi @Ismaeil Ghouneim -- Welcome to the Atlassian Community! To confirm, is this the Jira REST API endpoint you are using: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-post Did you confirm the version was created successfully in the project? Is your…

Hi @Hemant Srivastava -- Welcome to the Atlassian Community! Yes, your Jira Site Admin could configure an incoming email handler. Please look here to learn more: https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/ Kind regards, Bill

Hi @Shmuel, Dave -- Welcome to the Atlassian Community! You may need additional automation rules if you want to handle other possible scenarios / edge cases. For example: * What should happen if someone manually changes the Related Product field in a Task or Epic? * What should happen if the parent Epic of a Task changes?…

Ping...Have there been any conversations about improving / reducing / eliminating the very large banner? Thanks!

To add the watchers for the mentions, an example rule could be: * trigger: comment added * smart value condition:* first value: {{issue.comment.last.body.split(" ").match("\[~accountid:(.*)\]")}} * condition: does not equal * second value: leave this empty * action: add watchers, using this smart value expression…

Hi @Rob Brooks -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this notification on issue transition? That is, "why do this?" Knowing that may help the community to offer other suggestions. Until we know that... Although it is possible to scan all the comments to identify the mentioned…

Hi @Grant Mitchell -- Welcome to the Atlassian Community! The solution you describe would not find all sprint, scope change issues: it would only find the ones created after the start of the sprint. If one from the backlog was added, it would not appear. One solution for this is to use an automation rule and an indicator…

Hi @Wojciech Wardaszko In the rule Trudy suggested, the clause of issue != {{issue.key}} is in the branch's JQL, and so will work as expected. At that point in the rule, {{issue}} and {{triggerIssue}} refer to the same thing, and so the branch will work to exclude the trigger issue. Context is important for automation…

Yes, but not from that List View as I do not believe it is possible to do that. If you use JQL directly from the menu item Filters > View All Issues you may use that syntax with NOT IN.

Hi @Arnold Schoenfeld -- Welcome to the Atlassian Community! I recommend discussing this question with your team's agile coach / scrum master to learn how your organization does this. If your teams use some defined methodology, that may already have guidance on the flow from ideation to delivery for the portfolio items. If…

Hi @Ward Schwillens_ Schwillie What problem are you solving by creating those "dummy" tasks? That is, "why do this?" Knowing that may help the community to offer better suggestions. Until we know that... Any mistakes in such looping rules can have consequences. For example... * a simple rule mistake could halt all rule…

With Jira Cloud, (I believe) the issuelinks smart value could be parsed with smart value, list filtering to get the needed ones in one step. But that smart value does not exist yet for Data Center's version of Lookup Issues. The dynamic JQL should work for both Jira versions.

Yes, and...I neglected to add the dynamic JQL in that prior question's response, so I added it this time :^)

Hi @Tyler Monroe -- Welcome to the Atlassian Community! Which version of Jira are you using: Cloud, Server, or Data Center? The different versions have different automation capabilities, so knowing the version will help to focus any suggestions. For now, I will assume Jira Cloud or Data Center... First, your rule will need…

Hi @Reb Bravo and @Vikrant Yadav I do not have experience with the legacy automation and so have no suggestions for that feature. Earlier in this thread, I note there was a challenge with accessing the linked issue status when it was in another project. To do that, the rule will need to be multiple-project or global in…

Thank you for that image, as it shows you are using a Jira Work Management (JWM) project, and that is on the List view, selecting the Filter options at the top-right. To filter by the other status values, please scroll down in that filter list and you will find the Status fields. Then select only the ones you want to see.

Hi @Maurice Stassen The example you show will correctly set the variable, and then it can usually be referenced later in the rule as: {{AccountIDToCheck}} Please note I added "usually be referenced"...Some rule syntax cannot use variables, or it is challenging to do so. This is why I asked to see your entire automation…

I do not, as I am just another Jira user with no special access / information :^) My recommendation would be to read the weekly blog updates for upcoming changes: https://confluence.atlassian.com/cloud/blog And, to add watches in the community articles for Jira updates, perhaps on keywords like "team-managed".

From what you describe, there may be an error on your project dashboard display or in the measure / algorithm used to determine your value. You note "Predictability would be > 100% if PBI is overestimated". That seems like a potential problem. For example, if people are measured (or rewarded) based on improved…

Yes, and... Sometimes scrum teams leave buffer capacity to help with both uncertainty and emergent opportunities. Teams may also have production support responsibilities, and that could generate unplanned work. There are several ways to handle these sources / impacts to work, including using a buffer and ensuring there is…

Hi @Shelli Kleman Perhaps try this one, which adds the grouping and wildcards to the regular expression, and then checks if the result is non-empty: {{#if(issue.summary.match(".*(lightning).*").isNotEmpty)}}:zap:{{/}} As needed, please adjust the regular expression if you do not want to return the search text embedded in…

Hi @Anth.Burnikell What version of Jira are you using: Jira Cloud, Server, or Data Center? For Jira Cloud, I confirmed this works: * when you use the Clone Issue action * select the Attachment field from the dropdown list * select Copy Attachment from Trigger Issue in the options Kind regards, Bill