Bill Sheboy Expert

Hi @Pathan Zubair Khan First, please try removing the quotation marks from your smart value. If that does not work, please confirm you have the correct smart value/attributes for the field. You can do that with this how-to article: https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/…

Hi @Harin Alex -- Welcome to the Atlassian Community! For a purchased marketplace app like Agile Docs, you may want to check with the vendor's support page for this question. https://marketplace.atlassian.com/apps/1220574/agile-docs-hierarchy-for-jira?hosting=cloud&tab=support Kind regards, Bill

Hi @ST Kambor-Wiesenberg I do not believe there is an option to disable that link. As a work-around, I think you could create an automation rule which removes the link when issues are cloned. Kind regards, Bill

Hi @JM -- Welcome to the Atlassian Community! When you are using math on smart values, it can help to supply a default value with the pipe operator. For your case that could be using zero (0) as: {{#=}}({{fieldChange.to|0}}/3600 - {{fieldChange.from|0}}/3600 + {{issue.original estimate|0}}/3600){{/}} If that does not work…

Hi @Marko Majkic Yes, and...to Ravi's suggestion: if you need this type of query often check for marketplace JQL app addons. If you need this one time, consider exporting the issues from the projects to a spreadsheet and join there. If you need this multiple times for this defined use case/join, and expect the result set…

Hi @nicolaspannetier Your rule is mostly correct, and you do not need any additional marketplace apps to do this. For the Issue Created trigger, there can be timing issues where all data is not available. Please add a Re-fetch action immediately after the trigger to see how that helps. Next for your edit, please change to:…

Hi @david_contreras Yes, and...to Mikael's suggestion: If you want this date to be "only" the first change to the specific status, please add a condition after the trigger to check if the custom field is empty. That will prevent updates to the date when an issue cycles (backwards/forward again) in flow. Kind regards, Bill

For those who have not heard: created variables can now be used as function parameters! This will greatly simplify rules, and open up lots of possibilities for advanced branching. https://jira.atlassian.com/browse/JRACLOUD-75659

Awesome: created variables can now be used as function parameters! This will greatly simplify rules, and open up lots of possibilities for advanced branching. https://jira.atlassian.com/browse/JRACLOUD-75659 Thanks, Atlassian Team!

Hi @Sarika Dalal First thing, I do not have Jira Service Desk, so I will try to help based on what I see in your automation rule. * Is temp_Asset_ID a defined field in that lookup, as it may not be present if it is returning as empty? * For {{lookupObjects.get(1)... I believe this is trying to return the second item in the…

Would you please post images of: * the details of your Scheduled trigger, and * of the audit log for a run where it does not work as you expect? Thanks!

Hi @Evan Nixon Regarding the "update" and "fields" in the JSON, one is a subset of the other: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/#Advancedfieldediting-JSON--What-sthedifferencebetweenupdateandfields And sorry that did not work as you expected. The other work-around I…

First thing, I recommend checking if you have any of the marketplace addon apps for JQL. (Lots of premium license customers seem to do so.) If you have one, check the vendor help to learn how to do the join, or search the community for ideas for the app's usage. Without the addon, you will need to perform the join outside…

Hi @Austin Songer -- Welcome to the Atlassian Community! What have you tried so far? Would you please post an image of your rule? If you have not started, please select your rule trigger and then use the plusBusinessDays() function to do this. For example: * trigger: issue created * action: edit issue, setting the Due Date…

Hi @Mary Irion You cannot see the watcher names in the JQL search with the UX. Two possible work-arounds I know are: * Create your JQL filter, and export all fields. The watchers' Display Name and Account Id will be included in the results. * Create an automation rule to capture and send you the watchers' information,…

Hi @andy_smith You could "hack" the Atlassian interpretation of a Cumulative Flow Diagram (CFD), by refining the settings to only show your backlog status values. Please look here for information about that report: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-cumulative-flow-diagram/ To…

Hi @Sergii Shevchuk You cannot do that in one JQL query with out-of-the-box features. Some alternatives are: * do the query in steps with multiple queries* for the epic, get the child list, and export their keys * for those keys, create a combined query with ORs the results together * export the issues and perform the…

Hi @Clariza Bergeron Short answer: no Some work-arounds to still do this automatically are: * Subscribe to the email yourself, and create an email rule to automatically forward it to the other people * Build an automation rule to create the report, and send the email to them directly * Investigate marketplace apps which…

Hi @[deleted] -- Welcome to the Atlassian Community! Just to confirm... * Do you actually have an issue link type in your instance named "project = DevOps"? * Or, are you assuming that this is somehow performing a join-like operation on the DevOps project? If it is the second one, out-of-the-box JQL cannot perform such a…

Hi @Phillip Bucknell As you have discovered, Lookup Issues does not support that field yet. A work-around with built-in functions for automation for Jira is to: * using a webrequest in your rule, call the Jira Cloud REST API for a JQL search, using the JQL replacing your Lookup Issues call * use text and list functions to…

Hi @Ernie Longmire I do not believe that is possible at this time for Server/Data Center or for Cloud versions. Here is a suggestion to add the feature, which you may watch/vote for to see progress...although it is quite old. https://jira.atlassian.com/browse/JSWSERVER-10241 Kind regards, Bill

Thanks, Cindy! I had not thought of such a use case before: the number of child issues in a particular status correlates to the progress of the parent epic. You can probably modify/copy your existing rule to do what you ask: * action: Lookup Issues action with JQL to find the siblings of a trigger issue (with the same epic…

Hi @Jack Arndt When do you need to know this information, and how stable is your team's sprint contents/scope? If you want this after sprint start and the contents/scope are stable, this could be done with an automation rule and a custom field or entity property. For example using 2 rules: * Triggered on sprint started...*…

Hi @Michelle Salguero -- Welcome to the Atlassian Community! While using a JQL filter search, I do not believe you can display that information with out-of-the-box features. There may be a marketplace app which can do this. As a work-around, if you build your filter and export all fields, you could get all the work logged…

Hi @israel siboni -- Welcome to the Atlassian Community! How often do you need to do this, and what effort/cost are you willing to invest? * One time need, with some effort with no cost:* Export your issues of note to a spreadsheet, use a formula to get the create time, and use a pivot table to analyze * Not one-time and…

Hi @Cindy Chan Yes, and...to Trudy's thoughts: This could be automated, however the only time I have seen a use case like this was when the business problem/need for the Epic was considered "solved" when part of the work was completed. (i.e. 80/20 rule, or Pareto Principle) For such a scenario I would expect the requestor…

Hi @Evan Nixon Please try the accountId value instead of trying to remove by name: {{initiator.accountId}} If the "remove" action does not work, you could also try this the harder way: * Expand the existing field values into a list, and remove the relevant accountId using conditional list filtering, storing as a created…

comments[0] would be the first, not the last comment. Your rule is triggered on issue commented, so to get the last comment's value for that attribute please try: {{issue.comments.last.jsdPublic}} After logging that, if you see no value, but you did see a value in the REST API response, the field may not be supported by…

Hi @Mélanie Liguet I do not know, so I was asking Manoj Kumar what they observed, as I didn't find anything in the documentation. If you are on a paid Jira license, consider asking your site admin to submit a support ticket to Atlassian to learn what they say: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @Sruthi Would you please post an image of your complete rule, as your question is unclear to me? The smart value expression you showed will return true or false, but that has nothing to do with advanced branching, which is a way to iterate over values in a rule, such as from a list. Kind regards, Bill