Bill Sheboy Expert

Hi @Kajsa Fransson Did you notice the typos in your log and comment actions, where they are missing the period after issue? Kind regards, Bill

Hi @Manhar Sharma -- Welcome to the Atlassian Community! I have not tried to set that field with a rule, but I suspect it is a single-select field type. And so the syntax for setting it would be as shown in this documentation, with the "id" attribute:…

Hi @Dmytro Shaforost What problem are you trying to solve by dynamically changing the REST API call authorization from an automation rule? I do not believe that is a capability of rules, but instead something more likely done from an application calling the REST API functions. For your first question, the user's account ID…

Hi @Celina Kincaid -- Welcome to the Atlassian Community! If you did try this: {{issue.project.projectCategory.name{}}} The reason that did not work is the extra curly brackets after name. Please try this instead: {{issue.project.projectCategory.name}} Kind regards, Bill

Thank you for confirming the field is Due Date. When you test the rule, what do you observe happening?

I do not believe that would be possible with the built-in rule features, and the suggestion to add advanced branching for Server / Data Center has not had much activity: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 Other things to try would be: * investigate marketplace addons for this capability * build a service…

For something like this, eazyBI would work. If you have already built that, no need to read further in my response. Otherwise... You are correct that a work-around like this can be complicated, and it helps when additional tools like eazyBI are not available. Let's first confirm which version of Jira are you using: Cloud,…

Hi @승엽B -- Welcome to the Atlassian Community! When creating your rule, I recommend both checking the documentation for actions you have not used before, and to look at all of the options shown in the rule editor. * For creating a new version, the dates can be set under the additional options for the action * There is no…

Hi @Andrew King -- Welcome to the Atlassian Community! Your advanced branch is iterating over the selected users for the field, and those will each be a user object. In your write to the audit log, you are correctly referencing the emailAddress attribute, but in your send web request you are passing the entire user object.…

Hi @Joao Resende Your rule trigger is Sprint Created, and so the {{sprint}} and {{sprint.id}} smart values are available. Have you tried using {{sprint.id}} as the value for the sprint field when creating the story in the rule? Kind regards, Bill

Hi @Patrick Schmidt First thing, I am using Jira Cloud and not the Server version (which your post seems to indicate). Please test with your version for the things I am suggesting. Thanks! When you added the format string of "yyyy-MM-dd" to the toDate() function that helped with the conversion, and the resulting date /…

Hi @Jan Schiemann -- Welcome to the Atlassian Community! Please try using the minusDays() function on the specific version's date value: {{issue.fixVersions.first.releaseDate.minusDays(10)}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-minus-unit--- Kind regards, Bill

Hi @Ingo Cernohorsky First thing, I am using Jira Cloud, not the Server version, and so my suggestion is based on what I know about automation rules and not your specific Jira version. With that out of the way... Have you tried using text functions to build the epic name, such as with the Replace() function; use that to…

Hi @Michelle Herschell Adding to John's answer: That symptom can happen with the Issue Created trigger because it fires so quickly that some data for the issue may not be available at the time the rule starts...such as the parent key from which to copy the fields. The work-around for this is to always add the Re-fetch…

Hi @Michael Goodrich -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation 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 expected. Those will provide…

Yes, that is possible using the changelog smart values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- After the rule trigger, test if the previous value was empty and then test if the new value is not empty. For example: * trigger: field changed * smart value condition: check…

Thank you for those rule images. Your rule appears to be coping the Original Estimate value from the trigger issue, and back to the same issue. If you want to update from a different issue, the rule will need to access the other issue first. For example, the rule could use the Lookup Issues action to do this: * trigger:…

Just to clarify on the multiple sprints / carry-over issue: if your team clones issues and selects the checkbox to clone the sprint, the sprint value(s) will be propagated. Using the JQL condition approach, I provided the JQL in my first response and the condition type to use is this one:…

Yes: you could use the date / time difference function for that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference--- Or, convert the values to text and then perform the…

Hi @Jonathon F. Lacerda -- Welcome to the Atlassian Community! Yes, I believe that is possible. An automation rule could be triggered on the change to the field, such as the Due Date field. And the person (Jira user) who made the change can be identified from the {{initiator}} smart…

Please see my earlier response: checking if a value is in the available values for a selection field is only possible by calling the REST API and comparing. And...would you please clarify: What problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help to reveal other solution approaches.

Please follow up with your site admin on how to submit a support ticket for your product. My understanding is Atlassian Support for Jira Server ends on 15 Feb 2024; after that only Cloud and Data Center will have support. To learn more about that support change, please look…

Hi @Hector Sibisi Please consider: you are trying to compare the issue's create date / time to the exact sprint start date / time. That is unlikely to ever match, and so a greater than test would help. And even better approach might be this: * Once a sprint starts, it becomes "active" and the issues in it can be found with…

Hi @Kasper Ramstafer The format() function takes an object (like a date) and formats it as text: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- Instead you want to take a text value and convert it to date type. Please try using toDate for that. As you have a non-standard…

Hi @Ersel Bora -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation 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 expected. Those will provide context…

Hi @David Martinez Moreno Would you please post an image of the audit log details, showing the rule execution? That may provide some context for this symptom. Until we see that... You note a "People" field. Are you using a team-managed project? You may find this information at the lower-left side of the page's expanding…

To provide some context for that symptom, please post some images of: * your entire automation rule * images of each action's details * the audit log details showing the rule execution Thank you!

Well done! They were objects, similar to iterating over users. Once you have the object, the different attributes need to be accessed. This how-to article can help when using smart values like this, as it shows the structure and smart values in the…

Hi @Abiodun Famoye -- Welcome to the Atlassian Community! To find issues in closed sprints, please use this JQL function: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#closedSprints-- To find issues in the current, open / active sprint, please use this one:…

Hi @Sonia Lorena Paniagua For automation rules, the Issue Create action cannot set the time tracking fields at the same time as the create. Instead try creating the issue first, branch to the most-recently-created-issue, and then set the time tracking fields, such as Original Estimate. Kind regards, Bill