Some improvements for the Reports with regards to time tracking

We recently pushed out new Filtering capability which will allow you to filter on time tracking events

We will mark this Idea as shipped to keep the idea backlog clean (since the other items are taken care of through existing ideas).

Thanks Daniela. we've updated the original idea with your prioritized list.

We have good news regarding the 3 highest priority items on your list.

1. We have an upcoming feature to add filtering for Time tracking dates on the reports screen. This should help to provide more insight into billable time review and reporting. This feature is planned and should be available in the short-term - we will reach out once it is available.

2. Pivot table headers are also a feature that we are likely to implement. You should vote on the idea here and you will get immediately notified once there are new updates: https://big.aha.io/ideas/APP-I-1895. This has not yet been planned but is definitely on our radar.

3. We have a workaround which can help with your specific use case. Invite your team to join a new product (perhaps call it something like Internal Time Reports). In this new product, you can create reports which are filtered for the original product, and share them only for your team to be able to view. This would allow your team to access/view the reports, and your client would not be able to see it (because they are not a member of the newly created product).

In regards to your lower priority items, there are captured under other standalone ideas. I'd suggest voting for them so that you can get direct updates on the ideas. Some have been reviewed but not all just yet.

• Burndown charts by time are something which are also on our radar: https://big.aha.io/ideas/APP-I-719. This is marked as likely to implement but further out on our roadmap
• Product line filters: https://big.aha.io/ideas/APP-I-1596. I can see what you are trying to achieve, though based on priorities and community feedback, it is currently a lower priority.
• The additional time logging ideas are also lower priorities right now based on our strategic objects, but we will keep this open for now.

I hope that the updates above, particularly on your 3 highest priority items will be helpful. Please stay tuned as we continue to provide more updates here.

Hi

I have updated the comments on the Idea to include priority etc.

Hope that helps

*Daniela Patterson*
Project Manager

*A Salesforce.com Platinum Partner*
Level 4, 39 Martin Place, Sydney NSW 2000
*M* +61 447 770 855
*W* www.systempartners.com
*L* au.linkedin.com/in/danielapatterson

Hi

Order of priority is:

1. Ability to do pivot tables showing the time tracking logged during a specific date range.  Therefore we can see across all products what time an individual has booked in the last week, fortnight, custom dates etc.
   1. Issue: We cant align out review of time entered with our budget reporting.  Also staff can't review they have entered all their billable time for the day as they can't filter by date range
2. Add labels for each of the Columns/rows/cells so as to easily distinguish what the data is that is being rolled up.  With some complex pivot tables it is hard to recall what each field represents
   1. Issue: we are needing to remember what each label represents for multiple pivot tables which is challenging.  When sharing Pivot tables via Notebook with the client, it is not obvious what the table is trying to reflect
3. Ability to share any reports at a 'user' level not just at a 'Product/product Line' level.  There are specific reports such as time entered reports I only want my team to see but not the end client.  If I share this report at a product/product line level that the client has access too, I don't want them to see this information (unless they built the report themselves - which often they wouldn't).
4. Ability to capture non rolled up effort to a feature card/requirement.  Therefore, if the feature is 4 days, and you have booked 1 day but you don't want that 1 day to burn down the 4 days or have any impact to the 4 days at all as it is technically 'non billable' effort but we still need to track this effort and report on it where possible
   1. Issue: We track both billable and non billable time (eg: pre-sales, review, upskilling/handover).  I want my staff to be able to enter time to the feature card but not have it impact the remaining effort etc but show it as separate time entered: Time entered that does impact feature/requirement estimates, and time entered that does not.  I need this to go all the way through to reports/pivot tables etc so that we can report on this too
5. Ability to add a description when time is logged to either a feature card or requirement - not just time
   1. Issue: if we are adding 'non billable' time to a task, it would help us understand the supporting comments with the time entered.  Also, some of our clients want more detail of time entered etc and comments would allow us to capture specifically what was done in the 1, 2 hour etc.  Example would be an Implementation feature card.  For 2 hours I prepared the implementation run sheet and held workshops with the client to gather supporting details.
6. Have a burn down chart that shows time logged for a product/release etc that is in synch with the pivot table
7. Ability to filter in the Pivot table by 'Product Line' and not just 'Product' level
   1. Issue: Again if I am doing a 'time entered' report and want to see all time across the whole product line, rather than select all supporting Products would be simpler and easier.  Also allows other rollups to occur at a Product Line level for executive and client management purposes.

Hope this helps.  Glad to have a goto meeting to discuss these further if needed.

Kind regards

Daniela Patterson

Hi Daniela, thanks for the note and the suggestions for report improvements. Can you prioritize your suggestions based on what you feel is most important?

Also, can you expand upon exactly what areas are most problematic? This would be helpful for us to better understand the issues, as well as what potentially can be done.

Hi - what are the chances of getting at least some of these improvements.  This is causing us considerable pain at the moment.

Could we also please include the ability to filter in the Pivot table by 'Product Line' and not just 'Product' level?

It would also be really useful if the Pivot table reports allowing reporting of the work done by resources, and work remaining, at the Requirement level (like what is possible at the Feature level).