Bill Sheboy Expert

Hi @Sujala What problem are you trying to solve by doing this? That is, "why do this"? User stories are often considered the smallest piece of valuable work that can be released to production. Subtasks are often considered a piece of work to complete something, like a user story. They are not typically individually…

I wondered about that but thought it would have errored-out with other symptoms. You can quickly test this by identifying and using the account id value instead of the user name in the query.

If you tried the "find your smart value" how-to and did not see your field, then it is not supported by automation rules (because it is not supported by the REST API for issues). However...I just tried that how-to technique for our JPD project and found all of the fields we added, including the dates. Looking at the JSON…

Your scenario will determine which rules you need. Specifically, * how often do you need this field to be accurate for the child issues: always or periodically (such as daily)?* When you need the field updated "at all times", you need several rules to keep things in sync. When you need a periodic update, a single scheduled…

For a sprint on a Jira board, the last column is "done". When there are other boards in the same project, their respective board layout determines doneness. These are aspects of the Jira tool, regardless of how a team defines its processes. Was the issue in the last column on the board when the sprint completed?

I was suggesting to conceal the URL and security information in your screen image, not to completely remove it. You appear to want to change the options for a select list, custom field. If that is correct, please look here for the REST API methods which apply:…

Hi @Ben Krichko Are you asking how to write a JQL for the project, comparing the "Project Management Capacity" to 10? Or, are you asking about creating a view in JPD which filters based on that same field and value? Kind regards, Bill

Hi @V N Raju Raju First thing, I recommend removing that image and replacing it to obscure your URL and authentication information. Perhaps also select the Hidden option for your header data. Next, please describe what is not working as you expect? Kind regards, Bill

Hi @Kevin Lioenel Branches that could be on more than one thing run asynchronously and in parallel, so you cannot append values in a loop in this way. In fact, there is no guarantee that such branches will complete up to the last step in the rule...so you cannot use actions/impacts inside the branch loops for steps after…

Hi @Kevin Lioenel This seems to be a duplicate of your other post, so please close this one and look at the other for suggestions. Thanks! https://community.atlassian.com/t5/Jira-Software-questions/Automation-For-Each-Append-Value-to-the-Field/qaq-p/2431942 Kind regards, Bill

Hi @Jeff Moy -- Welcome to the Atlassian Community! Smart values are name, spacing, and case-sensitive. I wonder if the issue is the name for the smart value is {{lookupIssues}} so perhaps try this: :ship: Release *{{webhookData.releaseName}}* is ready to ship: :ticket: Tickets: {{#lookupIssues}} - <{{url}}|{{key}}>:…

Hi @Kapil Vashishat -- Welcome to the Atlassian Community! Would you please clarify your question? Are you... * writing an app which is calling the Jira REST API to make changes, * calling a REST API from an automation rule, * triggering a rule from a webhook, * or something else? Kind regards, Bill

Hi @Dave Furlani My suggestion on this unique use case would be: divide and conquer. Pick one of those measures, and once it works, the methods you develop may help to solve the others. For example, if you take your count of sprints by team...(Disclaimer: I am describing this and not writing this based on creating a test…

There are quite a few statements and ideas in this post. One wonders how the post might be improved with some references to original source materials.

Hi @Frank Would you please clarify your question? Subtasks always have a parent issue (a Story, Task, or Bug). Yet you seem to be noting that issues with no subtasks are selectable, and at the same time that issues with subtasks are sometimes selectable and sometimes not selectable. Based on the screen image shown, you…

Hi @Roman Witt -- Welcome to the Atlassian Community! The issue history (changelog) is stored with each issue. When you want to see that, please view the issue and you will find History in the Activity section. This information is not a separate report at the project level. Please look here to learn more about issue…

Hi @Jim Smith For a question like this, please post images of your complete automation rule and the audit log details showing the rule execution. Those will provide context for the symptom you are seeing. Thanks! Until we see those... You describe trying to use JSON to edit the field. Have you tried to select the field…

Hi @Tuyen Vetter When you are on a paid Jira license, your site admin can submit a support ticket at that URL. Please work with them to create the ticket. Kind regards, Bill

Yes: you may use advanced branching for that, as described below and in my earlier post: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 Basically you name a branch variable and supply a source, such as a list, split/delimited text, or collection of issues.…

Hi @Lindsay Cloudy -- Welcome to the Atlassian Community! Here are some follow-up questions to help narrow down on solution approaches: * What problem is your audience solving by having this report? * What do you mean by "2-week look ahead report"? For example, would this be a list of issues which have some due / want date…

Hi @Nuno Pimenta (ADM) Even though you have an answer using a CRON expression, I recommend submitting a defect to Atlassian Support for what you have found. As the site admin on a paid, Jira license you can do that here: https://support.atlassian.com/contact/#/ I see the same thing and that value "A date" is not…

Indeed! This question reminded me I had solved this last year, could not find my test rule, and so had to re-create / re-learn the method :^)

Hi @Trudy P Claspill It is possible to gather up the issues and their subtasks in one query with a rule...but it is often not practical because of the automation processing limits. For example, the 100 issue limit for Lookup Issues and the execution time limit (depending on what needs to be done). Let's assume we know…

Hi @Dmitriy Gatsura You seem to be asking: How can I add summary values to a swim lane heading on a Jira board? For example, the total of estimate for the issues in the swim lane. If that is your question, there is no way to do that with the built-in features. There have been several suggestions to add that feature, and…

Hi @Zuhaib -- Welcome to the Atlassian Community! That would be possible using an automation for Jira rule, however... What problem are you trying to solve by doing this? Knowing that may help the community to offer you additional ideas. To get you started on creating your rule, please review this documentation and…

Hi @최종운_Jongun Choi_ -- Welcome to the Atlassian Community! Adding to John's answer: Did you want to do this from the "Start Date" or from the "Created" date for any issues? Is the "Start Date" always filled in for your issues? Kind regards, Bill

Hi @Sherin -- Welcome to the Atlassian Community! I wonder if you are running into the known problem that the number of returned issues is expanded into the URL as a CSV list, and that then exceeds the limit. Here are a couple of open suggestions/defects on that, which you can watch/vote for:…

Hi @Shari Fitz-Patrick Adding to the answer from @Prerna Sony What type of project are you using: company-managed or team-managed? You may find this information at the bottom-left side of the page expand area. At this time, only company-managed projects support configuring card information. There is a suggestion to add…

Hi @Marcel Vellage I believe that may only be possible if you have a REST API method which the rule can call to make the changes. If you have such a method to call, here is a how-to article for calling a REST API from an automation rule:…

Hi @David Washburn From what you describe, it seems that REST API call is already returning a list and not an array. One simple way to test that is to try to iterate over it an write to the audit log this: {{#webResponse.body.choices.message.content}}{{.}}{{/}} If it writes the values you expect, you can then try using an…