Allow custom field/feature values to be fed into scorecard

It would be useful to be able to expand the advanced scorecard functionality to dynamically pull values from other fields in Aha!

Primarily, allowing people to have an estimate value in their score card and have that value pull/push to an estimate value on the feature card.

  • Danny Archer
  • May 6 2015
  • Likely to implement
Release time frame
  • Attach files
  • Jason Slaughter commented
    May 7, 2015 21:05

    The example I think would be most useful is to automatically set the "Effort" slider based on the "Effort" field in Aha! (for example, the story points).

  • Paige Richbourg commented
    May 15, 2015 17:49

    This would also be helpful if you wanted to import from a spreadsheet and include these fields to set the scorecards.

  • Admin
    Chris Waters commented
    May 15, 2015 22:47

    Would it be useful to have a custom field which can be an equation that produces a result based on other fields or score card metrics?

  • Jason Slaughter commented
    May 19, 2015 14:53

    Chris, that could be useful, but it seems confusing to me. How would this work in the UI?

    The way I envisioned this feature was that in the scorecard editor it would be possible to pull certain fields from the feature (in my case, the "effort field") as inputs into the scorecard equation.

  • Jamie Burr commented
    June 4, 2015 20:34

    Good example: I would like to take the current Vote count on an idea and use it as a multiplier in the Score for that Idea.

  • Brian Campillo commented
    January 28, 2016 14:13

    Need this ASAP!

  • Thomas Dhollander commented
    February 23, 2016 02:19

    I would like to use the following: Effort based on effort (story points) and value based on sum of votes of ideas linking to this feature

  • Russell Swisher commented
    April 11, 2016 20:05

    We'd like to be able to pull a numeric value entered from an idea submitted in the idea portal, and be able to use that within the formula for calculating the idea scorecard value.

  • Matt Cardwell commented
    October 31, 2016 21:34

    This enhancement would be excellent. It would have to be able to draw upon additional linked elements to replace some of the outside of Aha scoring that we do on various product roadmaps, though. In particular, access to linked initiatives from within the feature would be imperative or to sums across a release based upon included features would be necessary.

  • Jason Slaughter commented
    February 8, 2017 21:05

    Has there been any movement on this?

    We use "Effort" in our scoring, which is exactly equal to the value in the "Estimate" field. It would save us a lot of annoying duplicate work if the "Effort" part of the score could automatically update when the "Estimate" field is entered or updated, and would also avoid mistakes where the "Estimate" field is updated by the Score is not.

  • Russell Giroux commented
    February 15, 2017 16:24

    This is very important for our company. It would be great to have the fields that fed into the scorecard to be visible and editable in other parts of the interface. We would like to be able to feed external information into the scorecard as well.

  • Patrick Matthews commented
    March 23, 2017 19:06

    I'll add my vote to this one. We use Effort in the score card, but it's an exact match for the feature estimate (which is calculated by the estimates of the feature's requirements). Allowing this to auto-update when the devs update the requirement estimates in Jira would be a huge boon to us.

    For completeness sake, here's a typical score calculation for us:

      (CustomerValue x weighting + PublisherValue x weighting) x (Deliverability / 100)  / If(Effort>0,Effort,1)

  • Tony Lopez commented
    May 22, 2017 13:03

    Additional example & Suggestion:
    We rate our clients (Gold, Silver, etc.) and store client info (including rating) as a custom table.  We would like to include our client rating as part of the Aha score, potentially by associating a value or equation with each client rating value.  For example, add 10 point or Gold clients add 5 points for Silver. Or apply a 1.2 multiplier for Gold clients and a 1.1 multiplier for Silver clients.  Thanks for considering.

  • Dave Tucker commented
    June 15, 2017 20:54

    I'd like to include the number of votes as a metric in the scorecard so drawing that in as a field would be ideal

  • Jessie Salzbrun commented
    July 26, 2017 19:48

    Adding my vote here - my specific use case is this:

    We rate effort on a sliding scale in our Scorecard (points for front end/back end/mobile), which combine to make up the (+) portion of each feature's Score. We then sum the total effort scores (front end score + back end score + mobile score) to make up the aggregate Effort/Story Points. It would be great to sync those two, or to first score in the Effort field and have this flow into the Scorecard as a metric.

  • Geoffrey Kim commented
    August 9, 2017 15:48

    I didn't go through all the comment below, but having tags or text also become metric source would be very useful.  For example, Technology A gets 20 points and Technology B gets 40 points etc and the mapping is defined as part of scoring system.  That will expand the scoring system to include non-numeric values.  Thanks!

  • Devin DePoint commented
    December 6, 2017 03:32

    A use case that my organization would find beneficial is if dates in a custom field could be used to increase the scorecard rating as the date gets closer and closer.  This would essentially be saying "as we get closer to the target date, increase the score of the feature because it is more urgent".

  • Guest commented
    February 23, 2018 18:35

    Our use for this is similar as some of the comments below. We have custom fields in our features where the responses are based on options from a drop down menu (that is not a #). We would want to be able to place a value on those options and than have the scorecard automatically calculate the values and produce a total. As others have said, this would remove the subjectivity of someone needing to choose a # from a scale. I need this capability today to help us prioritize our work.

  • Sam Marsh commented
    April 27, 2018 14:54

    We would find this very useful also. Currently we have a slider for t-shirt size, and a table in the tooltip to tell folks 'XL: 13, L:8, etc'. If we can select a t-shirt size in the feature (as a custom field) and then have the slider update as a result, that would be superb.

  • Oleg Yazvin commented
    July 16, 2018 17:55

    Adding my vote here. We base our prioritzation off the Pragmatic Marketing Framework which includes counting the number of customers that have asked for a particular feature.