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; } } }

How to create a field that is defined as a calculation

Holly Rademacher

Is it possible to have a field that is calculation based on the number of days the work item has been opened and the severity? Number of days opened * a predefined value based on severity.

For example - If the work item has been opened for 10 days it would show the following values based on the severity of the work item:

Sev 1 (number of days opened * 10) = 100

Sev 2 (number of days opened * 8) = 80

Sev 3 (number of days opened * 6) = 60

Sev 4 (number of days opened * 4) = 40

Thank you - Holly

Accepted answers

All comments

Bill Sheboy

Hi @Holly Rademacher

Atlassian is currently building a feature for calculated, custom fields. You may watch / vote for that item to see progress here: https://jira.atlassian.com/browse/JRACLOUD-61966

Until that is available, you could...

Use two automation rules (one triggered on work item create and another on source field changes) to calculate the value
Investigate any Atlassian marketplace apps which provided scripted / calculated fields

If you need more suggestions on creating the the automation rules, please let the community know. Thanks!

Kind regards,
Bill

Stephen.Lugton

Hi @Holly Rademacher

If you were to go the automation route that @Bill Sheboy mentioned, the severity would only be updated when the ticket is created, which would potentially set the severity to 0, or when you update a specific field on the work item.

If you want the severity updated daily, as your calculation would imply, I would suggest using this trigger for the automation:

Scheduled: Could be daily / weekly, with a branch for all work items that meet specific criteria, e.g. statuscategory != Done AND issuetype = Task

If you're ok with the severity being updated on request, you could use this trigger:

Manual: when someone wants to update the severity they can manually run the automation to update that ticket only

Bill Sheboy

Hi @Stephen_Lugton

Please re-read my post as I describe two rules:

Use two automation rules (one triggered on work item create and another on source field changes) to calculate the value

Kind regards,
Bill

Stephen.Lugton

Hi @Bill Sheboy

So the work item create trigger sets the severity when the work item is created, and the source field change sets the severity either straight after the work item is created (i.e. when the field first changes) or when the source field changes.

I may have misunderstood but any changes made by the automation are static changes, which means that there will be no change to the severity if there are no field changes after the initial work item creation / field change unless the source field changes.

But the calculations require the number of days since the work item was created.

I'm suggesting ways to update the severity without changing the source field, i.e. by scheduling an automation to run at a regular period that will pick up the number of days since the work item was created, or by running a manual automation to do the same thing.

Stephen.Lugton

Both a create work item trigger (or field change trigger) and a scheduled trigger would be needed to keep the calculation up to date; looking back at my original post I didn't make that clear.

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-cloud