Bill Sheboy Expert

Thanks, Stefan; I missed that! Unfortunately Lookup Issues and nested branches are not supported yet, so the work-arounds are limited: entity properties and a scheduled rule with bulk-processing that includes a branch to the parent.

Hi @Mela Yes, and...to Sam's answer: The built-in dashboard function has not be updated for many years, and so you would need apps/addon gadgets from the marketplace for some of those visualizations. And the built-in dashboard has very limited format layouts (1, 2, or 3 columns) and so also consider marketplace apps which…

Hi @Meet Lalpurwala -- Welcome to the Atlassian Community! Although there are old, internal REST API functions to get some of the sprint reports, those could be removed at any time and so should not be relied upon. Instead, consider using the supported REST API functions or automation rules (with sprint triggers) to gather…

Hi @Mohit Goel -- Welcome to the Atlassian Community. By "capacity" do you mean the available work capacity for a team during a given sprint? If so, you are correct that Jira has no built-in features for capacity analysis for teams. When this is needed, consider performing this analysis outside of Jira during sprint…

Thanks, and that appears to restate what you have already noted. What problem does that help you solve? For example, does this help you know something about the teams with overlapping work between the projects?

Hi @Salim Hammar As your automation rule is different for your case, I suggest you: * create a new question, * include images of your rule and the audit log details, * describe your Jira instance and project type, * describe what you are observing, and * link to this thread to request ideas from the community. Creating a…

If "parent link" is the field linking your issues, try using a Lookup Issues action to gather the sibling issues of the trigger issue with this JQL: "Parent Link" = {{triggerIssue.Parent link"}} You may then sum your field using the lookup results, for example: {{lookupIssues.myCustomFieldName.sum}}

For the first line in that log, it shows "No Actions Performed". Please expand the Show More section on the right side to see that happened during the rule, and post that also. If you were expecting that issue to process, please examine the issue's fields to learn why the conditions were not met.

Hi @Julio Ribeiro -- Welcome to the Atlassian Community! Are you asking about this REST API method: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/issue-getIssueWorklog If so, this method uses pagination, like many of the REST API ones. You would need to use startAt to grab the results, page by…

Hi @Noah Di Gesù -- Welcome to the Atlassian Community! Yes, and...to Jack's answer: The team-managed project's Story Point Estimate field is apparently not fully supported for basic conditions and actions. One work-around is to use the Advanced Compare Condition and check the smart value directly: {{issue.Story point…

Here is a great how-to article for calling a REST API function from an automation rule webrequest: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Hmmm... As a query can find the condition but cannot display it as a field perhaps you could use an automation rule (triggered on the various DevOps triggers or a schedule) to add a label or component, and then report on that value. Use of other DevOps triggers (or another scheduled rule) could be used to update/remove the…

I am also using Jira Cloud. Perhaps it has not rolled out to all servers yet and that is why we are seeing different things. Thanks, Bill

Hello @María Alejandra Londoño Gómez and @Tinker Fadoua I am seeing this behavior also for the backlog view, with two different browsers. This appears to be an intentional update to the UX. Kind regards, Bill

Hi @Amy Christianson Please take a look at this JQL documentation article for how to do that with JQL, and then perhaps you can show the issue information on your page as an issue list: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-developer-status/ Kind regards, Bill

Hi @Anaelle Layrac -- Welcome to the Atlassian Community! Yes, and...to Trudy's answer: another source for example rules is the library: https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20 You cannot download these yet, but you can view them to get ideas for…

Hi @Paul Dokken What is the problem you are trying to solve by doing this? Couldn't you just reference the Summary field later rather than duplicating the information...or...are you expecting the two fields will be updated independently later? Thanks! Kind regards, Bill

Hi @Paul Dokken Do you mean when the pull request is merged? If so, there is a trigger for that event: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Pull-request-merged Kind regards, Bill

Hi @Dipu Krishnan -- Welcome to the Atlassian Community! That is not possible with out-of-the-box features of Jira. If you specifically need that feature, please investigate the Atlassian Marketplace for addon gadgets to help. And also, if you describe the problem you are trying to solve, perhaps the community can suggest…

Hi @aisrinivasan -- Welcome to the Atlassian Community! This seems to be a duplicate of another question you have asked here: https://community.atlassian.com/t5/Jira-questions/How-to-create-bugs-automatically-in-JIRA-when-a-testcase-fails/qaq-p/1996795 If that is the case, please consider closing one of the questions to…

Hi @Yash Raj You noted that you already have an automation rule. Please post images of your automation rule and the audit log details. This will provide context for the community to offer suggestions. Thanks! Next, you note wanting to assign date fields based upon changes to date fields in dependent subtasks. * When do you…

Hi @Chuck Cox I have seen several suggestions to add WAS IN for other fields in the public backlog, but nothing for custom fields. My recommendation would be to check the marketplace for JQL enhancements to make queries operate more like SQL, and then contact the vendor to ask if they support this specific capability. Kind…

Hi @John Ricard Jumping in to try to help with the concern you note about execution limits, etc. I recommend pausing to consider the problem you are trying to solve and if there are other ways to solve it. As you are triggering on status transitions AND later transitioning other issues in the rule, looping can…

No problem, Chris...and...I recommend creating a new question and linking back to this thread for context. That will ensure the most number of community members see the new thread to offer insights and see solutions. Thanks!

Another idea, @Joseph Ssebagala If getting a JQL addon isn't possible, you can also try this with an Automation for Jira rule. If you are interested in trying that we can start another thread in this post to keep the solution approaches separate for future readers. And...you may take a look at this documentation to see if…

Hi @Hendrix_ Jonathan -- Welcome to the Atlassian Community! I just recreated that symptom: tried an import with Assignee from an email address and it worked correctly for me with Jira Cloud, and failed on a user custom field with the error the user does not exist. I do not see an open defect for this in the public backlog…

Hi @Gail Yes, and...to Trudy's answer: To do what you asked, you would need a rule that triggered on an issue transition AND checked JQL to only trigger once; that does not exist. Trudy's idea on checking for any non-done issues with a lookup issues seems like a great approach, although it will trigger any time an issue…

Hi @Rania -- Welcome to the Atlassian Community! To answer this question, I suggest having a conversation with your site admin about the vendor tool you are using to manage tests and if you have any marketplace addons for JQL. With that information you could investigate the test vendor's documentation to learn if this is…

Hi @Derek Bowes You cannot perform a nested query like that with out-of-the-box JQL. It is not a SQL and so doesn't have that feature. If you need to do this type of query often please investigate one of the marketplace addon apps to enhance the features of JQL. If you need to do this one time, you could first query to…

Hi @Heather Ronnebeck I recall that lastCommentedDate comes from the ScriptRunner addon and is not a built-in thing for JQL. Kind regards, Bill