Bill Sheboy Expert

Hi @Yael Geffen To ask Kian's question another way: How are issues being re-opened from "Done" to another status? Is a person always doing that or does another rule sometimes do it? And showing images of your entire rule and the audit log details showing the rule execution may also explain this symptom. Kind regards, Bill

Hi @Jana Jäger Your rule is very close to what you need...the missing part is a branch on most-recently-created-issue. Please try this adjustment to add the subtasks: * trigger: issue created * action: re-fetch (I always add this after the Issue Created trigger as the rule can run so fast the later conditions may fail.) *…

Hi @Zeynep Ceylan Just a hunch here: have you confirmed those custom field id values are correct? They seem to have one more digit than all of your other custom fields. Kind regards, Bill

From my perspective, JPD is just a team-managed project with a bunch of extra, fancy features :^) When you add a field to a JPD project it is a custom field, and so you should be able to find them with that how-to I suggested. I checked and the fields I added to my JPD project (to test the smart values I gave you) did have…

When using Lookup Issues, try referencing the fields without an issue. prefix, like this: {{#lookupIssues}} {{key}} {{/}} If you prefix as {{issue.key}} inside of the iterator, I would expect the results to be empty, which is what you are seeing. The reason is once inside an iterator, nothing outside that scope (i.e.,…

Hi @Nicolas Courvoisier Would you please post an image of the audit log details showing the rule execution, including one with the error? That may provide some context to understand this symptom. And as the rule appears longer than what you show, could you also post an image of the complete rule, ideally in a single image?…

Hi @Josh -- Welcome to the Atlassian Community! First thing, why do you have story points assigned at a sub-task level? One of the ideas of story points is toward delivering value to production, and one of the ideas of sub-tasks is a piece of work contributing to a larger item, and not be individually releasable. And so…

Hi @Marian Hlaváček -- Welcome to the Atlassian Community! Yes, and...to Clark's answer: How does your team do sprint planning and use people's availability to plan today? An alternative to what you suggest is for the team to pause at the start of planning to quickly identify who is present/not present during the sprint.…

Hi @Sanjivani Wayal Adding to the answer from @Pasam Venkateshwarrao ... You could use Lookup Issues with JQL, checking the issuetype matches what you need. I believe you could also use smart value, list filtering and a math expression on the {{issue.issuelinks}} smart value to count these in one step. Kind regards, Bill

Hi @Casper I believe this is possible with a single rule, and as you note you have tried to create a rule, please: * explain the problem you are trying to solve (i.e., the "why") * post images of your rule, including details of the trigger, conditions, and actions * post an image of the audit log details showing the rule…

Hi @Management Team -- Welcome to the Atlassian Community! You cannot perform a query like that with out-of-the-box JQL. (It is not a SQL, and does not have such features.) Do you have any marketplace addons/apps which extend the features of JQL? If so, one of them may help. If not, and you do not need a query like this…

Hi @john peter -- Welcome to the Atlassian Community! I recommend posting a question like this one in the developer community: https://community.developer.atlassian.com/ And when you do make that post, consider providing more context for your question, as it is possible you already have the displayName attribute and that…

Hi @Saurabh Chaudhary Adding on to Mohammed's answer... You note the "bit not executing" is what you have shared, but the rule you show does not attempt to set the Team field. Have you posted the correct image? Next, there are unfortunately several fields in Jira Cloud named "Team" and many of the fields related to…

I am glad you noticed the watcher field is a list, and so when we referenced {{issue.watchers.emailAddress}} that expanded into a list...even when empty. One work-around is to join that list into a single text string first, like this: {{issue.watchers.emailAddress.join(",")}} Then when the initiator's email address is…

What does not work as you expect? Please be as specific as possible and include example issues/values to clarify. You asked about estimation (time tracking) fields. Why are you editing the Story Point field in one of the rules? Please post images of audit log details showing the rule execution. That will provide context…

I haven't done this with Github, but I wonder if you could use a scheduled rule (or webhook trigger) to call the Github REST API and check on the status of the review, taking actions as needed: https://docs.github.com/en/rest/pulls/reviews?apiVersion=2022-11-28

Could you instead use a filter for your Confluence page's macro, and then adjust the issue fields so it will be found by the search?

I am glad to learn you have something that works. FYI that match() can take a single, created variable as a parameter (at least for the Jira Cloud version of automation). And so when I have a dynamic, regular expression based on other fields, I first build the expression in a created variable and then use that in the…

Hi @stephan_lewis What do you mean by "connected to a project"? If you mean shared with the project, you could use this REST API function and filter by projectId: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-filters/#api-rest-api-3-filter-search-get If you mean the JQL for the filter references the…

Thanks! I see no typos in that one so it is probably the field names. Let's try that how-to to replace the names with the custom field id values.

Audrey, I am having trouble following the thread here. May we please stick with one of these rather than adding new threads? Thank you! Let's start with rule #2: would you please post what you pasted into the edit field for the edit? If it was exactly what I provided then I suspect the smart values I guessed for the fields…

Hi @[deleted] -- Welcome to the Atlassian Community! This appears to be a known symptom and was recently logged. You may vote for/watch it to see progress: https://jira.atlassian.com/browse/JSWCLOUD-25797 Kind regards, Bill

Hi @Ailen Agustina Correa Have you tried using the CHANGED operator with the status field, as described here: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED That would allow to include timeframes in the query. Kind regards, Bill

Hi @Vishal Guleria -- Welcome to the Atlassian Community! Is the reviewer declining the PR? If so, I believe there is a trigger for that event: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Pull-request-declined Kind regards, Bill

Hi @Connor I also checked and that trigger, "Alert Created", does not appear for JSM, JSD, Jira Cloud, or Jira Server/Data Center documentation...at this time. It is possible it existed in a non-prod version long enough for someone to make that screen image. Or it is from a marketplace addon. Recently I also encountered…

Thanks for those images! If you review the error message, it shows the fields are either collapsing to null/empty values, or to the text values from the select-field list. I wondered what JPD might provide for the fields, and... I did some quick experiments and the weight values we enter for a JPD project field are not…

Have you talked to your site admin to learn if any scripting/addons might be doing this?

Hi @Devlend Maul That is an excellent question as there is little current documentation on this gadget. And there are several open/timed-out defects on the accuracy of this gadget: * https://jira.atlassian.com/browse/JRACLOUD-74324 * https://jira.atlassian.com/browse/JRACLOUD-75778 *…

Hi @Robert Ortega When you look at an example issue with this symptom, and check the change history, who/what does it indicate is setting the Due Date field? Looking at that may point you to the cause. Kind regards, Bill

I have never seen that error before! (Although I have seen an error for reaching the maximum number of components in a rule: 65.) Would you please show an image of the error and your rule structure? That may help clarify what is happening. Based on your scenario I did not think you needed variables at all...just the issue…