Pivot improvements: Add custom fields

Add custom fields to the pivot table so that we can report n-levels deep. For example, I may want to add initiatives but then indicate which component the features relate to using my custom tags field.

  • Suzanne Vaughan
  • Oct 28 2014
  • Shipped
Release time frame
  • Attach files
  • Ram Tulasi commented
    November 14, 2014 17:59

    This would be so awesome! I need it!

    For example, the release theme can help us communicate themes that succinctly capture the roadmap. This would be super powerful for us.

  • Guest commented
    November 20, 2014 18:56

    This is critical to helping us fully retire Excel as a planning tool.  We need to be able to evaluate the component coverage of features.  Can't have this feature soon enough!

  • Chris Maddocks commented
    November 20, 2014 22:22

    Yes please! We absolutely need this to be able to communicate product plans to senior stakeholders. We often need to report across ALL products for a particular vertical, business unit, etc. and have no way to do this today other than a lot of manual Excel / PowerPoint massaging.

  • Keith Mader commented
    November 20, 2014 23:04

    I need it to stop Excel from being abused.

  • Jonathan Berg commented
    January 26, 2015 13:21

    I would also like to be able to use Tags in the pivot tables. 

    That would allow me to use pivot tables to create a story map, which is very useful in the planning stages of a new project. 



  • Admin
    Chris Waters commented
    January 27, 2015 03:39

    Can you elaborate on how tags should work on the pivot table. Would you like each tag to be a separate row or column heading? Or something else?

  • Pravin Conda commented
    January 27, 2015 12:05

    This is just one instance, but the way I envision tags would work on the pivot table is that you will have tags or custom fields to be able to another item within the drop-able fields. This would in turn turn that tag so that they can set it both as an extra field. I believe in order for you to get n-levels deep their might be more functionality needed, but as a starting point it would be great to pull custom field to bring in additional dates that are crucial to the release. 

  • Jonathan Berg commented
    January 27, 2015 12:15

    Hi Chris,
    I’d like each tag on a separate row or heading. I would do something along these lines:

    * each column has a tag at the top
    * Each row is a release (or an initiative)
    * Each cell has a list of features; ideally the features are listed in the order that they appear on the feature board (in the releases)

    That should allow me to create a story map (if necessary, you can see an overview of story maps here http://www.agileproductdesign.com/presentations/user_story_mapping/)

    Jonathan Berg
    Director, Product Management

    115 W 30th St, 10th Floor
    New York, NY 10001
    o: (212) 213-8333 ext. 169

  • Chris Maddocks commented
    January 27, 2015 17:09

    Can you elaborate on how tags should work on the pivot table. Would you like each tag to be a separate row or column heading? Or something else?

    This is what we had in mind too: the ability to use tags as the row headings, and releases (or quarters) as the column headings. Then you can map out what we are delivering toward different verticals or categories by quarter. We're migrating most of this type of data to custom fields, but I can imagine situations where the tags would still be helpful.

    It would be important to pick and choose which tags to include, because that list can get quite long.

  • Gabriel Michaud commented
    April 01, 2015 21:52

    Definitely something that I would like to see ASAP! Other basic fields such as feature "Type" should be there. Right now since i'm unable to do it I have to use the "Initiative" field for something which it was not intended, and that creates other issues.

  • Smitha Tatavarthy commented
    April 08, 2015 02:40

    This is a very critical feature for a product manager ..when can we anticipate the release for this feature ?

  • Admin
    Chris Waters commented
    April 08, 2015 02:55

    The pivot table is under development now. Accommodating all of the different use cases is quite challenging, but we are making good progress.

  • Ram Tulasi commented
    April 08, 2015 16:39

    Great news Chris! Can you elaborate on what might *not* be handled with this feature request? 


    Ram Tulasi, Concur Technologies

  • Gabriel Michaud commented
    April 10, 2015 14:47

    Great news Chris! Do you also plan to include the other standard fields which are missing right now, such as Feature Time, Release Phase etc?

  • Guest commented
    April 16, 2015 19:50

    Also need access to non-custom existing fields 'feature type' and 'story points' so we can monitor via line/bar charts.

  • Jamie Burr commented
    June 04, 2015 20:47

    I would like to see the ability to pull the total feature score by release - this gives us a release value we can compare between releases. So, the ability to select the Score field in the pivot table is the request.