Bill Sheboy Expert

Hi @Artur -- Welcome to the Atlassian Community! I recommend starting by writing some JQL which you expect to return the issues which should have created the issues. After that is tested, you could use that in a scheduled trigger rule, which then uses Lookup Issues to find the expected, created issues...and if not found,…

Hi @Farrukh Elahi -- Welcome to the Atlassian Community! For a question like this, I recommend posting an image of the complete rule, images of the relevant actions / conditions /branches, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Until we…

Hi @Scott Buratt First thing, I am just another user and not an employee of Atlassian or a marketplace vendor. With that out of the way... JQL is not a SQL, and so does not have such features. IMHO it is primarily for returning issues to support the features in Jira, and so has limited other capabilities. To do more, often…

Hi @Bikram Agarwal -- Welcome to the Atlassian Community! As this is an intermittent problem, with essentially an unchanged rule, I recommend working with your Jira site admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ They may see something in their internal logging which is not…

Hi @Aaron Rose For a question like this, I recommend posting an image of the complete rule, images of the relevant actions / conditions /branches, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Until we see those... You describe having a Jira…

Hi @Mary Mark For a question like this, I recommend posting an image of the complete rule, images of the relevant actions / conditions /branches, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Until we see those... Your question description uses…

Hi @Zhinoo Zobairy Are you trying to change the project category, or actually archive or delete a project? If you want to change the project category, please see the update project function: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-projectidorkey-put Kind…

Hi @Nava Bar-Sagi For a question like this, please post an image of your complete automation rule, images of the relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks! Until we see those... From…

Hi @Dhanashree Gaikwad -- Welcome to the Atlassian Community! First thing, it will certainly help one team if they have one board for all of their work. It will reduce task-switching, improve focus, raise visibility of progress and make planning / coordination / etc. easier. This will also help as the team appears to have…

Hi @Mart Postma First thing, this will be much easier if you have one of the marketplace addons to enhance JQL features. As you prefer not to do this, some possible work-arounds are... (A) You could export all of the epics to a spreadsheet weekly, filtering out the ones missing the links of interest, either your types or…

Hi @Sridhar Gandla For a question like this, please include: * an image of your complete rule, * images of any relevant actions / conditions / branches, * an image of the audit log details showing the rule execution, and * explain what is not working as you expect. Those will provide context for the community to offer…

Hi @Bernard Carpio -- Welcome to the Atlassian Community! You are trying to create the JSON for a multi-select, custom field: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-select-custom-field To make that easier you could use the asJsonObjectArray() function to populate the…

Hi @madhuri kaniganti -- Welcome to the Atlassian Community! Are you asking if the status can be transitioned based upon the user who created the Idea? If so, I believe an admin for the Jira Product Discovery (JPD) project could create an automation rule to do that transition. Kind regards, Bill

Hi @sarend You seem to be using the update syntax for a multi-select field. Is your environment field single or multi-select? If it is single-select, perhaps try this: { "fields": { "customfield_10156": { "value" : "{{userInputs.OrgEnvInput}}" } } } And also...please confirm that the value in your user input field exactly…

Hi @Isabella Musial First thing, I am using Jira Cloud and not Jira Server, so my suggestions are based on what I know about automation rules, and not specifics for the Server version. In your current rule, have you considered branching to the parent (after the story is updated) to make the change by comparing the date…

Thanks for reviewing this approach, @Svenja Lorenzen Some of the larger, and more structured, places I have worked have used these to feed into the start-up of new efforts / projects. (e.g., in a PMO or Agile PMO) To do this leaders and teams were asked to mine the earlier learnings during project initiation, to both…

Thanks @Kristján Geir Mathiesen Several teams I have supported have combined these ideas with an annual check-in to: retrospect, have fun together, update our mission and measures, and refresh our working agreement...with the last one taking the form of a team poster.

Hi @Ashley Honeycutt When you want to iterate over a list of values in a rule, the syntax is like this: {{#someList}}{{someFieldOfTheList}}{{/}} For your case, are you trying to mention on the user's display names? If so, that would be like this: {{#issue.approvers}}@{{displayName}}{{^last}}, {{/}}{{/}} That last handling…

Hi @Glen Brannigan You could do that using the issue created trigger, a branch on JQL to the issues with the same parent as the trigger issue, and then an edit to copy the field using smart values. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @[deleted] What is not working as you expect? If you are not getting a URL to the attachment file, try using the {{content}} smart value instead. And consider that only recipients with a Jira user will be able to access that URL. If you are expecting an image of the attachment file to appear in the email, that is not…

Hi @Aurelie Seth When you think of a "value vs complexity matrix" what does that look like to you, and how would your teams use that with Jira? And, how are you representing value and complexity: with custom fields, etc.? For example, are you thinking of a M rows x N columns table, showing the count of items for each value…

Hi @David Torrente - Bibloos -- Welcome to the Atlassian Community! Are you trying to do this: Given there is an epic which has child stories, and those stories have subtasks When the epic has a version added to Fix Version Then copy the Fix Version from the epic to the child stories and their subtasks You could do that…

Hi @Simon Xiao -- Welcome to the Atlassian Community! Within an automation rule, the {{changelog}} only refers to the fields which changed and lead to the trigger. That smart value does not have any other information from the issue history...which is what you appear to be attempting. The syntax you show for using the date…

Hi @Mike Wilkins -- Welcome to the Atlassian Community! Where are you getting information about the "planned sprint"? Is that a custom field your team has added? Next, you are correct that JQL cannot compare issue fields. (It is not a SQL, and so does not have such features.) If you have any marketplace addons for JQL,…

Hi @Tomasz Osik Adding to the earlier answer: I am unclear why you are placing the Change Cost value next to the math operation. Would you please explain? For an example, please show some example values and your expected output (field set). Knowing that may help the community to suggest improvements. Kind regards, Bill

In automation rules, things which happen at different points may not be visible later. For example, when a variable is created inside of a branch or condition. This is known as rule scope. You appear to be using an if/else condition structure, and inside of that creating a variable named Progetto (i.e., Project). That is…

Thank you...Would you please show the details of the issue create action? There seems to something the create is doing which is related to issue linking.

Hi @Paul Scarlett As a disclaimer, I am just another Jira user, and not employed by Atlassian or any marketplace vendor. With that out of the way... Jira is just a tool, and although there are some better (and worse) ways of using it, you can decide how you use the features, and accept what happens. Releases / versions…

Hi @G. De Fazio Adding to Jack's answer... The error seems to indicate a problem with issue linking; specifically that the value used to link the issues is invalid. Please show the details of where the issue link is attempted, and the source of the value used to link the issues. That may indicate the cause. Kind regards,…

Yes, I understood that. I was suggesting the new design (layout, fonts, etc.) are causing this for both the column titles and the card contents. I still recommend submitting the new defect so the Atlassian team is aware you have this impact.