Metrics automation with custom fields

[Victor Fairen]

Hi community,

We are trying to define automation metrics for projects in Jira Cloud and Confluence and I got stucked wih some fields. 

• First problem:

We are trying to implement this automation to track the timing of projects. So we have created a custom field named "Time" with three colored fields (yellow, green, red) which will be automatically changed depending on the due date and the field work ratio. However, the work ratio cannot be used in the automation.

Any idea of how can we track the timing taking into account we need the due date and the progress of the issue?

	due >= “14d”	due <= “-14d”	due <= “0”
Work ratio > 100%	yellow	yellow	yellow
Work ratio = 100%	green	green	green
Work ratio > 81% AND Work ratio < 99%	green	yellow	red
Work ratio > 61% AND Work ratio < 80%	green	red	red
Work ratio > 41% AND Work ratio < 60%	green	red	red
Work ratio > 26% AND Work ratio < 40%	green	red	red
Work ratio > 1% AND Work ratio < 25%	green	red	red
Work ratio = 0%	green	red	red

• Second problem:

We have two numbered custom fields (estimated CAPEX and actual CAPEX) which is manually updtaed by the Project Managers. As in the previous problem, we've created a new custom field named "Budget" with the three colored options which would be automatically changed by the difference of both fields. As well, this automaiton cannot be done by automation.

Budget is green if "CAPEX (real)" < "CAPEX"

Budget is yellow if"CAPEX (real)" = "CAPEX"

Budget is red if "CAPEX (real)" > "CAPEX"

Any idea of how can we track the difference of estimated and real CAPEX on this?

Many thanks in advance!

Anna

[Bill Sheboy]

Hi @Victor Fairen 

First thing, for a question like this please post images of your complete automation rule and the audit log details showing the rule execution, describing what is not working as you expected.  Those will provide context for the community to offer suggestions.  Thanks!

Until we see those...

I checked, and both work ratio and the source fields to compute it are available for issues in Jira Cloud automation rules.  What have you tried that is not working?

For your second concern, if you have added custom fields they will be available to automation rules.  The challenge is often determining the correct smart values to use.

Smart values are name, spacing, and case-sensitive.  When an incorrect smart value is used, there often is no error and the value is substituted with null.  To identify the correct smart values for your fields, please try this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Victor Fairen]

This would be the matrix automation for the first problem: 

And this the second one: