Bill Sheboy Expert

Hi @Leonardo Silva -- Welcome to the Atlassian Community! Adding to Jack's answer...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…

Hi @Nitu Tarnekar -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, why do this? Knowing that may help the community offer better suggestions / solution approaches. Until we know that... The information you note is stored in the history for each issue, but that cannot be easily queried…

Hi @bartlomiej.jochym Adding to the answer from @Kalyan Sattaluri ... Would you please explain some things about your rule: * Why does this rule move all of the linked issues to Completed when one issue moves to Done? * Which issue are you trying to measure for: the trigger issue, the linked issues, or both? * For the…

Hi @Emna Elleuch Some questions to help guide your approach could be: * When (under what conditions) do you want this sum to occur? For example, when the QA or DEV stories log work, on some time scheduled, etc. * What are you trying to do with that sum value? For example, set it to a field, send a notification, etc.…

Hi @Vinutha GR 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.…

That appears correct. Have you tested it yet? Also please note: if you want to mention a user in a comment so they get a notification, their account id value must be used with the mention syntax. Try replacing this: {{assignee.displayName}} With this: [~accountid:{{issue.assignee.accountId}}]

I wonder if the variables with the converted values are still in a format which cannot be directly converted with toDate. Please try writing the variable to the audit log to confirm the format, and perhaps add more conversion with toDate.

Hi @Jouni Riimala As this is a very old thread, I recommend creating a new question and linking back to this thread. Otherwise only people following this one will see it. When you post your question, please... * explain the problem / scenario you are trying to solve, * include an image of your complete rule, * include…

Please post an image of the complete JSON you are using, as what you show is incomplete, and that may explain why it does not work as expected. Also, I asked earlier if there are multiple versions in the field. Please let me know if there can be multiple values as the syntax will be different: a field iterator must be used…

To format a date in a particular text layout, please use the format() function, or one of the built-in formats. To change the displayed format for a date field on an issue view, please check your profile settings and /or the site settings.

Hi @Andy Tran You state you are trying to list the parent's summaries (that is, the associated epics for any issues in the sprint which started). My assumption is only the child issues, and not the Epics, are assigned to the Sprint. Your rule has a few challenges, and so my suggestions would be: * The rule trigger is…

Thank for clarifying the scenarios. I recommend using two different rules to handle the cases because the changelog will not work with the Issue Created trigger. And so the cases are: Before value After value ACTION Rule to handle this case ------------ ----------- ----------- ------------------------ new issue! empty…

Hi @Rim Ben Rejab Adding to Trudy's answer... The filter for a board impacts what is shown for the backlog, board, and reports. The Kanban sub-filter further reduces what is shown on the board only. It has no impact on the backlog or reports. (Some of the built-in reports have additional options to filter what is shown,…

Thank you for that information. You appear to have most of the parts needed in the rule, with some adjustments: * Remove any JQL with the scheduled trigger * Instead, only use the JQL with the Lookup Issues action, and add the condition you have on the Quarterback field to the JQL * Your rule can then send just one email,…

Thank you for that information. It seems you are trying to copy the Fix Versions from the trigger issue in one project (e.g., DEV) to the linked issues in another project (e.g., CS). Versions / Releases in each project are different, even when they have identical names. In each project, the Versions are created with their…

When you create a variable, that is stored as a text value. Those variables need to be converted to date before using the diff() function. In your create of the "Diff" variable, that would be this, adding the missing units of measure, days: {{OldTargetEnd.toDate.diff(NewTargetEnd.toDate).days}} One more thing: when…

You have seemed to change the scenario, as you now want to test if the previous value was not empty. Please update the condition test on the {{fromString}} value from the change log and that should work.

Looking at the documentation, that function requires the Administer Jira permission, and so the token for the request would need to be for a user with that permission, and not one dynamically provided from another user.…

In that case, I recommend working with your Jira Site admin to contact Atlassian Support for this one.

Hi @Francisco Narvaez -- Welcome to the Atlassian Community! 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…

Hi @Ledith_Harrison Short answer: I suspect the pop-up's questions / fields for the Release Version action are meant to help teams decide what to do when there are remaining issues, and the behavior of that automation rule template is independent of that. Perhaps consider the team's working methods if there are challenges…

Please post an image of your current rule and the audit log details showing the entire rule execution. These may provide some context. The way your rule is currently structured, the audit log entry and comment will show the version information for the linked issues and not the trigger issue. Is that what you intended? Do…

Your rule image shows this: {{issuefixVersions.name}} but it should probably be this: {{issue.fixVersions.name}}

Hi @Samuel Sajasi -- Welcome to the Atlassian Community! Are you trying to accomplish this with an automation rule? If so... 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,…

Hi @Ravikanth -- Welcome to the Atlassian Community! I am using Jira Cloud, not Server version, but I found that gadget symptom listed in the public backlog for these two defects: https://jira.atlassian.com/browse/JRASERVER-65444 https://jira.atlassian.com/browse/JRASERVER-70634 The work-arounds in those suggest checking…

Awesome; I am glad to learn it is working!

Just to confirm when you write the {{varStakeholder}} smart value to the audit log inside of the branch, you see the email address. Correct? And if you write the entire URL for your request to the audit log (copying it directly from the "Web request URL" field in the action), does it look as you expect?

I wonder if the cause is a URL encoding issue for the Slack REST API call. Please try changing the request URL to use this for the stakeholder value: {{varStakeholder.urlEncode}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#urlEncode--

The time tracking fields are normally set with Log time (when changing an issue on a board) or with rule actions. For your scenario, do you want to set those fields, such as Original Estimate, for the new issues? If so, that must be done in two steps: create the issue and then set the field. For example: * action: create…

Hi @Ian Liu Rodrigues There is no built-in "days in status" field. It is dynamically calculated when shown in the UX for the board. And, when the sort order for the board filter is changed, this disables the ability to drag-and-drop to reorder issues on the board and backlog. Do you need that feature? If so, please change…