Bill Sheboy Expert

Good stuff, @Darryl Lee ! Another good pairing of techniques with that newline split is to add regEx and smart value, list filtering. Now...if smart value, list filters also worked with smart value params and smart branches could produce objects...we'd have a lot more options :^) Kind regards, Bill

Short answer, probably not for Jira Server/Data Center... My understanding is Server/Data Center versions' automation rules do not support Lookup Issues or Created Variables yet. The equivalent in Server/Data Center for Lookup Issues is the bulk handling feature of branches and scheduled…

Hi @Craig Brehmer Have you tried the linkedIssues() function: https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-functions-reference-939938746.html#Advancedsearchingfunctionsreference-linkedIssueslinkedIssues() Perhaps like this: key IN linkedIssues(myStoryKey-1234, "is blocked by") Kind regards, Bill

Hi @Liam Cass -- Welcome to the Atlassian Community! A couple of ways to do this (including one you mentioned) are: a dashboard and automation rules. Dashboard (pull approach): Create a dashboard listing/visualizing your different queries and manually send an email (or use an email scheduler/meeting invite) with a link to…

Sounds good. Which addon are you using?

Awesome! I am glad to learn it is working.

First thing, were you trying to use "cloned" as an operator or as the value to set? That is not a valid operator for the built-in JSON updates with automation rules. Let's try the simplest possible JSON first to see if that works for your addon's field: { "fields": { "customfield_11002":…

Are these company-managed or team-managed projects, or one of each? Company-managed projects use shared definitions of status and team-managed projects each have their own definition of status values...even though the names might be the same (e.g. Backlog and Backlog). So multi-project rules impacting team-managed projects…

Hi @Guaraci Nakamura I believe you have 3 options, each with costs/benefits: * Upgrade to a higher license level with more global/multi-project rule executions per month. (Cost: licensing fees, benefit: no rule modification needed) * Copy rules to each relevant project (when possible). (Cost: maintenance work to sync…

Would you please search for an issue which was created and disappeared, and post an image of the history? That may help indicate what is changing in the issue to cause this. Thanks!

Hi @Sarah Coles I notice a couple of things: The issue shown in the audit log is not in the PROD project, and so fails the first condition...so no more processed. Is that what you wanted? Next, I see the "Allow Rule Trigger" option is enabled. That means this rule can lead to triggering itself for other linked issues,…

Thanks for clarifying! If you remove that first condition test (after the branch) you should be all set to add issues, and any subtasks under them, as needed. For example: * trigger: sprint created * action: create issue (assigning it to the sprint with {{sprint.id}} * branch: most recently created issue* action: create…

Hi @Shehrooz Ahmad -- Welcome to the Atlassian Community! When you read over that error, you note it indicates there are components in the rule requiring issues, and there are none. That is correct... Your trigger is sprint created, and sprints initially have no issues so none are available. If you expect there to be…

Hi @Jeffrey Bistrong I do not believe that is possible with out-of-the-box JQL features, as you would need the ability to nest queries to find any new epics: "Epic Link" IN (some other JQL result set) You note one possible work-around, which is to mark all relevant issues somehow (e.g. label, component, custom field, etc.)…

Hi @Alena Samruk Are you using the built-in checkbox field or a marketplace addon app for checklists? * The built-in fields are normally accessible from field edit during cloning * If not, or the field is from an addon app, you can use the advanced edit with JSON…

Hi @Nilüfer Çelik Another question: did you recently change your product licensing, as there is a defect for this symptom when the software license is cancelled: https://jira.atlassian.com/browse/JSWCLOUD-18170 Kind regards, Bill

Hi @Abhinav Reddy Copying the labels from a story to a created subtask is possible with an automation rule. You describe that you tried this, so...please post images of your rule and the audit log details. Seeing that information will help the community to offer you suggestions. Thanks! Kind regards, Bill

Hi @Khyati Pitroda Have you checked if there are any automation rules running which may be moving/deleting/transitioning the issues? You can check this by searching for the created issue and looking at it's history, or you can navigate to the automation audit log to see if any rules have run during the timeframe the issue…

Hi @Sari If you are trying to link the trigger issue and the newly created one, your rule is missing a branch...otherwise the rule is trying to link the trigger issue to itself. For example: * trigger: issue commented * condition: check the comment with JQL * action: create the new task * branch: on most recently created…

Hi @Alex If all of the other query criteria apply, you could alter the query slightly to do that: project IN (TOPPROV, ABC) AND (created >= 01/01/2022 AND created <= 07/01/2022) AND assignee IN (I.shangarev, t.petrakov) AND ( (resolved >= 04/01/2022 AND resolved <= 2022-07 -01) OR resolved IS EMPTY ) Kind regards, Bill

Hi @Thomas One way to do that would be with an Automation for Jira rule...with some limitations: * This will require a global/multi-project scope rule, and execution of such rules is limited by your Jira license level. Please discuss that with your site admin as they will need to create the rule and to check on limits. *…

Hi @[deleted] First thing, I personally do not believe there is a "best" way to address this use case/flow. Any way you choose to solve this with Jira will have advantages/challenges to address. How you choose to solve this greatly depends on how your teams want to work. A few ways I have seen this done are: * Two issues*…

Hi @Kshamta Pareek -- Welcome to the Atlassian Community! You note wanting to report the status changes for a task without a paid addon, and putting the results into a spreadsheet. A couple of ways to solve this are: * Build it yourself, using the REST API functions and expanding the changelog histories, and then parsing…

Thanks for that clarification. Again, there is nothing built-in Jira to help with that. With the Google Sheets report you describe, you could try to write an application to open the document, update it, and send the report. Or you could investigate marketplace options to do so, as there appear to be several apps for…

Hi @Saurabh_mittal -- Welcome to the Atlassian Community! For your scenario is this one team doing work across multiple Jira projects or multiple teams (with different peopel) doing work across different Jira projects? I ask that question as different teams' sizing (with story points) is usually different. That is, one…

Hi Francis, I have not used that addon, so I have no input on it. I just checked and could not find any obvious suggestions for collision detection in the public backlog, and I found a different addon for Confluence to help with this issue. Regarding the situation of 2 (or more) people updating the same field in Jira…

Hi @Yash Raj If the chart and/or table that John suggested do not meet your need, I do not believe there are any built-in gadgets that will display those fields as a bar chart. Instead please look at the Atlassian marketplace for free or paid addons for reporting/dashboards. If you do not need this in a dashboard, you…

Hi @Dhinesh Dhanapal From the dashboard, select the option at the top-right for ... Rename and Share, and then change the Editors for the dashboard. Kind regards, Bill

Hi @Марко Лошић -- Welcome to the Atlassian Community! There is nothing in out-of-the-box Jira Cloud which will send a status report as an attachment. Depending on what you mean by "automagical export" and "status report", some of the built-in features might help...Please check the documentation to learn more about these:…

Hi @francis Yes, and to John's answer: You seem to be describing is a process problem and not a technical one: with different text fields a tool cannot easily determine that two different people ignored the data in the other fields while making changes. A couple of possible answers to your question of "How can you avoid…