Bill Sheboy Expert

Hi @Cash Coyne I recall community posts of others trying that approach, although I have not tried it. As I am now on a free license I would be reluctant to experiment with it...given the packaging limit changes :^) My hypothesis is such a solution approach could lead to either deadlocking and / or service limit problems if…

Hi @ნოდარ ვარდიაშვილი_ Nodar_Vardiashvili_space_ge Where are you trying to perform this validation with the regular expression? For example, in custom code you wrote, an automation rule, etc. Have you tried to floor or format the story point value before performing the comparison? Kind regards, Bill

Advanced Branching is one of the types when you select to add a branch to the rule for Jira Cloud. https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/#Advanced-branching This is not available for Jira Server or Data Center versions of automation. Here is the suggestion to add that…

Hi @Christopher Vickery and @Trudy P Claspill Regarding the challenges Trudy surfaces for changes to the Fix Versions field, there is also a known defect for the changelog for that field...and so it cannot be relied upon to discover changes during rule execution: https://jira.atlassian.com/browse/JRACLOUD-80486 However...I…

Considering the documentation disclaimer, the only way to confirm what works is by experimenting... After I pondered a bit, I remembered I solved a similar challenge last year with created variables: * action: create variable* name: varRegularExpression * smart value: ([*_{}\[\]()#\+\-\.!|]) * action: create variable*…

Is the feature the parent of the Story (i.e., an Epic issue type), or a custom field in the story? That will be a long label as it includes the Story's Summary and Epic Summary / Name. And it could fail to add if there are special characters in the Summary. The spaces need to be replaced with another character, such as an…

Hi @Maartendirickx -- Welcome to the Atlassian Community! Unfortunately, there are now at least 3 fields named "Category" in Jira projects, of which the field for team-managed, business projects is only one. Selecting it from the Edit Issue action field dropdown does not work (and shows the JPD Category field for my site).…

Hi @Toni Duer and @Kalyan Sattaluri Please note the {{fromString}} and {{toString}} values for the changelog of Fix Versions could overlap in values, and... There could be inconsistencies due to this known defect for changelog accuracy of list fields such as Fix Versions and…

Hi @Michał Pacewski The create subtask action is based on the rule scope for which issue is "current". To create the subtasks as children of the newly created, a branch is needed. For example: * action: create issue, for a task * branch: to most recently created issue* action: create subtask Kind regards, Bill

Hi @surabhi.agrawal -- Welcome to the Atlassian Community! First thing for your scenario, what happens if the dates are the same value: is the value set to yes or no? Next, what have you tried thus far to solve this? * If you have a rule and it is not working, please explain what is not working as you expected, post images…

Hi @Amy Chang For your scenario, your rules will need to use various different triggers, and use conditions to decide what to do. In general... * To clear the field, please try the issue edit action, leaving the value empty * To always copy from the current parent epic, try the issue edit again, selecting to copy from…

Hi @Yousuf Al Rawahi From what you describe, you have two automation rules, and the actions of one (create the subtask) will trigger the other (to attach the form). This second rule has probably enabled the option "Allow Rule Trigger". The Issue Created trigger can fire so quickly that some issue data may not yet be…

Hi @KB When you want to strip out the markdown, please try the text function: {{issue.someFieldWithMarkdown.text}} And also... The documentation for automation use of regular expressions states they are "based on Java's Pattern class", but it does not state what actually is / is not supported. Several community posts…

We would need to see the audit log details to know more, but the likely cause is the two different edits of the issue colliding. Perhaps try adding a Re-fetch Issue action after the transition and before the Assign Issue action. That will reload the issue data before proceeding in the rule steps.

Progress! Now you want to add / remove labels, having the label somehow reflect the date change. Is that correct? If so, what is the format you expect in the label?

Hi @andrea.rodifalanga The easiest way to do this is to select the option to include the attachments when the issue is cloned manually. With automation rules, the features to select the source issue for attachment copy are quite limited, requiring the source to be: the trigger issue, current issue, or some linked…

Thank you for clarifying! The rule you show is triggered on Issue Commented, and so only works with attachments added during commenting. To also copy comments when they are added without a comment, you could try a second rule, triggered on Issue Field Changed for attachment. I have not tried that to learn how it handles…

Hi @Prinka Rai Based on what you described, have you tried changing the rule condition to include all three issue types? If you have, what is not working as you expected? Kind regards, Bill

That sounds likely, but I do not know as I am not using JWM. My suggestions were targeting Jira Cloud features. You could try searching in the developer community to see if there are related questions / solutions: https://community.developer.atlassian.com/

I am unclear what you are updating with that expression, but here is the syntax for adding / updating issue links with JSON in an automation rule: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Linking-issues

Hi @Reha Jhunjhunwala -- Welcome to the Atlassian Community! As this is a very old thread, I recommend you create a new question, perhaps linking back to this one. That will ensure the maximum number of people see it to offer suggestions. Thanks! Kind regards, Bill

The expression should look like this, such as called from a browser, substituting in your values: Your Jira URL/rest/api/3/field/customfield_12345/context/67890/option If this is for one context, you could call this manually to identify the value for that second id number (the context):…

Hi @Nancy Tsai Yes, and...to Trudy's answer: Remember to add that Clone Issue action before the Create Variable one to get that scenario to work as expected. If your scenario is different than that example rule, please disregard. Thanks! Kind regards, Bill

Hi @Dmitry Alabyan Is this the one you are looking for to get the available options for a custom field: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options/#api-rest-api-3-field-fieldid-context-contextid-option-get Kind regards, Bill

Sounds good...and if... They used an automation rule (rather than a workflow action) to add the description template, your rule will need adjustments, possibly to allow the first rule's actions to trigger yours.

You may use this how-to article to identify the smart values, and their structure in the issue: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Also, I recommend pausing to talk to your Jira Site Admin to learn why there are two fields. That technique is sometimes used to add template…

First thing: the trigger is the generic one for Issue Updated. I recommend changing that to issue Field Value Changed. That will help focus your testing as the rule you show could be triggering on other issue changes. Next, let's map out the cases so you can exercise them. Please adjust accordingly. * GIVEN date is empty…

Something is up: that should not be empty! Your trigger is checking the "Issue Description" field, and not the "Description" field. Do you have multiple description fields on your issues?

Hi @Vicky S I believe this needs a couple of conditions...assuming the trigger is specifically on your date field changing. * First check if the label exists. If it does not, proceed with your next condition... * For the first time check if {{fieldChange.fromString}} does not equal empty * Then set the label. Kind regards,…

The bold markup should not be it. One more thing to try...let's write the description directly to the audit log and see what markup it contains: Description: {{issue.description}} If smart links are used, this will show it. If not, it will show what we need to correctly parse the description for the key.