Bill Sheboy Expert

Hi @Steve Tedeschi Where are you trying to do this? For example, if this is with an automation rule you could try using the match() function with a regular expression: https://confluence.atlassian.com/automation/jira-smart-values-text-fields-993924863.html#Jirasmartvaluestextfields-matchmatch() Kind regards, Bill

Hi @Brandon Moberg Advanced Branches take a list of values for iteration. Created Variables are plain text values. For both of your rules, the variable should be split into a list to feed the branch iterator. * For the add watchers rule, that would be this: {{addedAccountIDs.split(", ")}} * For the delete watchers rule,…

I believe the first sentence is the key as the announcement article link is included for adding Action Items to Jira: Support to manage Action items in Jira via JQL or REST API or Automations. Right now, Jira does not have a dedicated page like Confluence for viewing all action items directly from comments. The specific…

Awesome; I am glad to learn that helped! If your Jira URL ends in atlassian.net or atlassian.com you are on Jira Cloud. Otherwise it will likely end with your company's name for Data Center.

Thank you, and I see substringBetween() is only performing one single find. To parse out all possible values, the Description needs to be split into lines to search each one. For example: {{issue.description.split("\n").substringBetween("Ticket ID: ", ")")}} Update: if you are using Jira Cloud and the Description contains…

That is odd, and I do not see that with similar fields: one used for grouping and multiple other fields used for sorting. I recommend working with your Jira Site Admin to report this symptom to the Atlassian Support team: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to…

Please show the expression you are using to extract the ID values and an image of the action where it is used.

Correct, that is changing the message URL to specifically point to the user's channel. I suspect that works even without supplying their ID in the "Channel or user" field. This approach is not easily scalable as it would require creating a separate Send Slack Message action (with URL) for each possible user.

Hi @Zoltán Lehóczky That is not supported yet. Here is one of the suggestions to add that capability: https://jira.atlassian.com/browse/JRACLOUD-85414 Kind regards, Bill

Hi @peggy_rattarree -- Welcome to the Atlassian Community! Your example appears to show only the Module values. Are all of those shown in the same Domain value, and grouped together, or are they in different ones? What type of view are you using: list, board, etc.? Kind regards, Bill

By the way...my suggestion was based on you needing this information often. If you need this one time (e.g., for an upcoming report, retrospective, etc.) you could also export the issues and do a quick chart / pivot table chart in a spreadsheet to show stacked bar charts for several sprints.

First thing, I personally recommend not using any bot guidance for Jira help (even the built-in one yet). Each Jira version / site / project / issue type / workflow has too much context-specific information which is not available for the bot / guesser to use. Perhaps the built-in one will get better over time. What I was…

Thanks, and I hope Atlassian updates the documentation and automation app if direct messages to Slack are no longer supported from rules. Interestingly...when I tried this scenario, the automation engine's call out the Slack API with a valid Slack user ID does not fail (even though it does not post the message to the…

At that top of that article from @Walter Buggenhout , it describes it is for Jira Cloud. There are comments asking about Server / Data Center, but no responses from anyone who got it to work. I did find a knowledgebase article for Server / Data Center where setting the Target Start and End succeed with rules and JSON, but…

I just checked the public backlog and it appears copying the Team field with an automation rule using the Server / Data Center version is not supported yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-159 https://jira.atlassian.com/browse/JIRAAUTOSERVER-779 https://jira.atlassian.com/browse/JIRAAUTOSERVER-1093 The…

Hi @Chris Theisen -- Welcome to the Atlassian Community! Short answer: that is not possible with the built-in Sprint Velocity report. Assuming you have an issue type (or some field indicator) to identify such issues, you could investigate marketplace gadgets to add to a Jira Dashboard for such reporting. I recommend…

Hi @stephan_lewis No, the JQL CHANGED operator cannot detect history changes for the Due Date field: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED You could create an automation rule, triggered on a change to the field, which uses the {{changelog}} values for comparisons:…

Please post an image showing the audit log details from trying to run the rule. Also, have you confirmed that is the correct custom field ID for your field?

Wow, that is an older version...and was just after distinct was added for Server / Data Center, so I wonder if there are problems in the earlier release. Let's try this: * using your original expression, set the first field (without the distinct) * add a Re-fetch Issue action * using the Log action, write that first issue…

Hi @Isabella Musial First, your rule is branching to "Most recently created issue" but no issues are created during the rule; that is the purpose of that branch type. The branch may be removed. Next, your rule is referencing what appears to be a Created Variable by it has not been defined anywhere. Assuming your "Team"…

Hi @Priya Christy -- Welcome to the Atlassian Community! For Jira dashboards, there is no built-in Sprint Burndown Gadget. Please identify the marketplace vendor of the gadget addon you are using, and then review their documentation to learn more about its usage. Kind regards, Bill

Hi @shantanu behera Automation rules run after some event has happened. They cannot halt processing to show a dialog / pop-up screen. What are the "certain practices" to be followed? If there are required fields, you could either make them required for all issues or add a validator or transition screen to the workflow. For…

Thanks for that information; it confirms my hypothesis that the problem is due to the missing Re-fetch after the first edit action. Do you need the duplicated values in the custom field, or can that be the distinct ones also? If you only need the distinct values, you could do this: * Create a variable which only has the…

If you are up for some reading and experimentation, here are three automation articles I wrote (with the last one showing some more advanced topics): https://community.atlassian.com/t5/Automation-articles/Automation-concepts-Learning-to-write-and-use-rules/ba-p/2901393…

Hi @Kunal Kumar First, this is a very old thread, and so it helps to create a new question. That ensures the maximum number of people see it to offer suggestions...rather than trying to add to the old thread. I found your new question, adding some suggestions here:…

Hi @jbrowne Perhaps there are multiple fields with that same name and the linked one is not displaying...or, something got broken in the project configuration due to the changes. I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support for them to take a…

Hi @Diego Martínez 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, * an image of the audit log details showing the rule execution, and…

Hi @Kunal Kumar 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, * images of any relevant actions / conditions / branches, * an image of the audit log details showing the rule execution, and * explain what is…

Hi @Matt Shovlar -- Welcome to the Atlassian Community! You describe using the Component field to select on which board an issue displays, which means those different values are selected in the different board filters. Have you considered making the field required for the issue creation, ensuring the person creates it so…

Hi @Jennifer Joyce -- Welcome to the Atlassian Community! Adding to Jack's answer: When the rule is inside the branch, "current issue" and "issue" refer to the branched-to issue. In your case, that is the most-recently-created-one. Instead you want to copy from the "Trigger Issue". Kind regards, Bill