Bill Sheboy Expert

Please post images of your entire rule in one continuous image and of the audit log showing the rule execution. Those may explain why the value is empty. Thanks!

Please post an image of the audit log details showing the rule execution. When you do so, expand the areas at the right side fully. There is no such thing as an "Automation project". Please identify the project type: * Navigate to your list of projects: * yourJiraURL/jira/projects * Find your project in the list * What is…

When you have access to log into that email account, that should be all that is needed. In my opinion, there is no amount of "proof" to indicate someone is the owner of the email account without login. Showing old emails will not help. And from what you describe, this is currently a free license account. Again, you cannot…

For testing, you could create the variable with the JSON as I described earlier, and write that to the log and remove the Create Work Item action. Please try that to confirm the JSON matches what you expect. Once it works, you may re-add the Create Work Item action to test further.

TIP: When diagnosing rule problems, use the Log action to write values to the audit log for later investigation. Using log writes you would find three problems, including where your scenario is different than the article I showed: * Your variable is named allAssignees, but you have added a space in the name later, making…

Sorry, I added the toDate conversion which automagically adds a time. Let's remove that to only use the text from the date range value: {{jsonStringToObject(destinationIssue.customfield_10393).end}} That will be in jiraDate format and so should work.

Hi @IFERGAN -- Welcome to the Atlassian Community! When using a free license account, you need access to that email account in order to log in. There would be no other way for Atlassian to validate it is your site. When using a paid license account, I hypothesize it is theoretically possible for Atlassian to validate your…

Hi @Dan Spearing There are two problems with your smart value expression: * varSource is not defined, and that leads to a null value * once inside a set of double-curly brackets, do not add more Please try this expression: {{issue.summary.replace(fieldChange.fromString, fieldChange.toString)}} Kind regards, Bill

Hi @Khalid El-Bialy -- Welcome to the Atlassian Community! First, what version of Jira are you using: Cloud, Server, or Data Center. That impacts the supported features of automation rules. Next, I recommend pausing to review the documentation for how math expressions work with smart…

Hi @Trevan Householder_Isos-Tech-Consulting_ What you describe for expanding options for user inputs is part of several open suggestions, including at least these: https://jira.atlassian.com/browse/AUTO-744 https://jira.atlassian.com/browse/AUTO-1729 Regarding workarounds with the present features, you could: * use Short…

You appear to be using Jira Server (or Data Center), correct? If so, there are several things which could impact the behavior of JQL: upgrade problems, history problems, etc. If you check with your admin they may know if others are seeing unusual search results. If you are using Jira Cloud, the image you show of that Pie…

Hi @Vincent Larouche -- Welcome to the Atlassian Community! Even though you are following a knowledge base article, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed,…

Hi @jessica_huebner Rather than using if / else condition blocks, you could instead use a Lookup Table to simplify your rule and make it easier to maintain: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-lookup-table The rule would need handling for edge cases to decide what to do if…

Hi @philip_song I am starting a new answer to this question to avoid colliding with the other suggestions, and to provide more ideas to try... First, what type of project are you using: company-managed or team-managed? Next, if using team-managed what is the type of your custom field: a global, user-selection field or a…

Okay, I am confused by your response... You originally noted some JQL queries were not working as expected and now you are indicating they are working fine. Apparently there is no problem so solve, so please disregard my suggestions.

Hi @philip_song It is the stray comma which is outside of the conditional expression, and so it appears before the section for customfield_15851 when the first field is null. Please try moving it inside. TIP: for dynamic JSON expressions, I recommend building them in a Created Variable and logging them before use in the…

In that case, please work with your Jira Site Admin to ask the Atlassian Support team for assistance solving this. The community members will not be able to access your site data to help.

My apologies if I was not clear: please show the actual search view with the JQL which returns issues, including the one you show. And, did you check for other variations of capitalization of the label value, perhaps from earlier entries? There is known defect for that symptom described…

That linked post and this article explain the steps: https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Find-Overlaps-Between-Lists/ba-p/3045704 Please show what you have tried thus far to solve this for your rule, and explain what is not working as expected. That will provide more context to…

Hi @Chandrashekhar Maruti Badar Depending upon the endpoint and its response, you may not be able to parse the response as JSON (or with dot-notation for attributes) in a rule. Based on what you describe, perhaps this response is plain text. I recommend experimenting: * write the entire response to the audit log to confirm…

Labels are case-sensitive. Do you have other variations of that label which are not exactly "Codeupdates"? If not, please post a image of Jira for the JQL search, showing that exact JQL, and a work item with that exact label value? Please also note: as you are not also testing for EMPTY, the JQL you describe will always…

Looking closely, there is a typo: there is only one and not two curly brackets at the start of the second condition in the "first value". Please add the second one like this: {{destinationIssue.issuetype.name}}

Hi @Digvijay Singh Gehlot There are no built-in automation rule actions to do this. A rule could send an email / message as text, or create a text Google document. As an alternative, you could create a saved JQL filter and ask people to subscribe to it, allowing them to then download the results as a spreadsheet or as CSV.…

Hi @Vinnasoft -- Welcome to the Atlassian Community! Adding to the information from @Marc -Devoteam- ... What is the purpose of adding the comment? If you share that, perhaps the community can offer additional ideas. Until we know that... You posted this question in the automation product area, and thus if your intention…

Hi @Mauro Dalle Prane -- Welcome to the Atlassian Community! Adding to the information from @Mohanraj Thangamuthu here is the link to the incident, which appears to be resolved: https://jira-software.status.atlassian.com/incidents/czsbxccb7l6h Kind regards, Bill

Hi @Prajwal Sapat -- Welcome to the Atlassian Community! I recommend first pausing to consider the entire value stream (from concept to cash) for your own organization. Then review the handbook provided by the Jira Product Discovery (JPD) team:…

Hi @Melisa K_ Savich Yes, and...to the ideas from Amanda: Since the last community re-organization to change where one may create questions versus discussions versus articles, I have used this approach: * for an apparent defect, I find the article for the latest community release notes at the list below, adding a comment…

First, please see the documentation for that JQL function as you are missing the quotation marks for the date increment: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#endOfDay-- Next, in your advanced branch, I recommend not using a variable name which can match the built in ones. That is, use…

Correct. For several things like this, the Status Category for the Status does not impact the behavior. There is no way to fix this for that built-in feature where the Story Points are summed in the backlog. This inconsistency with the Status Category behavior creates several challenges / limitations, particularly for…

@Blake please post images of your current rule and of the audit log details here in the question using the insert photos option. Those will provide context for the symptom.