Bill Sheboy Expert

The way your rule is written (based on an app translation of your rule): * it is triggering on an issue transitioning from "To Do" to "In Development" * and then trying to transition that same issue to "Running" I suspect that is not what you wanted. Can you please confirm? Instead you seem to want to transition a…

Thank you for that information. That error describes for your global rule's transition issue action, the destination status is not available for that issue type. Please check that you have selected a valid status for that issue type and workflow.

Hi @Santri Web Programas -- Welcome to the Atlassian Community! Adding to Mohamed's answer... When you post images of your rule, please also post an image of the audit log details showing the rule execution. Those will provide context to help the community offer suggestions. Thanks! Kind regards, Bill

I do not have an example, although I provided the steps for the entire rule above, including the specific REST API function to call. Using automation rules requires learning and experimentation, and so I encourage you to try to create the rule. And if you run into problems, post images of your rule and the audit log…

Hi @Ben Krichko Have you tried to create an automation rule in your JPD project for that? It could use a Scheduled trigger with a JQL query on the Ideas to find the ones you are interested in. I just did a quick test and the CHANGED operator does work for JPD idea status values: project = myJPDProject AND statusCategory !=…

Hi @Colin -- Welcome to the Atlassian Community! You may want to also post your question in the developer community: https://community.developer.atlassian.com/ Kind regards, Bill

Hi @Mikael Sandberg FYI...Often for smart values in an expression like this, I think it uses the default attribute when one is not specified; that would be key for an issue. As the defaults are not documented anywhere, I agree with you that using {{issue.key}} explicitly is better to avoid uncertainty :^) Kind regards, Bill

Hi @Raphaël NORYNBERG That does not appear to be possible, even with the public REST API functions. Here is a suggestion to add that feature, which you may vote for/watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-78714 If you have additional ideas for this area I recommend adding to, or creating an…

Hi @Brian Taylor There is no automation rule action to update a version, but there is a trigger to detect an update. Have you tried to do something like this... * trigger: version updated * advanced compare condition: use the change log to determine if the released attribute changed to true * advanced compare condition: to…

Hi @Jenni As you have solved this, please mark your own solution as "answered" to help others in the community. Thanks! Kind regards, Bill

Hi @Andy For a question like this, it can help to also post images of your complete rule and the audit log details. Those will provide context for the symptom. Thanks! Back to your question... Where are you seeing that error in the audit log details? Is it for the advanced compare condition or something else? If it is for…

And...here is an article on calling a REST API function from a rule to help: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Hi @James Jacob First a disclaimer, that I do not work for Atlassian or any marketplace vendors. I am just another Jira user offering some ideas. If I understand what you are asking, I believe this is possible using saved filters to contain the relevant epics, such as for your example of ProjectXY. First though, I…

Hi @Elaine Cawthorne Short answer: maybe. More information... In automation rules, things which branch on multiple things/issues or perform multiple actions together happen in parallel. And so ordering of saved/updated issues is not guaranteed. For your subtasks, can you determine their order by some field, such as by the…

Hi @Nikodem Macuk -- Welcome to the Atlassian Community! I do not believe there is anything built-in to modify the PR that way from an automation rule. Instead have you tried calling the Github REST API from the rule, using a send web request action, to add the label? Kind regards, Bill

Hi @koutarou ishibashi Your expression is both incorrectly using conditional logic and trying to combine that with a math expression in a way the rule cannot process. Instead try using the inline version of those operations. (I am assuming your lookup table values are text, and so have added asNumber for conversions.)…

Hi @Aron Gombas _Midori_ As a reminder...In accordance with the community guidelines for marketplace and solution providers, please ensure you disclose in the text of your post your relationship to a vendor when recommending their products. Please see the community guidelines for more information.…

Hi @Abby-Marie Flood -- Welcome to the Atlassian Community! Have you tried the Get Project one? https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-projects/#api-rest-api-3-project-projectidorkey-get Kind regards, Bill

Would you please post images of your complete automation rule and of the audit log details showing the rule execution that failed? Those may provide some context as it is possible that error is not focusing on the actual cause.

Hi @angel1573 -- Welcome to the Atlassian Community! You cannot change the built-in definition of when a week starts and ends for the JQL functions. However you can use increment / decrement values with the functions startOfWeek() and endOfWeek() to adjust to your needs. Please see this documentation for examples of that:…

Hi @Works, Robert It appears you have an outline for your rule. What have you done thus far to try this? If you have started a rule, please post images of your complete rule, the relevant actions, the audit log details showing the rule execution, and explain what is not working as you expect. Until the community sees…

Thanks for that information and the rule image. First to answer your question about "counting", I would refer to that article for guidance. As of today, that article says the following actions do not count: writes to the audit log, create variable, and create lookup table. Everything else counts... Which is a problem for a…

Hi @Becky Brooks - MCP Gateway for Jira In accordance with the community guidelines for marketplace and solution providers, please ensure you disclose in the text of your post your relationship to a vendor when recommending their products. Please see the community guidelines for more information.…

Hi @Snehal Singh -- Welcome to the Atlassian Community! Customers do not set the service limits. Instead they are defined by Atlassian. To learn about the limits, please look here: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ And if your rule processing was throttled, that could be caused…

That is curious! I just tried and it worked for my test instance of Jira Cloud. At this point I recommend working with your site admin to submit a support ticket to Atlassian. You appear to be on a Standard license level, and so your site admin can do this here: https://support.atlassian.com/contact/#/ When you hear back…

Hi @Jill Vieregge Have any Site Admin or Org Admin users changed the permissions for that user? Have any Project Admin users changed access for the project, removing / altering permissions? Kind regards, Bill

Hi @Nandita Parthasarathy -- Welcome to the Atlassian Community! Issues may be exported based upon what JQL is used. Have you confirmed your JQL is not excluding the subtasks? Kind regards, Bill

Hi @Amit Bhola At what scale / granularity are the items you are planning for 3, 6, 12 month planning horizons? After timeframe-based planning, do delivery teams plan / work-breakdown items before build? If these are large requests and a delivery team then executes on them, you may want to investigate using Jira Product…

Hi @Sindhu There is no "loop this many times" feature in automation rules. There are several work-arounds to do this, including these two: Use text functions to create a counter, and then use advanced branching, as described here:…

Hi @Liam That is a known issue. Here is a suggestion to fix it, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-21430 Kind regards, Bill