Bill Sheboy Expert

Hi @Mike Vitale Smart values are name, spacing, and case-sensitive. And when they do not match a known value, they evaluate to null and often silently fail to work as expected. Your condition at the start of the branch is referencing {{Work Participants.accountId}} but that does not match your branch variable of…

Hi @Kalai After you start typing in the time information (e.g., Time spent) the date fields will appear below for optional entry. Kind regards, Bill

Happy New Year, @Jaqueline da Silva Nicolau I have not used JMWE, and cannot answer that. You could copy the field with the built-in Automation for Jira rules. Please look here to learn more about that feature of Jira Cloud: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Hi @Asser Abdelaziz -- Welcome to the Atlassian Community! Adding to Jack's answer: Custom fields in team-managed projects are specific to each project...even when they have the same names and values. I recommend testing to confirm your rules work as expected after copying them. Some ways to do that are: * For rule…

Hi @Anastasiia Tsvetkova For a question like this, please post complete images of the rules involved, and the audit log details showing the rule execution. Those will provide context to help the community offer suggestions. Thanks! Until we see those... It appears you have one rule which is using the Release Version…

Hi @Kevin Ulland There is no indication in the help pages of the idea order on the right-side of the Matrix View: https://support.atlassian.com/jira-product-discovery/docs/what-is-the-matrix-view/ My quick experimentation shows it appears to be the built-in Rank ordering of the ideas, as they are displayed on a List View…

First thing, I recommend removing the "fields." prefix as it is not needed. Next, for the field you describe as a labels field type, that will be a list. Just providing the field name should be sufficient to produce a comma-separated values list: {{myLabelsField.value}} Finally, I am unclear what you are trying with this…

Hi @Juergen Holzer 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 @sacha_rouzkhosh Adding to Fabian's answer: I recommend first writing the smart value expressions to the audit log before trying to set the label values. That will help confirm they work as you expect, and isolate any problems so they can be fixed first. Kind regards, Bill

Thanks for the rule image, Chris. I see you are trying to use single-quotes within the replaceAll() function, with that then nested within double-quotes for the JSON expression. That will not work: those all need to be double-quotes within the smart value expression. One work-around for that is to perform the replacement…

Hi @Chris Case 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 @Rahul Jith Smart values are name, spacing, and case-sensitive. And often the smart value does not match the displayed field name on the issue views. The how-to article below helps to identify the correct smart value (and custom field id) for any supported fields for automation rules. The essential steps are: * identify…

Hi @Todd Skelton Short answer: the rule you describe may not be possible as it appears to span multiple projects, and because automation rules have a processing limit of 100 issues for triggers it may never update some issues. Longer answer, and some work-arounds: The way your rule is written, the condition compares issues…

Hi @Aftab_Akhtar This seems to be a duplicate post of your other question. Please use the other one to avoid splitting up answers from the community. Thanks! https://community.atlassian.com/t5/Jira-Content-Archive-questions/Automatically-release-a-version/qaq-p/2567403 Kind regards, Bill

Hi @Aftab_Akhtar Your rule's trigger is for "Version Unreleased", but you describe releasing on a schedule. Perhaps try the Scheduled trigger instead: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Scheduled For your second part of creating a new version, based on the name of version just…

Hi @Dennis_H For scenarios when you want one email for something, try this without JQL in the scheduled trigger. Instead, only use the Lookup Issues action to rollup the results. And just to confirm: did you want to check for "in this status for more than 5 days" or "not updated in last 5 days". If it is the first…

To use the built-in gadgets, the issues must contain the data you need, not the parent of the issue. Keeping with that structure, you could: * investigate marketplace addons which are capably of that type of reporting * copy the developer information to the child issue (i.e., Bug) to use the built-in gadgets As a follow-up…

Thank you for that information. Have you tried what Danut M suggested using your custom field, except inverting the axis selections? For example: * using a saved filter which only returns Bug issue types * use the Two-Dimensional Filter gadget with the x-axis as Issue Type and the y-axis as your Developer custom user field?

Hi @藤野　珠輝 -- Welcome to the Atlassian Community! Rather than using an if / else structure, you can simplify your rule to use a Created Table, Created Variable, and Advanced Branch. For example: * action: Create Lookup Table, with a row for each user. The "key" would be their account id and the "value" would be their Slack…

Hi @Quinn Campbell Adding on to the other answer suggested, I have a question: What problem are you trying to solve by automatically transitioning issues based on time? That is, "why do this?" Understanding that will help the community provide better suggestions. Thanks! Kind regards, Bill

Hi @Jaqueline da Silva Nicolau Adding on to the answer from Danut M... You note measuring "bugs that a developer created". How do you know this information? Is it the user who created the issue (i.e., Jira field Creator), or some other field? You note it is not the Reporter or Assignee? Kind regards, Bill

Hi @Nagarjuna Busireddypally Yes, that can be done with an automation rule. The rule would be triggered on work logged, check that the issue type is B or C with a condition, and then branch to the linked issue A to add the same work logged with an action. I recommend trying to create your rule, and if you run into…

Hi @Kaitlyn Vu -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud and not the Data Center version. And so my answer is based on what I know of automation rules. Please test what I suggest with your version of Jira. Thanks! In your rule you are using the {{fromString}} smart value for the field, and…

Hi @Jasmeen Bajracharya What you describe may be possible, but it is risky for an automation rule to process this. You describe updating the Start Date and Due Date for linked issues, in a chain of issues. This is similar to what a project management tool could do. For example: KP-15 links to -> KP-16 links to -> KP-17…

Hi @Harut Avetisyan I do not believe that type of query is supported with the built-in features of JQL. Your possible work-arounds depend upon how frequently you need to do this type of query and your willingness to spend money: * need this one time* Export the issues to a spreadsheet and perform the additional filtering…

Hi @DLLPGF First thing, rather than add on to this older post, I recommend creating a new question and linking back to this thread. Otherwise only the people following this one will see it to contribute ideas. When you post the question, ensure you include your Jira version (i.e., Cloud, Server, or Data Center), your…

Hi @idan farbman As you appear to have also posted this question in the Atlassian Developer Community, I recommend waiting for the response there. That location is more likely to provide application development suggestions. https://community.developer.atlassian.com/t/how-to-select-a-jira-project-from-a-drop-down/75764…

Thanks for the additional information as that leads to some other questions / insights: You originally described copying labels from an Epic to its children Stories. And then you want to further copy those labels to any Test or Bug (defect) issue types which are linked to those child Stories. In automation rules, branches…

Hi @Aron Kurovski de Castro Paiva -- Welcome to the Atlassian Community! Have you considered having a conversation with each individual, to learn where they believe they need to improve based on expectations for the team, and perhaps supplement that using data from the built-in control chart? Using a quick-filter on…

Hi @Valeri Rozenberg -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer better suggestions for the scenario. Kind regards, Bill