Bill Sheboy Expert

Hi @ChandraPrakash No, that is not possible with the built-in features. The backlog view is summarizing what is on the board (regardless of the columns and status values) when it shows the counts by Status Category values. Kind regards, Bill

A couple of other thing to try could be informed by first writing the value of the Start Date and Now to the audit log in that rule... Do you have people in different time zones transitioning issues? If so, you may need to convert both Start Date and Now to the same time zone before performing the difference so you can see…

First thing: I would create a test project to experiment with a rule like this. That can allow faster development and safer testing. When done, you may copy/edit the rule into the target project. This rule worked for me using the version's name when I explicitly selected the Project from the drop-down in the Release…

Two things to help... The time tracking features use the system settings for working days and hours, so it can help to log as minutes and then let the system do the rest. Next, when adding to timeSpent, the units of measure are required, such as minutes as "m". So perhaps try this in the JSON expression: "{{issue.Start…

To get you started on creating your rule, please review this documentation and examples: * https://confluence.atlassian.com/automation/jira-automation-data-center-and-server-993924595.html * https://confluence.atlassian.com/automation/smart-values-993924860.html *…

Hi @Claudio Rouillon Just to confirm, are you using Jira Cloud or the Server/Data Center version? It appears you are using Cloud, so... With this type of rule you do not use JQL with the scheduled trigger. Instead you only use the Lookup Issues action, and then there will be one email, referencing the {{lookupIssues}}…

Hi @Matthew.Anzano -- Welcome to the Atlassian Community! A few ways to do this are: * directly access the linked issues' status and types from {{issue.issueLinks}} using smart value, list filtering and then branch * branch to the linked issues in your rule, and then add conditions as needed * branch to JQL to find your…

Yes, and...the built-in "card color" only provides a tiny color stripe down the side of cards. "Flag" is the only exception as flagged cards fully highlight. There are many open suggestions to change cards' background color conditionally, such as this one: https://jira.atlassian.com/browse/JSWCLOUD-17278

Hi @Wonderful Life -- Welcome to the Atlassian Community! First thing, this is not a support channel. Instead this is a community of users helping others. I wanted to ensure you understand the difference between this area and the actual Atlassian Support team: https://support.atlassian.com/ Next, what is the purpose of the…

Hi @Vijaysundarraj Balasundaram -- Welcome to the Atlassian Community! Perhaps a different approach than a report/notification would be a dashboard with issues not updated in the last 24h, with a filter gadget on assignee. You could do your original request with an automation rule, however it would be limited to 100 issues…

Hi @[deleted] First thing, I am not using JSM and so am basing my ideas on the documentation... It appears the {{approval}} and {{approval.addedApprovers}} smart values are only available with the triggers for approvals: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--approval-- You may…

To detect assignment for a specific user, trigger on Issue Assigned, followed by a condition to check if it is the specific person of interest. Then you can notify when needed. For your other use cases, such as Issue Commented, use that trigger and again check if the assignee is a specific person. In my opinion...this…

After the lookup issues action, add a write to the audit log to check the value: {{lookupIssues.worklog.timeSpentSeconds.sum}}

Hi @Claudio Rouillon You cannot get the count by running a query directly with the Jira UI, but you can do so with other methods: * for Jira Cloud automation, using Lookup Issues with the JQL, and then check {{lookupIssues.size|0}} for the count (adding a default of zero to avoid nulls) * for Jira Server/Data Center…

Hi @Gary Spross My understanding is "Issue Color" is the replacement for "Epic Color", and that both only apply to Epics. This is the color epics display in their lozenges on child issues and on roadmaps, etc. And so this color can impact boards/backlogs when they show their parent epic's information on the card, swim…

Hi @Joshua Tilton To reference a version as a smart value for the Release Version action try using the id instead of the name: {{issue.fixVersions.last.id}} Also, do you ever expect there to be multiple fixVersion values assigned for this issue? How about no values? If either case applies please update your rule…

Hi @Valerie Prater -- Welcome to the Atlassian Community! Here are a couple of things to try... First, created variables are text. To use them as a number use asNumber to convert the value before math operations/functions. Next, smart values for fields are name, spacing, and case-sensitive. To confirm you have the correct…

For the automation triggers for versions (e.g. version released) you can access the same smart values as for a specific version within an issue field (e.g. {{issue.fixVersion.first}} As you note, not all of the version attributes are available from smart values.

Given the inconsistencies you are observing, I suggest submitting a support ticket for Atlassian to take a look. As the site admin for a paid license you should be able to do that here: https://support.atlassian.com/contact/#/

Thanks for that information. A few things I noted that could help... * The Issue Created trigger can fire very quickly, often before the issue is fully saved and available for a rule. This can cause conditions to fail, and other problems, in automation rules. The work-around is to add a Re-fetch Issue action immediately…

Please note I was suggesting to change the JQL for the branch and for the lookup issues. It seems you did not change them as I suggested, so please try that from my last comment. To be clear, the JQL for the branch could be: issue IN linkedIssues({{triggerIssue.key}}) AND issueType = Story And the JQL for the lookup issues…

That is interesting...During that time, did anything change for the scrum board for status mapping to columns, add/edit/delete of status values, or to the workflow? I would expect that some of those could reset the value, while no changes would lead to carry-over values from prior sprints. For myself and the teams I coach,…

HI @Ankush Mahajan -- Welcome to the Atlassian Community! The status values in Jira are configurable by administrators for your site. Please talk to your project admin (or the site admin) and they may help you understand the setup and meaning of your status values. Kind regards, Bill

Hi @Cesar Bastos For a question like this, please include images of your complete automation rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. For you Send Web Request action, did you enable the option to "Wait for response", and then check the…

I am glad to learn that it is gone now. For early warning, I recommend creating a global automation rule which monitors / triggers on the service limits / usage of your instance, and have it email the site admin when limits are about to be exceeded:…

Hi @Inna S Adding to the answer from @Fabian Lim you may use the following how-to article to find all of the smart values supported for an issue, including the details of release versions: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Kind regards, Bill

Hi @Daniel Havas Jira does not have a built-in way to assign issues to multiple users...which I find a good thing for accountability and work management. You seem to instead be describing notification. Two questions to clarify things: * How stable is the list of "other project managers"? Specifically, it is always the same…

Two things to check: Try running that JQL manually with advanced issue search (outside of the rule) to confirm it returns all of the issues you expect. Next in the rule, after the Lookup Issues action, write the value for the sum of the time to the audit log. Does it match what you expect for those issues?

Well...the JQL for that branch needs to be more specific to narrow things down...Otherwise it will try to yank in every story! Let's narrow that down to linkedIssues to the trigger issue which are stories: issue IN linkedIssues({{triggerIssue.key}}) AND issueType = Story Next for the advanced compare condition on the…

Hi @Craig Easton First thing: would you please post images of your rule and the audit log details showing executions which run as expected and others which do not? That may provide some context for the community to offer ideas. Thanks! Next, what is your Jira license level: free, standard, premium, etc.? There are limits…