Bill Sheboy Expert

Hi @Katherine Lisman As an FYI for your rule with a scheduled trigger on JQL, automation rules can only process up to 100 issues per execution. You noted that when you ran/tested the JQL it returned 119 issues. Something to watch for in the future as such a rule could take a few executions to complete all the work,…

Hi @Ankit Nangia If you are generating and assigning issues with the automation, you should be able to send an email using the smart value {[createdIssues}} as the source data for the email text. If you want to report later, please use a saved filter, and a dashboard with the two-dimensional filter statistics gadget: *…

Hi @Niharika Verma -- Welcome to the Atlassian Community! There is nothing built-in which can do what you request. And a Jira sprint report is for one board for one sprint; it cannot span projects or sprints. Have you looked at the features of the built-in, custom dashboards and their gadgets? You may be able to create a…

Hi @Megha P Atlassian's interpretation of a CFD is pretty basic, and I believe you would need an addon from the marketplace to get what you ask: https://marketplace.atlassian.com/search?hosting=server&query=CFD Best regards, Bill

Hi @Januka Wijesinghe Just to confirm your use case: * When do you show/review information on the dashboard: before the release occurs (during development), or after the release has deployed? * What is the format of your version naming? For example, is it number-based, date-based, alphabetic only, or some combination of…

Josh, what do you mean by "naming convention"? Are you changing the summary (title) of an issue based upon the team working on it? If so, you may want to consider using a field like component or label instead to reflect such a change of teams. Those are less likely to be impacted by typos for changes.

Hi, Roy. To learn if this is in fact a problem, I suggest following your steps, (edit child summary, select parent breadcrumb link), and then selecting the checkmark to save, and see if it indeed updates the parent issue. If so that seems like a problem as perhaps selecting the breadcrumb link should: * abandon the edit…

I just tried your use case, and it worked for me, including both Company-Managed and Team-Managed on one board: * Create a simple filter spanning the projects: project in (ProjA, ProjB) ORDER BY Rank * Save the filter, updating the permissions for your desired visibility/access * Navigate to view all boards:…

Thanks for explaining. How about this work-around: add a custom field like StatusColor, and set it (hard-coded) whenever an issue transitions. Then you can use the color in your HTML table when needed in other rules. __Bill

Ah, that part about company-managed and team-managed projects may explain things. Please take a look at this article to see if it helps create the board: https://community.atlassian.com/t5/Jira-Software-articles/Multiple-boards-in-Business-and-Team-Managed-Projects-You-bet/ba-p/1719761

Hi @Luc Full disclosure, I am using Cloud and not Server version of Jira... What problem are you trying to solve by capturing the color? Or is this more a general question about the level of available dereferences in the smart values within automation? For the symptom you observed, this behavior is a known issue and…

Hi @Matt C_ Wilson Thanks for the info. As a reminder, Create Variable only works for Cloud at this time, not Server, and this question was for Jira Server. And as you noted...the branch's JQL could still work without the created variable by using the trigger's smart value for the sprint. Best regards, Bill

Hi @Chris Byrne Removing them is easy, if you do not mind any gaps in your comments. Please try the replaceAll() function with a regular expression to remove everything surrounded by the brackets. {{#issue.comments}} {{body.replaceAll("(\[.*\])", "")}}{{/}} If you want a placeholder, you may replace the empty "" with…

Hi @Matt Fetting Yes, and...for Trudy's ideas: how often do you need this information? If you are doing this one-time, please consider exporting data from a more general query and then use a spreadsheet to match up, "join" the columns you need to check. If you will need this often, other ways to go are: a marketplace…

Hi, Louis. That is interesting...Let's try to break down what you are seeing into pieces... * Where is your shared board stored: in a stand-alone project, in one of the source projects (e.g. "Project 1", "Project 2", etc.), or in your profile? * The backlog for a project should show everything for that project...except…

Hi @Roy Nijhuis -- Welcome to the Atlassian Community! First thing, when editing a field like that, please select the checkmark to save changes. Alternatively, you may place the cursor anywhere else except on a field and click to save the change. Next, I do not see you showing that the title actually changed of the…

Hi @Jiří Janošek I am not following your use case well.. For automation rule-related questions, it can help to post an image of your rule details and the audit log for the execution. That may provide context for the community to offer suggestions. Thanks! It seems like your scenario is: * WHEN an issue transitions * AND…

Hi @Joshua Buchanan That sounds possible to do with Automation for Jira rules. You note using multiple boards for the different teams; what is different in the team filters to support the shift from one team to another (e.g. Component = Team1 vs Team2)? Using that information, you could trigger a rule on that field…

My bad, @Jack Brickey as I mis-remembered the issue, which was sprint event-related. I updated my post and added the link. Thanks for keeping me honest. ;^)

Hi @Louis Royster -- Welcome to the Atlassian Community! Have you tried to invert your query, looking only for the issue types you want? For example: project IN ("Project 1", "Project 2") AND issuetype IN (Story, Task, Bug) ORDER BY Rank ASC Best regards, Bill

Hi @Scot Michael Hirschman As a disclaimer, I am not using Insight, so my advice is about checking if the smart values are supported... There are several open suggestions to add more Insight field support (link to Code Barrel backlog). Until more are added, you could use an example issue with your fields and call the REST…

Thanks for the step-by-step, @Jack Brickey Another *possible* limitation/issue of this approach was in a recent community post: sprint event changes from the profile-located board may not trigger automation rules in the source projects. My testing showed this mostly worked for sprint created and completed, so I suggested…

Hi @Januka Wijesinghe Yes, and... to what Jack suggested is to use earliestUnreleasedVersion() in your dashboard filters. https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-earliestUnreleasedVersionearliestUnreleasedVersion-- Best regards, Bill

Hi @Lusca Fontoura Such queries can be tricky to get correct as you will need to determine your date range clauses. Some things to help are: * Draw yourself a timeline on paper, indicating what you care about. For example, -1w, -2w, -3w... * Mark your use cases and ranges on the timeline * The CHANGED operator can check on…

Sorry, I'm just a customer so I don't know that stuff. :^) The support site says a fix has been implemented and that they are investigating the cause. I have not seen the root causes listed on the page often.

Hi @Alexandra Wayne Harper -- Welcome to the Atlassian Community! Several of the questions you have are common to service-oriented work in silo'd orgs (like UI/UX, architecture, dev teams, etc.). This may be regardless of whether the people doing the work are on a stand-alone team like yours or embedded on delivery teams.…

Nope, not yet for Lookup Issues. Here is the suggestion to add it...and...it has moved to the dreaded status of "Future Consideration" ;^) https://jira.atlassian.com/browse/JRACLOUD-75018 As you are using the Cloud version of Jira, the automation has a handy action Create Variable. So...one work-around for this Lookup…

Hi @Divyanshu Verma -- Welcome to the Atlassian Community! There was a problem earlier today with all automation rule execution being delayed, and it appears they have resolved it now: https://status.automationforjira.com/ Are you still seeing the problem/symptom of the rules not firing? Best regards, Bill

Hello @LAKALISKA Nadica -- Welcome to the Atlassian Community! Here is the documentation for creating issues from emails for Jira Server: https://confluence.atlassian.com/adminjiraserver/creating-issues-and-comments-from-email-938847641.html Best regards, Bill

Hi @Gerda Tilk Do you mean no updates at all or just no status changes? If want to check status changes you could use this JQL in your rule, replacing your project and whichever statusCategory values you are interested in checking. project = myProject AND statusCategory IN ("In Progress") AND NOT status CHANGED AFTER -10d…