Bill Sheboy Expert

Hi @Brendan Betheldo What does not work as you expected, and what does the audit log show when you try your rule? What does your Assign Issue action contain? One way to do this is to select the Smart Value option with the Assign Issue action, and use this smart value expression: {{issue.comment.last.body.split("…

Hi @Stacey Telford For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @marianna_taborda For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer…

Thanks for that information. As a tip for community questions about automation rules, try using a scrolling browser addon or screen capture app to contain the entire rule in one image. That will ensure it shows with the full context / alignment. Back to your question...I wonder if this is related to the half-hour part of…

Thanks for that information. As @Trudy P Claspill described in that other thread, some links have directions while others do not. The type of link and the triggering issue can be used to determine "direction" when it is relevant. A possible workaround for deleting a single, specific link is to use the Send Web Request…

Awesome; I am glad to learn that helped! To clarify my earlier comment: project-scope rules can create (or clone) issues in other projects, but they cannot see them otherwise for triggers, branches, conditions, and actions. Those need global or multiple-project scope rules.

I'm a bit confused by what you describe... First, Epics and Initiatives do not have subtasks; subtasks are a part of a standard issue type, such as Story, Task, or Bug, as a child item. Next, if you want the rule to start when something happens to the parent issue, your conditions seem incorrect. Perhaps this is what you…

Hi @Troy The trigger controls when a rule starts and conditions limit the continuation of steps. As your rule is written, and assuming it is a single-project scoped rule, it will: * trigger when any issue transitions to Done (from any previous status) * check if the Parent issue of the trigger issue has a status = Done and…

Hi @Nilesh G -- Welcome to the Atlassian Community! Context is important for automation rule questions. Please post an image of your complete automation rule, an image of each action where you are using {{now}} as you describe, an image of the rule details (at the top) to show the rule configuration settings, and an image…

Hi @Enrique -- Welcome to the Atlassian Community! To help with your question, let's align on some Jira concepts first... * Issues are stored in Jira projects * A Jira board is a view of issues within one (or more) projects, based on a saved filter * Some project types can only have one board, while others can have…

Hi @Negar Mousavi As this is an older thread, I recommend creating a new question, and adding a link back to this one. That will ensure the maximum number of people see your question; otherwise only people following the older thread will see it. When you post your question, please include: * your Jira version and project…

Thanks for that information, @Rita Arellano You note Epic and child issues are in different projects. In your rule details, is this rule for a single-project or multiple-project scope? A single-project scope rule can only access issues in that project. Please change the project scope to include all of the relevant projects…

Hi @Rita Arellano Using the Field Value Changed trigger for Component seems like it should work, particularly as you have specific conditions to check for any existing issues with each Component value. The other alternative is to use the generic Issue Updated trigger and then add a smart value condition to confirm the…

Hi @Melissa C I recommend creating a new question, with images of your complete rule, the audit log details showing the rule execution, of any relevant actions, and explain what is not working as you expect. That will provide context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Leon Gumba That error message is the hint that the manage watchers action cannot "see" your new issue. To fix that, please add a branch to the most recently created issue: * trigger: scheduled * action: create issue * branch: to most recently created issue* action: manage watchers Kind regards, Bill

Hi @Joshua Oberlin -- Welcome to the Atlassian Community! Yes, and...to Trudy's answer: There are multiple open suggestions / defects for this symptom, caused by the different contexts and values for Status (and other fields) for each team-managed project: https://jira.atlassian.com/browse/JRACLOUD-78528…

Hi @Ofir Haun -- Welcome to the Atlassian Community! You could use the indexOf() function to find the position of the text in the Summary. If it is not found, the value will be -1, and so that may be used for a comparison. Please adjust the example below for your scenario / specifics: {{#issue.subtasks}}…

Perhaps try extending your original rule, like this, with the changes in bold font: * trigger: issue created * action: re-fetch issue (I recommend adding this after the Issue Created trigger to prevent racetrack error / timing problems.) * condition...on the project * condition...on the parent key * action: create issue…

Sorry, I am out of ideas on this one. Perhaps ping the support team to learn what they suggest: https://support.atlassian.com/contact/#/ In my experience, not all Description field macros / formatting can be done in automation rules. My hypothesis is there's more information "behind the curtain" which we do not have access…

Subtasks are challenging for cloning in rules, and one approach to try is: * after creating the new Task (i.e., the new parent), save the key {{createdIssue.key}} using the Create Variable action * branch to the trigger issue's subtasks* using the Create Issue action again, re-create each one, setting the parent to the…

Thanks, @Rafal 

Regarding story points: * company-managed projects use the "Story points" field, and * team-managed projects use "Story point estimate". Please select the correct field from the dropdown list for the TMP issue, supplying the value as {{issue.Story points}} to copy it. However... Regarding issue types, this is a known…

Hi @Marcel Rossouw Please try using the {code} formatting notation in your rule: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=advanced If that does not help, please post an image of your complete rule and audit log details showing the rule execution. Those may provide context to help explain the…

It appears they are not yet supported for updates using rules. As you are the site admin for a paid Jira Cloud license, you could contact the Atlassian Support team to confirm that and learn any possible workarounds: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to…

Hi @Samuelraj Agreeing with John's suggestions, and... I recommend pausing to understand why due dates are changing, and under what conditions that would be a valid need. That is, what is the root cause leading to changing the field. Please discuss this symptom with your team to learn "why" this is happening, possibly such…

Hi @jbrowne -- Welcome to the Atlassian Community! JPD is using this different version of a date field, apparently to store ranges, as needed. And so text functions are needed to extract the values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ For example one way to do this with your…

Hi @Gabriel Freddi de Matos Santos You could do that with the substringBefore() function when you create the variable: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringBefore-String-separator- For example with this: {{issue.reporter.emailAddress.substringBefore("@")}} And just to…

Hi @John Tucci There is a related suggestion to hide / filter the automation events in the issue history: https://jira.atlassian.com/browse/JRACLOUD-80137 Your idea is a bit different; perhaps add that as a new suggestion / feedback item. Kind regards, Bill

Hi @Abi Williams -- Welcome to the Atlassian Community! Team-managed projects (TMP) have their own configurations and types, different from the shared ones for company-managed projects (CMP). That error indicates using the Issue Type of "Same issue type" will not work with the TMP, and so it shows the specific issue type…

For the format() function, "H" is the hour-of-the-day and "M" is the month-of-the-year. Did you want to use "m" for minute-of-the-hour instead?