Bill Sheboy Expert

Hi @Dave Furlani I recall a similar question from two weeks ago about dynamically selecting the project from a manual trigger's user inputs, and that did not work. What was tried was: * using user inputs in the project field, * not selecting the project and using a JSON edit to set the project, and * selecting the current…

Hi @Gary Spross Adding to Stephen's suggestions... You could regularly export all rules from the global admin area as JSON, and with some parsing capture a few rule details for documentation. I recall seeing another community post about doing that, although I have not tried to create such a parser...yet :^) Kind regards,…

Hi @Fabrício Diego Ferreira What problems is your team trying to solve? How does your team work, and how do they interact with other teams? What goals does the organization have? What things are you trying to optimize? (e.g., trade off matrix areas) Measurement supports doing various things, and measuring without context…

Hi @Ronny-André Bendiksen -- Welcome to the Atlassian Community! With the Sprint Completed trigger, only the {{sprint}} smart value and its attributes are provided: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--sprint-- With that, you may use JQL with the Lookup Issues action to…

Hi @Will Portman -- Welcome to the Atlassian Community! You could set the date / time value to the start of the day plus hours (or use with... to set the specific hour), add your business days, etc. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#To-date-with-time-conversion…

Hi @Pierre Ibrahim With the answer from @Kalyan Sattaluri you have a solution for all of the current attachments using {{toString}} from the changelog. It is possible to get the single attachment's details added, as each attachment is added, using a rule triggered on Issue Field Updated for Attachment and quite a few…

Hi @Addison Alexander -- Welcome to the Atlassian Community! Please consider these questions which may help: * Have you reviewed the audit log details and checked the links for the issues processed? * Are all of the linked issues in one Jira project: "Addison Test"? * Have any additional link types with names related to…

Hi @Rajesh Konda Adding to Sebastian's answer... If you read the article provided, there is an open defect that only one link may be added when an issue is created or edited: https://jira.atlassian.com/browse/JRACLOUD-81845 Additionally, there are potential racetrack error problems trying to add / change links too quickly…

Hi, Nils! Please try to stick to one thread when posting; that will help others looking at this question in the future know if there are multiple solution approaches. Thanks! As I suspected, your scheduled trigger contains JQL, and it should not. The rule is processing for each issue found by the trigger. Here is the…

Let's confirm some things: 1) Are you using Jira Cloud, Jira Server, or Jira Data Center? If you are using Jira Server or Data Center, the Lookup Issues action does not support most fields, including custom fields yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 In that case, the workaround is to call the REST API…

Please post an image of the audit log details showing the rule execution.

Let's clarify the scenario as I do not understand the order things are happening for your manual steps versus what you want to automate. Please describe the steps of the scenario, from beginning to end, including... * when versions are created * when issues are created * when should the version be assigned to an issue…

Hi @Mario Quercia Adding to John's answer... Assuming you are setting the users in a multiple-select user, custom field, you could gather the Assignee values from the subtasks and use them to set the parent Task's custom field using JSON, as described here:…

I have not used any like that before so I do not have a recommendation. Perhaps search on "issue history" in the marketplace to find examples that may help, installing trial versions for comparisons.

Hi markus.neuwald@canon.at That information is in the issue history, but it cannot be easily queried for a custom field such as your date field. There are probably marketplace addons which can do this type of reporting: https://marketplace.atlassian.com/ It might also be possible to create an automation rule to read the…

When the issue is the trigger, please reference the field the version is assigned to and then use the smart values. For example, if the version is assigned to the Fix Versions field, it could be this: {{issue.fixVersions.last.name}} to be released on {{issue.fixVersions.last.releaseDate.jiraDate}} Seeing the specifics of…

Hi @Sam Stinton -- Welcome to the Atlassian Community! I do not believe you can use a JQL condition for your test. The expression must be valid JQL, and you are performing a specific comparison for the first condition: comparing a substring of the summary to a defined string. A work-around for this would be to use a smart…

Hi @Suporte JRetail Yes, most of what you ask may be implemented with automation rules, although there may be differences from what you mean. First, issues are normally linked to versions with the Fix Version and / or Affected Versions fields. Versions are specific to one project, and so the versions in your development…

Hi @Rajesh Pinku For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Shubham R That information is in the issue history, but it is difficult to access using automation rules. This is one reason marketplace addons often help with this need. It may be possible to get that date using an automation rule, but first let's check the extent of this need: * Create a JQL query to find the issues…

Hi @Nils Herhaus -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Jar Lady Would you please describe the problem you are trying to solve? That may help the community to offer suggestions, because... In rules, branches cannot be nested and if / else conditions cannot be defined inside of branches. And so the scenario you described may not be possible with a single rule: While…

Hi @Remy -- Welcome to the Atlassian Community! First thing, I am not using JSM and my suggestions are based on what I know about automation rules... To add / remove users with JSON for Jira Cloud, the id value is needed, as described here: *…

Hi @Valeriia_Havrylenko_SaaSJet 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 @Swati Sharma That is not possible with the built-in features of JQL. It could be performed with a marketplace addon to extend the features of JQL, or in several steps, using the results of one query to build the next one manually. You posted this question in the Automation area. Are you trying to perform such a query…

Hi @kshridvipa7878 As this is a very old thread, I recommend creating a new question, and perhaps linking back to this one. That will ensure the maximum number of people see your question to offer ideas. When you create your question, please include specifics for: * the problem you are trying to solve; that is, "why do…

I wonder if some conditions (such as JQL condition) do not work on deleted issues because they actually run against the database's issue data rather than the issue data in the rule. Please try removing the branch on current issue, and then testing the trigger issue smart values directly using the advanced compare condition…

Please try my suggestion to use that how-to article to identify your smart value in your Jira site. Only the users logged into your site will be able to do so.

Hi @raju mandapaka Please try using the substringAfter() and substringBefore() functions, perhaps chained together to get the text you want: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringAfter--String-separator- You could also do this with a regular expression and the match()…

Hi @Ray Balmeo Cagayon -- Welcome to the Atlassian Community! You mention automation, and so I am assuming you mean automation rules. You also note both Task and Subtask issue types: * for subtasks, you could gather and sum the values with {{issue.subtasks.yourField.sum}} * for Tasks, you could use the Lookup Issues action…