Bill Sheboy Expert

Hi, @Darryl Lee Yes, and...automation can do quite a lot, and so helps often. Bundled with the REST API and many problems can be solved. There is room to improve and this article shows the team is doing so...We just gotta be patient for some of the requests to be considered as there are lots of great ideas out there.…

I am glad to learn that helped you. Please consider marking this question as answered. That will help others in the community find solutions to similar problems faster. Thanks! __Bill

Hi, and thanks for clarifying! Something is clearly broken/different, as I also confirmed the option is now gone, even though it is shown in the post you reference and there are open defects about its behavior. I suggest asking your site admin to submit a defect to support here: https://support.atlassian.com/contact/#/…

Inside of an automation rule, you can use smart values in JQL. For example, you can branch or do a Lookup Issues on: assignee = {{triggerIssue.assignee}} You cannot test it with "verify" when writing the rule, as the smart value isn't populated yet. Instead you would need to run the rule to confirm your results.

Yup, that 100 limit probably helps manage performance and leads to other issues. One of the reasons I suggested checking on the dashboard is that some of the gadgets do not appear to be constrained by the 100 limit.

Hi @Claire Bilski I am unclear what you mean by "use more than one smart value that equals lookupIssues". You can use the Lookup Issues actions, do what you need, and then use it again with a new query. Unfortunately, Lookup Issues only supports a limited number of issue…

Hi @Alexey First thing: I wonder if you are solving a symptom or a root cause of the problem, which appears to be people are not finishing work before starting more work, leading to higher work in progress (WIP). Solving the symptom using Jira automation may lead to unintended consequences: such as people not assigning…

Hi @Max Boerma I am not Google forms savvy, and so I wonder if the form can send an email once completed. If so, you could have Jira consume the email to create the issues. Best regards, Bill

Hi @Craig Rogers Short answers: no, and yes... No, not out of the box: There are several open suggestions to support add/edit of the other fields for versions from automation: * https://codebarrel.atlassian.net/browse/AUT-1188 * https://codebarrel.atlassian.net/browse/AUT-1335 *…

Hi @[deleted] What problem are you trying to solve? You posted: However, when opening a tab with 'Fix versions' under the Edit issue filed, I cannot find 'next unreleased version' within my project. What do you mean by opening a tab? The earliestUnreleasedVersion() is a function which is available in JQL, and it is also an…

Hi @Gerardo Dalena Those functions you are using from advanced JQL are relative to the current day. They do not float as I believe you are expecting for any day. I do not believe that is possible with out-of-the-box Jira Cloud's JQL. There are marketplace scripting add-ons which could help. For your weekly query,…

Hi @nagisha.vasudev The option you note is for the Server version of Jira, not for Cloud. You are using Cloud, correct? If so, the equivalent feature for Cloud automation is Lookup Issues. For your use case, you would set up a scheduled rule without JQL, and then use Lookup Issues with JQL to process the issues as a batch.…

Hi! Yup, that nesting issue is why I suggested gathering the information first, use if/else on the results, and then branch inside the if/else clauses. The opposite is not supported, as you note. To learn more about created variables, please look here:…

Hi @Raju Mandapaka Adding to what @Mykenna Cepek describes...that works when you are inside the list iterator. To just get the first issue, use {{lookupIssues.first}} Best regards, Bill

Hi, Dave. Short answer is: no. JQL is throttled to return up to 100 issues, and even the REST API requires calling in chunks to get more issues. Possible work-arounds are: * Refine the JQL so it would return less than 100, and use multiple calls. E.g. reporting by project, by create month, by status category, etc. * Or, if…

Hi Igor, and thanks for clarifying your use case. At this time, there does not appear to be a way to access a list of a generic data entity (e.g. Version) which is not associated to an issue. You can get such things as the version list from the REST API, and that can be called from an automation rule. However... Here is…

Hi @Jordan Hauser -- Welcome to the Atlassian Community! For a vendor product-specific question like this, I recommend looking at their documentation and then contacting their support for help. Here's the information for that vendor:…

Hi @Julian Governale Rather than a number field, have you considered using a text field for account number, and remove leading zeroes, when needed...for example with a regular expression? Best regards, Bill

Hi @[deleted] -- Welcome to the Atlassian Community! The challenge with a use case like this is scanning/finding the earliest date. But first: I recommend creating a timeline/notes of what you expect to happen in various cases. That will help when you test your solution. One possible solution approach is using Lookup…

Hi @gmastrandrea -- Welcome to the Atlassian Community! For a question like this, please consider posting an image of your current rule and of the audit log from an execution. That will provide context to the community to offer ideas. Thanks! You probably can do this with related issues conditions, yet I have seen…

Hi @Peter Are you using a team-managed project or a company-managed one? I wonder about this symptom for team-managed projects, where the status values are defined by project, and so can cause issues when the names are the same as for other projects. (Dashboards are a good example of where that causes chaos.) Perhaps a…

Hi @nagisha.vasudev -- Welcome to the Atlassian Community! Or...you could use the steps in this how-to article for finding smart values: https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/ Best regards, Bill

Derek, I like your approach for a one-time (or a few times solution). Kit, if you need a frequent solution and cannot find something in the marketplace, you may want to investigate using webhooks to push out the logs, and report on them in another dashboarding/log parser tool. Or, pull out the data using the REST API. Both…

Hi @Kit Friend What problem are you trying to solve by viewing this information? Knowing that may help the community offer you ideas, or other keywords to search for in the marketplace, for solutions. Thanks! Best regards, Bill

Hi @Patty Banks What type of field is customfield_13536: is it a user field or just a plain text field? If it is a user field, please try something like shown on this documentation page: { "fields": { "customfield_13536": { "id": "{{issue.assignee.accountId}}" } }} Best regards, Bill

Hi @Natalia Trofimov Are you using a team-managed project, and is that custom field defined for the project? If so, I wonder if you could be seeing this defect: https://jira.atlassian.com/browse/JRACLOUD-76536 If not, perhaps it is this one related to this field type's…

Hi @David Wood Smart values are case-sensitive, so perhaps try {{lookupIssues.size|0}} Please note that I added null handling so this will always return a number. Best regards, Bill

Hi @Joelle Güfel Did you note that @Simon Laffont added quotation marks around the value on the right side? Did you try that format after removing the asJsonStringArray value? Best regards, Bill

Hi @eleanor kerman Yes, and...to what was already suggested: You may be reaching your limit on global rule executions, or have a project-scope rule that is running too frequently/consuming too many resources. Please consider discussing with your site admin to set up a monitoring rule that will email people earlier when…

Hi @michal_kabat -- Welcome to the Atlassian Community! What problem are you trying to solve? Each issue (card) on the board is in a status, mapped to a column. So the status is already noted at the top of the column. Best regards, Bill