Jira Automation: Unable to set Original Estimate

[Neil Poska]

I have a very simple rule to set Original Estimate based on the sum of a couple custom fields. It is failing saying that Time Tracking is not available:

All searches on this site that are similar say that Time Tracking needs to be available on the screen, but it is and so is Original Estimate. I can manually set the value and log time.

Here is the simple rule:

Am I missing something obvious? Any suggestions would be greatly appreciated.

Thanks.

[Bill Sheboy · Accepted solution]

Hi @Neil Poska 

The error messages in rule audit logs do not always indicate the actual problem...

First, your math expression syntax is incorrect.  Perhaps try this in the field, substituting in your fields and assuming they are all number fields:

{{#=}}{{issue.customfield_12345}} + {{issue.customfield_67890}}{{/}}h

If that does not work with the Original Estimate selected from the dropdown list, the same expression could be used with a JSON edit, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Time-tracking-and-logging-work

Kind regards,
Bill

[Neil Poska]

That fixed that part of it! Thanks!

But now it sounds like Original Estimate can not be added to advanced plans (?), and I can't get any other custom fields to roll up, so this path might have come to an end?

[Bill Sheboy]

Automation rule can update issues (i.e., work items) or other things which have a REST API endpoint to access them.

Your original rule showed updating an Issue.  If instead you are trying to update information stored in the Plan, the REST API would need to be called with the Send Web Request action.

[Pasam Venkateshwarrao]

@Neil Poska In Advanced Roadmaps(Premium Plan) you can do it 

Configure Advanced Roadmaps 

Go to:

Plans → Plan Settings → Customize view
→ Scroll to Custom fields→ Enable your custom estimate field
→ Make sure it is aggregated (you'll see a "Σ" icon when it's being rolled up)

This will now sum up values from child issues (e.g., Stories → Epics) using your custom field instead of Jira’s time tracking system

Hope this helps

[Neil Poska]

I'm sorry, you lost me. What do you mean by 'make sure it is aggregated'? 

I have a numerical custom field (TotalEstimate) and it is already in the plan, and the plan is already set to use hours instead of points. I see no Σ anywhere where it should be rolled up, or anything in the plan settings or field definition where I can make sure it is aggregated. And changes I make to the plan are definitely not getting rolled up to Epic or Initiative level.

I think we are close to a solution here... can you give me a little more detail?

Thanks.

[Pasam Venkateshwarrao]

Hi @Neil Poska 

Welcome to the community,you can set automation like below

Trigger: "Issue Created" (or any trigger you want)

Action: “Edit issue”

• Click “Add action”
• Choose “Edit issue”
• chosse the field
• At the bottom, click “More options”

Use Smart Values :

{
"fields": {
"timetracking": {
"originalEstimate": "{{issue.customfield_12345}}h"
     }
  }
}

  or if you want to use JSON

Paste this in the JSON section:

{
"fields": {
"timetracking": {
"originalEstimate": "2h"
    }
  }
}

Hope this helps

[Aaron Geister [Trundl]]

@Neil Poska

Welcome to the community. I can see how this can be confusing. When they say "on the screen" this means in the configuration screen. You would need Jira admin or product admin access to validate or update this. Also note that on the screen you might need to add Time Tracking as that is not always there. 

If you go to the settings cog > Issues > Screens, than you would look up the screen name for the project. This is usually found in the Project Settings > Summary. If you are in the Summary you can navigate to the screen from there. Or you can use the first way I pointed out. 

I hope this helps. Again you do need product admin access aka Jira admin. Once you add the fields to the screens then you should be good. 

[Neil Poska]

This worked, but now I have a new error:

I am trying to set Original Estimate to the sum of three number fields. Do I need to do some sort of conversion from number to time or something?

I added a intermediate variable to make thing a little more readable, so my rule now looks like this:

Related question: the reason for this exercise is that my boss wants to use the result of this automation to be able to roll/sum up values to parents in a Plan. Is there a custom field type that can do this better than fighting with Time Tracking fields?

Thanks.

[Aaron Geister [Trundl]]

@Neil Poska As was stated by @Pasam Venkateshwarrao  using advance roadmaps and sum up by time tracking when you configure your plan will get those results to role up to the epic. Then you just need to add the fields to the plan. This will give you the results your looking for. Make sure you configure your plan to use time and not points. 

[Neil Poska]

I already had the fields added to the plan and set to use time not points, but the automation still fails with the 'Enter a vaild value" error above. I tried adding a regular numeric custom field to the plan (the automation works perfectly for this field since it is not Time Tracking), and I see it perfectly, but it definitely does not roll up values to Epic or Initiative level.

What do I have to do to make my numeric value a valid value to Time Tracking? I tried {{totalEstimate}} and {{totalEstimate}}h.

If I go with my regular number field where the automation works, what do I have to do to make sure it rolls up value sums to Epic and Initiative level?

[Neil Poska]

Just did more research, and do I need to write automations all over the place to get numerical values to roll up? That does not seem optimal at all, especially considering the original reference to a Σ icon.

Roll ups are definitely correctly selected in the View Settings dialog.

[Aaron Geister [Trundl]]

@Bill Sheboy  as answered your question with this:

{{#=}}{{issue.customfield_12345}} + {{issue.customfield_67890}}{{/}}h

The math expression was off and that is the reason that it was not calculating correctly. As Bill stated the logs don't always tell you what is not correct. {{#=}} and the h at the end are both needed for the system to actually calculate your expression.

I believe you should update your expression to include what Bill had stated. If this helps please make @Bill Sheboy answer has correct. 

Also I do believe if the Plan is set up correctly it will rollup but if you have a custom hierarchy it might break that rollup.