nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

asNumber smart value

unknown

Appreciate any help the community can give me.

I'm trying to do something that is seemingly simple. I want to automatically convert a string to a number. I have a custom field with data type of string called "Dev estimate" and I want to edit the Story Point field which is of type number. Unfortunately, it is both successful and not producing any results (namely, converting a string to a numeric).

Here is a screenshot of the automation:

Screen Shot 2021-04-01 at 1.20.51 PM.png

Accepted answers

All comments

Bill Sheboy

Hi @[deleted]

Some ideas to try:

If you log your custom field to the audit log does it contain what you expect?
Does the case of your smart value "Dev estimate" match the name in the field definition?
Have you tried to use the custom field ID instead?

Best regards,

Bill

unknown

Hi @Bill Sheboy

Thanks for your quick response. See below...

If you log your custom field to the audit log does it contain what you expect?
>>Thanks. I added a log and the field data is what I would expect. Unfortunately, the copy and conversion results in any pre-existing value to be (presumably) nulled out.
Does the case of your smart value "Dev estimate" match the name in the field definition?
>>TA: Yes, it does.
Have you tried to use the custom field ID instead?
>>TA: Yes, tried that with multiple versions of the custom field syntax (customfield_id, cf[id], name). If you know of a different syntax that will assure success, please let me know.

If you have any other ideas, I'll take 'em.

Thanks again, Bill!

Tim

Bill Sheboy

Hi Tim,

Thanks for the detailed answers! By the way, I should have sent this link before that has a how-to for confirming which smart values are available, based upon an example story:

https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/

Okay, let's try to diagnose this from both directions:

Is this for a Company-managed project (formerly known as Classic) or a Team-managed one (formerly Next-Gen)?
- Company... use the Story Points field
- Team... use the Story Point Estimate field
Please check the project's settings to see if you have one-and-only-one Story Points field within the scope. If you have multiple fields there could be a collision issue happening.
I wonder if there are some none-printing characters impacting the conversion. Please try this value, {{issue.Dev estimate.trim().asNumber}}

unknown

Thank you again, Bill.

We use Company/Classic and currently using the Story Points field.

We only have one-and-only-one Story Points field within the scope.

I configured my automation rule to use {{issue.Dev estimate.trim().asNumber}} but it didn't change the results so, I added more logging to capture the values before AND after executing the edit. It helped reveal what appears to be a bug. In brief, here is what I tried:

-directly edit the story points field to contain a valid value

-modify the value in the Dev estimate field

-modify the value in the Dev estimate field, again

-check the logs

It's interesting what happens...

For the first Dev estimate field modification, the story point value does not change.

For the second Dev estimate field modification, the story point value is nulled out.

I've attached the results of the log.

Thanks in advance for any insight you can give.

Tim

Screen Shot 2021-04-07 at 7.41.06 AM.png

Thomas Parish_pytz7r

Not sure if this will work for you, but I was trying to convert an integer number field (external portal ticket ID) to create the full URL for the external portal so it's clickable from the Jira ticket.

I was aware it could be tricky because Jira displays the numeric value as 54,321

Whatever I tried, the numeric ID was always returned as decimal with 1 dp, e.g. 54321.0, thus creating "https://externalportaldomain/tickets/54321.0" which isn't a valid URL so the rule was failing.

I appended my smart value with .round

"https://externalportaldomain/tickets/{{issue.customfield_12345.round}}"

and that's created it correctly as https://externalportaldomain/tickets/54321

Resource: jira smart values as integer - Search

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud