Bill Sheboy Expert

Hi @Deepak Rai Yes, and...to the suggestions from @Tomislav Tobijas Creating a project takes time, and rather than estimating the amount of time to use in a Delay action, perhaps use two automation rules to allow Jira to determine the timing: * The first rule creates the project * The second rule has a global-scope using…

Thanks for that information. Just to confirm, you only want the Jira issues to have the major version value for the release (in Jira and to prod), correct? If so, if you have the Jira issues, you could get the minor version name or id from their Fix Versions values. Assuming there is one-and-only-one value in the Fix…

My apologies if you found my post read that way! I perceived you had only seen part way down, and not the original one. Thank you for the feedback.

Hi @Cristian0791 I am not the original poster asking the question. If you check the top of the thread you will find the poster asking the question to help mention / alert them to your suggestions. Thank you. Kind regards, Bill

Hi @Morgan Watts I do not know the answers to the questions you list, and... I normally use this endpoint to create a page: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-page/#api-pages-post Also, as you describe creating the page with data from the trigger issue, I have found it easier to use the…

Hi @Gilad Waldman First thing: how is your team using the "minor version" releases? That is, are they: * just holding buckets, and never intended to be Jira-released as versions or to production code, * they were incrementally released to production code but the version was not Jira-released, * something else? Considering…

Hi @William Pénet -- Welcome to the Atlassian Community! Yes, and...to Trudy's suggestions: When combining any other trigger condition with Issue Created, I recommend always adding the Re-fetch Issue action immediately after the trigger (as you show in your original question). This will help prevent any racetrack errors…

Hi @Lee Tarter -- Welcome to the Atlassian Community! Without seeing the details of your Edit Issue Fields action, it is unclear what you are trying to do. Is this what you are trying to do: GIVEN an Epic issue which has one or more child issues WHEN the Due Date changes in a child issue OR WHEN the Start Date changes in a…

Please post the following: * An image of your complete rule, in one single image file. This will provide overall context. If your rule is larger than a single page, try using a screen capture tool or browser addon which supports scrolling page capture. * An image of the complete Edit Issue action where that JSON is…

It does not appear you have tried what I suggested using the regular expression. Please read my first post, implement that approach, and re-test.

From the commit smart values, such as the repository, can you determine if the sandbox was used? If not, you may need to use the commit information to call the REST API endpoints for your source control tool, using the Send Web Request action in the rule.

What have you tried for the suggestions I provided? If you have updated your rule and it is not working as expected, please post: * an image of the updated, complete rule in one single image * images of each rule action and condition * an image showing the audit log details for the rule execution * explain exactly what is…

Hi @SAzaruddin.mp Adding to the ideas from @Valerie Knapp ... For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in one image file, * images of any…

Hi @chris cawley -- Welcome to the Atlassian Community! Where are you trying to use that JSON expression? Is that for an automation rule? If so, please post an image of your entire rule, the action where that JSON is used, and the audit log details showing the rule execution. Also, there are a few problems with the JSON: *…

Thanks @Andy Gladstone I was checking if there was guidance which I had not found. There are some with years-old "featured" ones, yet perhaps those are still considered more important than other posts. Here is a quick chart I made last week of the non-zero, featured item counts:

Thanks for that information, and... Please note the Move Issue to Board action was specifically added to automation because of another design problem / choice for team-managed projects: Unlike a company-managed project, for a team-managed project the status value is independent of when an issue is shown on the board versus…

Please post images of the following to provide context: * an image of your complete rule (in one single image file) * images of each rule trigger, action, condition, branch, etc. * an image of the audit log details showing the rule execution

Once again, for automation rule questions please post images of the complete rule and audit log details. Those provide context for the community to offer suggestions. Thank you. Without seeing those... Please consider Figma is an external tool, and integration with built-in features like automation rules likely requires…

Hi @Mirja Baig Adding to Walter's suggestions... You describe the issues are in different projects. And so the rule scope must be multiple-project or global to access the issues. Please discuss this with your Jira Site Admin as they will need to change the rule scope using the global automation access. Kind regards, Bill

Happy holidays to all!

Hi @Olive Sun For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * an image if the issue create / edit which is using your JSON expression, * an image of…

Indeed! I am concerned and curious to learn what they are actually implementing for the in-progress suggestion in this area, or if it just a delaying tactic (pun intended ;^) https://jira.atlassian.com/browse/AUTO-32 If it is a premium / enterprise-only feature to toggle branch processing type, that is going to cause quite…

My understanding is the branch smart values are only available with the branch-related triggers, and not the commit ones. Did you try writing the smart value you are testing in the condition to the audit log to observe what it contains? That is what both Trudy and I were suggesting.

Hi @Dmitri Vaschuk -- Welcome to the Atlassian Community! For an automation question, please also post an image of the audit log details showing the rule execution. Until we see that, what is not working as you expected? Have you tried writing the commit smart value information to the audit log to compare to what you are…

Hi @Ryan Gutierrez -- Welcome to the Atlassian Community! What you describe is the already mentioned workaround described in the suggestion / defect to fix this symptom for Team-managed projects: https://jira.atlassian.com/browse/AUTO-519 Kind regards, Bill

Hi @Ori Bergman -- Welcome to the Atlassian Community! Adding to the other suggestions provided... What are the types of your projects: company-managed or team-managed? This is relevant as you want to transition issues in different projects: * For company-managed projects, the status values are all shared globally...even…

Hi @Vikrant Yadav Following up on your last question from the other answer to find the attachments added with the last comment, for workarounds there is a "simple, mostly accurate" way: Let's assume the time from creating the comment and posting the attachments in the body is less than 10 seconds (or some figure you…

Hi @Harsh Jain -- Welcome to the Atlassian Community! Adding to the above suggestions, please note the {{design}} smart value is only available with the design-related rule triggers: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-design/ Perhaps if you provide more context that will help the…

My suggestion for #5 was in order to parse the lists into IDs for each case, followed by merging them for use in a single branch / reporting need. NB: I did indicate it was a reach to achieve that ;^)

Thanks for that information. The syntax you are using to "find" the smart value in the webResponse body is invalid and not a feature of automation rules. And, the supported way to filter within a list iterator would not work for your case because data / fields outside the iterator scope are not visible inside. Once…