Bill Sheboy Expert

Hi @Geoff Robles Short answer: no, this will require multiple rules. First, I recommend mapping out all of the cases you want to cover. Next... * With the trigger Issue Linked, the rule can handle linking the Tasks to the Story (or from the Story to the Task). If your link has direction, the rule could use an if / else…

Hi @Akash First thing, for your "3) Created vs Resolved Filter", you have this expression: AND (created <= now() OR (status = Done AND Resolution IS EMPTY)) now() is "now" and so it would not be possible for issues to be created after the moment the query runs. Thus the second part of that expression will never impact the…

The normal workaround for this scenario is to change the rule actor to a user with Creator permissions. If that does not help, please post the following for context and perhaps the community will have more suggestions: * an image of your complete rule in one single image for continuity * images of any relevant trigger,…

Hi @Marek Stracanek -- Welcome to the Atlassian Community! First, a disclaimer: I am just another Jira user and have no business relationship with Atlassian or any of their marketplace partners. With that out of the way... Yes, I believe this symptom is a side-effect of the licensing model for JPD where the usually, all…

Hi @Edward Hunter -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, and * an image of the audit…

Hi @Guillaume BERTRAND -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, and * an image of the…

Thanks for the additional information! Your rule could first test if the Original Estimate is set, and if not only then use the REST API to check the sprint values (for upcoming sprints).

Hi @Simon Keller This is the second community question I have seen today for this symptom. I recommend working with your Jira Site Admin to contact the Atlassian Support team to take a look: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to benefit the community. Thanks!…

Hi @Carlos Piña López -- Welcome to the Atlassian Community! First thing: what problem are you trying to solve by transitioning the cloned issue to the prior status of the original? That is, "why do this?" Knowing that will help the community to offer better suggestions. Until we know that... There are several ways to do…

Hi @Fidelidade JIRA Admin There is no "filter" function for smart value lists. Here are the supported smart values and functions: https://confluence.atlassian.com/automation/jira-smart-values-lists-993924868.html Instead you could use an iterator and smart value, list…

Hi @Jonathan Bobo -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center; * if using Cloud, what type of project is this: company-managed, team-managed, etc.; * an image…

Hi @shantanu behera The challenging part in what you describe is identifying the "next upcoming sprint". I suggest separating this into two things: * Use a rule to detect the sprint scope change for issues added to the in-progress sprint. Although...the team and Product Owner should already know that when the team is…

Hi @Apryl Harris The built-in JQL features do not support that type of query. As you note, this is possible when checking one issue at a time using the linkedIssues function. For example: project != projectABCD AND issueLinkType = "is blocked by" AND issue IN linkedIssues("projectABCD-1") ORDER BY Key ASC As you note no…

Hi @張博勛 -- Welcome to the Atlassian Community! What do you mean by "TODO panel"? Do you mean the status on the Jira board by its columns? If that is the case, an automation rule with a scheduled trigger and JQL to find the issues could be used to then transition their status value, however... What problem are you trying to…

Hi @Pinjara Srikanth -- Welcome to the Atlassian Community! That is possible using an automation rule to call the REST API endpoints with the Send Web Request action. If you want to try that, here are some references to get you started. * Automation…

Thanks for confirming that as it shows JSON will be needed instead: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field For example: { "fields": { "customfield_12345" : { "id": "{{triggerIssue.customfield_12345.value.id}}" } } } Please your own custom field ID…

Hi @Toomas Adson Yes, that sounds correct, and...because this is a custom field for Jira Data Center and you likely want to update the parent Epic, the REST API must be used. Please see this post for more details in this great article from John Funk:…

Please select your field from the dropdown list, Choose fields to set. At the right side of the field, there will be a ... option, select that, and then COPY. Now click on the field, changing the source, Issue to copy value from, to Trigger issue For example:

The Smart Values Condition is checking that the value is not empty before the rule continues. Then in the Edit Issue action, the field may be selected to Copy from Trigger Issue. That will copy all values currently in the parent to the children, regardless of what is selected.

I thought you wanted to copy the Team from the trigger issue to the child issues. Is that not the case?

Hi @LuisPinto Just to confirm, is the parent's field a multiple-select option field? If so, the rule could use a dynamic JSON expression (rather than selecting the field from the Edit Issues dropdown list), and built using list iteration. For example, the JSON could be this based on the rule you show: { "fields": {…

Hi @Philip Ng -- Welcome to the Atlassian Community! You could try the text function to remove all of the markup, including attachment images: {{issue.comments.last.body.text}} This will also convert any mention markup into just the display name of the users. Kind regards, Bill

Hi @Sharee -- Welcome to the Atlassian Community! Please see this knowledgebase article for changing some of the advanced roadmap fields using JSON in a rule: https://confluence.atlassian.com/jirakb/how-to-update-a-story-s-target-start-and-end-dates-based-on-the-sprint-dates-using-jira-automation-1189790988.html Kind…

I am not using Assets currently and so cannot test that, although I suspect if the AQL succeeds the rule will also.

Hi @LuisPinto This is a very old thread, and so I recommend creating a new question. That will ensure the maximum number of people see it to offer suggestions, and to help focus on your question. When you create your question, perhaps add a link back to this thread, and include the following for context: * what type of…

Hi @eric caprio First a disclaimer: I am not currently using a build pipeline with my Jira instance, and so cannot test my suggestions to verify them. Instead my suggestions are based on what I know about automation rules. With that out of the way... For this scenario, once the rule is triggered on PR Merged, you want to…

Yes, that is the one.

If you need to return the value with an ADF format, please read the documentation on using the REST API with that format. It is likely additional JSON encoding functions will needed to prevent errors when making the request.

Without seeing the specifics of your automation rule, I am guessing it uses the Lookup Issues action to find the issues and send the list. In that case, either the JQL could be adjusted or the smart value, list filtering could be used:…

Um...I am unclear how that condition works with the option "does not match regular expression". The first value {{#issue.labels}}{{/}} would return null because no values are returned inside the iterator. What I was suggesting was this to detect when there are stray labels: * smart values condition:* first…