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
  • Attach files
  • Jamie Burr commented
    4 Jun, 2015 08:47pm

    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.

  • Guest commented
    16 Apr, 2015 07:50pm

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

  • Gabriel Michaud commented
    10 Apr, 2015 02:47pm

    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?

  • Ram Tulasi commented
    8 Apr, 2015 04:39pm

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


    Ram Tulasi, Concur Technologies

  • Admin
    Chris Waters commented
    8 Apr, 2015 02:55am

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

  • Smitha Tatavarthy commented
    8 Apr, 2015 02:40am

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

  • Gabriel Michaud commented
    1 Apr, 2015 09:52pm

    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.

  • Chris Maddocks commented
    27 Jan, 2015 05:09pm

    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.

  • Jonathan Berg commented
    27 Jan, 2015 12:15pm

    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

  • Pravin Conda commented
    27 Jan, 2015 12:05pm

    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. 

  • Admin
    Chris Waters commented
    27 Jan, 2015 03:39am

    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?

  • Jonathan Berg commented
    26 Jan, 2015 01:21pm

    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. 



  • Keith Mader commented
    20 Nov, 2014 11:04pm

    I need it to stop Excel from being abused.

  • Chris Maddocks commented
    20 Nov, 2014 10:22pm

    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.

  • Guest commented
    20 Nov, 2014 06:56pm

    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!

  • Ram Tulasi commented
    14 Nov, 2014 05:59pm

    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.

  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • Avatar160.e35e46fe62a53e488ef9451dd1d3432e
  • +3