how do teams ensure numeric accuracy during servre to cloud migration?

[ALI SAIFULLAH]

In the middle of a Jira Server to Cloud migration. We're confused how do we deal with numeric values that mean something in the real world.

Jira stores numbers, but doesn’t seem to know what unit or system those numbers belong to.

Is there any built-in way in Jira to standardize this during migration, or is it completely on the us to verify units & values across different regional unit systems? 

[Trudy Claspill · Accepted solution]

Hello @ALI SAIFULLAH 

You specified that you are in the middle of a DC to Cloud migration.

You also brought up the use of numbers in your data.

You raised another topic about Jira understanding the contexts of the numbers.

Are you concerned about the data being migrated accurately, or are you concerned with how the data is interpreted in Jira DC vs. Jira Cloud?

Based on my experience, natively Jira DC and Cloud have just a simple Number custom field. There is no inherent context for what that number means. If you want Jira to handle those numbers based on the understanding that they are a certain unit of measure then you have to customize Jira appropriately for that. There is a new option in Jira to sub-classify a number field as number, percentage, or currency.

Assuming that you are using the native custom Number field in Jira DC, then during the migration those numbers should migrate as is to the same field in Jira Cloud.

You said you need to use metric vs. U.S. units interchangeably, and calculation errors are happening. How are you using these units interchangeably in Jira DC? Are the values being used by automated processes or people? How are the values getting set; by automated processes or people?

Are you trying to figure out if there is a solution in Jira Cloud for a problem you've been having in Jira DC?

Without a better understanding of your current implementation, and of the question you are trying to ask, it is challenging to offer advice. 

Your users need to put in the correct value for the specified units. If you tell the users the field is for liters and they put in values for gallons, Jira cannot fix that. You could potentially create multiple fields, one per unit of measure, and implement automation so that when one of the values is changed then the other values are recalculated to show the new value in their own units.

[ALI SAIFULLAH]

Now I get it best👍.

Previous answers emphasized proper guardrails and verfied table conversion charts to display in front of team managing fields.

I was just thinking about how to apply the guardrails. You've perfectly showed how I'm going about doing this. 
1. Multiple fields.

2. One field per unit of measure.

3. Then automation so that team stays away. No one puts gallon values in place of liters.

Definitely this is what was I looking for.

Thankkyou for taking time to answer my question. You gave a full applicable answer. I'm glad I postted the query on atlassian community. people are genuinely helpful here. 

[Danish Bashir]

you're right! Jira doesn’t actually “understand” real world units. Here you're just storing numbers. The meaning of those numbers (hours, capacity, volume) will entirely be defined by your team handling fields. 

What’s worked for us is being very explicit:
1. clear field descriptions

2. shared documentation

3. post-migration accuracy audit

Teams double-check values instead of assuming everyone reads them the same way.

[ALI SAIFULLAH]

Those're pretty useful insghts @Danish Bashir . 
I am working on projects where Metric & US customary system units needs to be used interchangibly. we're tracking liquid products in jira that need to be sold in Canadian & US markets.

Calculation mistakes are occuring mostly in volume units. for 1 product we need to manage quantities in liters , ounces vs a bunch of different type of gallons😑. 

Please elaborate over this. 

[Danish Bashir]

That is justtt a small part of problem. You're not understanding. Units and Measurement systems will be 1 time taught to your team managing jira project. Mistakes in values & their units will keep surfacing unless you make your jira workflow explicit, clear & adopt post-audit practice. 

[Danish Bashir]

For your concern about volume conversion. Display accurate, expert verified charts showing repeatedly used liter values converted to ounces, galones. For new values, direct your team to a ounces & gallons to liter convertor .This is how we do it. 

Jira won’t enforce numeric value & units accuracy for you. Like us, you'll have to put 'accuracy & precision' into how teams use it.

What actually keeps things stable is making unit meaning explicit in field names and workflows. Also validate numbers & units at transitions so bad assumptions don’t flow into automation, reports, or exports.

[Eddie Jones]

maybe Jira brings something to handle this in future. so that users are relieved off this confusion.

[ALI SAIFULLAH]

yeah got the point. I'll display unit conversion charts , if possible make my team sit an extra hour😐 and get them to cram the unit values. I really want to get rid of mistakes that later come in front of me in the form of blunders.

[Eddie Jones]

Realistically,

Jira won’t protect you from numeric mistakes unless you design guardrails around the data. And. Once numeric values & units move into reports, scripts, or external systems, Jira has already lost all context. Even you allow small in-accuracy to flow.

Imagine what happens if automation takes place and downstream usage on exports & integrations.

With guardrails, keep a verfied set of unit conversion charts easily accessible to the teams.