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

Using effort in a weighted formula

I want to build a formula that helps me identify features that are "high impact" and "low effort". Therefore, I would like to build a weighted formula that takes into account "Score" and "Effort". Where:

  • Score: Higher is better
  • Effort: Lower is better. (1 "dot" better than 5 "dots")

Right now as implemented for weighted formulas, both are calculated/normalized to be "higher is better".

6 answers

1 accepted

0 votes
Answer accepted

Hi everyone, this change is coming up soon. Note that you can also use a "write your own" formula to do that today.

Screenshot 2023-01-03 at 14.48.01.png

Do you have an estimated date when it will be rolled out? It's a bit silly now to have the effort score in reverse order (e.g. 1 dot is high effort and 3 dots is low effort) 🙈

We don't generally share release dates.

In the meantime, you can try:

  • using a negative input? (e.g. "-100" for effort)
  • using a custom formula ("write your own", e.g. "{Impact}/{Effort}")

What we're going to ship here is basically a convenience UI to achieve the same result

Thanks! I will try the negative input

It's really needed feature that you can select if value is positive or negative (if number 5 is good or bad thing). We are missing a lot if we can't use weighted score with rating fields when using impact vs effort (or other similar) framework

1 vote

@Seth Mason : what @Jonathan Hau said!

Here's a demo:

Also, you can use negative numbers in the weighted score (e.g. impact = 200, effort = -100) but I'm not sure how mathematically accurate it is. We've seen users doing that though

I think this can be easily solved by writing an Expression that inverts the value of the weighting in the calculated score. Or divides by effort. For example if using RICE scoring model: 2* (([Reach]+[Impact]+[Confidence])/[Effort])

I also came across the same issue.
As is
- I'm currently using the values of the effort field in the oppoosite (wrong) direction in order to make the calculation right.  

To be
- User should be able to indicate whether a criteria is contributing to the score in the positive or negative direction

Just came across the same issue, if not using RICE this solution isn't really helpful. I agree with Riku that you should be able to indicate if a scoring field is positive or negative. 

Where impact score includes effort, the lowest effort should be able to be weighted highest if required.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events