Bill Sheboy Expert

Hi @Raúl Eduardo Echeverría Urbina For questions on automation rules, please post images of your complete rule and the audit log details, showing the execution. That will provide context for the community to offer suggestions. Thanks! From what you have shown thus far... To perform division you may either use the slash and…

Hi @Suzy Nicholson Two possible things to check on this one: Please see your other question on this topic, as there is an open suggestion indicating problems with the People field's email address…

Hi @Suzy Nicholson Yes, and...to John's answer: Here are a couple of the open suggestions to make People fields available in automation rules. * https://codebarrel.atlassian.net/browse/AUT-1651 * https://jira.atlassian.com/browse/JSWCLOUD-22200 Kind regards, Bill

Hi @ola ogunsola First thing, what is your Jira Cloud license level: free, standard, premium, or enterprise? * These levels have different limits on the number of global rule executions per month: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/ * The rule you describe could quickly…

Hi @Jason Chan Please take a look at this documentation, and then use your field on reporter's email address in the IQL query with Lookup Objects to get at the data: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-insight/#SmartvaluesInsight-Lookupobjects Kind regards, Bill

Hi @Deborah Ciampá This could be a timing problem (i.e. racetrack error). The Issue Created trigger can fire before all of the data is available for an issue...and so your conditions fail in the rule because the Country is empty. The work-around for this symptom is to add a Re-fetch action immediately after your trigger.…

Hi @Urmo This seems to be a question about an automation rule. If so, please post images of your complete rule and the audit log details showing the execution. That may provide more context for the community to help. Thanks! Regarding your questions... What i should set to get under this…

Hi @Kristine Lurane What problem are you trying to solve by doing this? I ask, as you note using a Company-managed project (CMP), and those use the "Story points" field. The Team-managed projects (TMP) use the "Story point estimate" field. All of the built-in handling and reporting of story points for the project types…

Hi @Finn Harsfort I believe you can do this with a single math statement and the filtering of smart value lists feature: * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ * https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 *…

Thanks for that information. For your use case, there are a couple of approaches: * Conditionally process the components: use an if/else condition in order to handle the cases of "none" or "some" initial component values. The different paths will lead to different actions for the additions later. * Add a "placeholder"…

Given that information, I suggest going to that link I provided for defects and submitting a defect to the vendor. They may notice something which is causing this symptom. https://bitbucket.org/StonikByte/great-gadgets-add-on/issues?status=new&status=open

Hi @Jason G Please try converting the text string to a date value first, such as with: {{smartParsedDate.toDate}} Kind regards, Bill

Hi @Jira Gal -- Welcome to the Atlassian Community! Perhaps try the built-in pie chart gadget, with a filter which only returns over due issues: project = myProjectName AND statusCategory != Done AND due < startOfDay() Kind regards, Bill

Did you select the same board, and the same sprint filters, with your new dashboard versus the original one? And, if you expand the data table entries (by sprint), do you see what you expect for the sprints?

Hi @Clay Nichols -- Welcome to the Atlassian Community! When you create the sprint, do you know the start date? If so, why not just type it in at that time? You could do this with an automation rule and a call to the REST API, perhaps triggered on sprint start, but that seems a bit complex for this need. Kind regards, Bill

Hi @Meagan Hiatt Yes, and...to Trudy's answer: If you are not setting the Resolution as part of your workflow, you could instead use the statusCategoryChangedDate. This field would be set as soon as the issue changes statusCategory for any status, such as to "Done" Kind regards, Bill

Hi @Jay Dubinsky -- Welcome to the Atlassian Community! Two things of note: Please try the replace() function to substitute your spaces for underscores: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#replace-String-target--String-replacement- And, when using the edit issue action, either…

When I hear "deadline", I suggest using "want date" instead...and then explain the history of the term "deadline". The PMO folks do not like it when I do that :^)

Hi @Timo Vertanen First a suggestion: please consider using one of the free browser addons (or a screen-capture tool) to capture a scrolling browser window. That will help to capture your entire rule in one image, making it easier to see what is happening. Next, your use case is different from the original one in this…

Hi @Raul Herrera -- Welcome to the Atlassian Community! Throttling for automation rules usually tells us there is something happening with the way our rules are constructed or triggered, and/or exceeding our licensing levels for rules. I recommend working with your site admin to review the audit logs to learn which rules…

Hi @Karyna Tyrnavska _SaaSJet When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Hi @Timo Vertanen For some context, would you please post an image of your complete rule? That may help with suggestions on how to improve it. Thanks! Kind regards, Bill

I am unclear how to do that. Would you please clarify the problem you are trying to solve by limiting project access after a field changes? And, what does "limit access to the project" mean to you? Perhaps if you update your question to address those things the community will have more ideas how to help. Thanks!

I am currently only using the JSON ones. Probably worth some searches for JQL and others support, so I'll look around a bit.

Hi @Raghu -- Welcome to the Atlassian Community! Yes, and...to Trudy's answer: For teams using Kanban practices, and in my opinion, very few of the common/helpful measurements are supported (or supported well) by out-of-the-box by Jira. Pause to consider what your team needs, and then perhaps try dashboard gadgets,…

Hi @Martin Cleaver I added this suggestion to improve automation rule validation, and sadly it has moved to the dreaded "Future Consideration" status: https://jira.atlassian.com/browse/JSWCLOUD-22692 For complex smart values and JSON, I write them initially in tools like Notepad++ so I can use the syntax highlighting and…

Hi @Erna Putri Utami Based upon what you are describing, it seems you could do this all in one rule when the issue is transitioned into in progress. If not, please consider posting images of your complete rule and the audit log showing the details of the execution. That may provide more context for the community to offer…

Hi @prakash Would you please clarify: are you asking if a new version can be created (which Trudy answered) or if you can name the version to the next month, after the released version's date/name? Kind regards, Bill

Hi @Maahshid Vaziri Context is important for smart values like Project: * {{project}} by itself works for project-related triggers, and * when you have an issue trigger/branch, you instead use {{issue.project}} Which of those applies for your rule's trigger? Kind regards, Bill

Hi @Puneet Mehresh -- Welcome to the Atlassian Community! One way to do this is with an automation rule, gathering the subtasks for the parent issue, and then progressively checking for any in each step of your flow. For example: * trigger: issue transitioned * condition: issue type is subtask * action: use lookup issues…