Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

"Roll-up" custom formula type: normalized, or not?

The documentation describes that Roll-up custom formulas apply "normalization".

The normalized value x for a field is defined as 100 * (x - min) / (max - min). where min and max are the min and max values respectively across all the ideas. Hence, the max value will be interpreted as 100 and the min value will be interpreted as 0.

I've checked roll-up with several different inputs, and never saw normalization applied. For example for a rating field:

Screenshot 2022-10-11 105025.png


Is this a bug in the formula implementation, or in the documentation?

1 answer

1 accepted

2 votes
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 11, 2022

Hi @Jan-Hendrik Spieth , it's a problem in the documentation - the roll up just adds the values. If you want normalization, you can use a  "weighted score" formula

Thanks for the info, got it! I think it makes more sense this way, indeed.

Btw: normalization would be a useful addition to "custom" custom formula expressions.

Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 11, 2022

@Jan-Hendrik Spieth thanks. What you can do is create a formula field / "write your own". Then create another one (formula / "weighted score") that has the first one as an input. That will give you a normalized value. 

Thanks @Tanguy CrussonYes, using a weighted formula field is an effective workaorund.

I would still prefer to be able to use a normalize function in a custom formula. Some reasons come to mind.

First and foremost, I don't like adding fields that have no real meaning/semantics/purpose, in the "human" sense.

Right now, each and every fields is available in the idea sidebar (and filter/grouping dropdowns, etc pp!), and thus potentially confusing/annoying regular JPD users.

Like these two that I created merely for "investigating" rollups vs weighted formulas:
Screenshot 2022-10-11 135851.png

Polluted filter dropdown:
Screenshot 2022-10-11 141801.png

Without these kinds of prefixes ("exp", "wip", "debug", "calc"), I would already lost with all my fields ... ;-)

This is totally ok in a beta, if you ask me. (And for educational experiments, I could lateron create a separate JPD project). But for production use, I would really like to keep the number of fields that are available to my stakeholders as low as possible, and limited to only what they have to really work with.

If Atlassian allows us to "classify" fields, as in fields for productive/interactive use, hidden fields, or so, then ok. Maybe you have sth like "custom field schemes" on the roadmap already. (Now that I think about it, I hope you do! One would certainly want to share fields across JPD projects ...).

I hope that makes sense.

Long story short:
If JPD allows me to mark/hide fields that are merely used for intermediate calculations, and hide them from JPD users, the workaround is ok. Otherwise, not so much.

Like # people like this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events