Sumit's answer gives you a script field on an issue. This is a solution you've been told several times already, but ignored.
It does not happen in the workflow. If you want to calculate a field in the workflow, then you need a post function (again, something you've been told several times before).
The question that you've refused to answer in other conversations remains what you actually want from this calculation. Is a scripted field on an issue what you want? Or a field you can edit after an initial calculation is made? Or a field somewhere else?
That is not what you said on the other conversation. You said they should be read only. If you want them editable, then you need a post-function to calculate the value and put it in a field which the user can then change later. We've answered the total thing too - the navigator does not support that, you'll need an add-on.
Use calculated number field :
formula should be
<!-- @@Formula: (issue.get("customfield_XXXXX") != null ? issue.get("customfield_XXXXX") : 0) + (issue.get("customfield_XXXYZ") != null ? issue.get("customfield_XXXYZ") : 0) +(issue.get("customfield_XXXYZU") != null ? issue.get("customfield_XXXYZU") : 0) -->
it will work everywhere within JIRA [so no transition restriction will be applied]
XXXXX – ID of calculated number field which shown sum
XXXYZ – First Number field
XXXYZU – Second Number field
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs