Calculated Fields are a powerful feature of JSU which is used to calculate field values based on configured formulas.
Now, you don’t have to do complex and tedious calculations manually any more. With this feature, you can automate your field calculations without any scripting. It’s easy and handy to use.
They can be found in the left menu of Manage Apps in the Jira administration under JSU or as a standalone post-function in the list of JSU post-functions. Configure your calculated fields here by clicking on Create New Field.
Provide a field name on which you want to set the calculated value. it will create a new Number field.
Formula is the common mathematical equations that are used to calculate the field’s value. If you add another existing field to your formula, the value of that field on the same issue will be used to calculate the formula. If the value of the other field is changed, the calculated field will be updated automatically according to the new result of the formula.
Total Budget = “Per Person Budget” * “Person Count”
If you tick this option, the field will be automatically put on the relevant screens and other necessary configuration elements of Jira. In general it’s a good idea to leave this option ticked, so that you can view the calculated field value on the issues of the selected projects.
JSU will update up to 1000 of the most recently changed issues, which are still unresolved. The other issues' value will be calculated once a relevant field is updated.
Try it out
For example, Calculate the Gross Price which is Net Price plus 10 % VAT.
First create a Custom Field “Net Price” using Jira.
Now set up a formula using Calculated Fields configuration will look like:
3. Create a new issue and set the Net Price.
4. See the Result.
Supported Field Types
The Calculated Field in JSU supports many different field types. System fields, as well as custom fields which are of Text and Number type. Text fields will be converted to numbers. If this is not possible, they will be treated as if they were empty.
We recommend that you test JSU with fields which are relevant to you. Our evaluation license gives you 30 days free trial.
Newly created calculated fields are ‘read-only’ fields. This means that their value cannot be edited manually and can only change as a result of a change in the formula.
We do not use Jira’s ‘read-only’ fields for this purpose, but number fields, in order to provide you with more powerful search capabilities. Additionally, JSU will automatically configure your screens, so that the calculated field is only visible on the screen for the ‘View issue’ operation, but not for the ‘Create issue’ & ‘Edit issue’ operations, since it’s not editable.
In order to achieve this ‘read-only’ behavior, a new screen will be created for the ‘View issue’ operation. The default screen is simply duplicated and assigned to the ‘View issue’ operation of the screen scheme with the indication “Calculated Fields copy” and the calculated field will be assigned to this screen.
For screens used by multiple operations (create, view, edit), we check if the 'View issue' screen is used in any of the other operations. If yes, the screen is duplicated and assigned to the view operation.
If you prefer to have full control of your screen configuration, feel free to uncheck the option of including the calculated field into your project’s screens when you create or update a calculated field. You can then set it up manually so that it fits best in your environment.
For more information about Jira screens configuration, please check here.
Calculating fields might take longer than expected, especially when affecting several issues at the same time. The system can process up to 1000 requests at the same time when re-/calculating fields.
In order to avoid system overload, we introduced the system load bar in the overview page of Calculated fields to let the user know about the status of the system.
It is supported by an error message when the user tries to create a field with number of requests to be processed exceeding 1000, which asks the user to try the operation later after the system processes the current requests.