SQL Query for timebookings on projects epics, sprints, stories and items for Zoho Analytics

SQL Query for timebookings on projects epics, sprints, stories and items for Zoho Analytics

At CEYOND, we use Zoho Sprints for our agile projects. To evaluate and charge the effort of the tasks we use Zoho Analytics.

With this SQL query you could access all relevant accounting data and assign it to projects, sprints, epics, stories and items. Hope this helps.

  2. date(substr(t."Log Date", 1, 10)) "Log Date",
  3. t."Description" "Description",
  4. t."Log Time in Minutes" "Log Time in Minutes",
  5. t."Log Time in Hours" "Log Time in Hours",
  6. t."Last Updated Time" "Last Updated Time",
  7. t."Billable Type" "Billable Type",
  8. ou."User Name" "Owner",
  9. au."User Name" "Approved By",
  10. p."Project Name" 'Project Name',
  11. s."Sprint Name" 'Sprint Name',
  12. s."Sprint Type" 'Sprint Type',
  13. i."Item No" 'Item No',
  14. i."Item Name" 'Item Name',
  15. i."Item Type Name" 'Item Type Name',
  16. i."Priority Name" 'Item Priority Name',
  17. e."Epic Name" 'Epic Name',
  18. e."Epic Type" 'Epic Type'
  19. FROM  "Timesheets (Zoho Sprints)" t
  20. LEFT JOIN "Users (Zoho Sprints)" au ON (au."ZSUser ID"  = t."Approved By") 
  21. LEFT JOIN "Users (Zoho Sprints)" ou ON (ou."ZSUser ID"  = t."Owner ID") 
  22. LEFT JOIN "Items (Zoho Sprints)" i ON (i."Item ID"  = t."Item ID") 
  23. LEFT JOIN "Sprints (Zoho Sprints)" s ON (s."Sprint ID"  = i."Sprint ID") 
  24. LEFT JOIN "Epics (Zoho Sprints)" e ON (e."Epic ID"  = i."Epic ID") 
  25. LEFT JOIN "Projects (Zoho Sprints)" p ON (p."Project ID"  = i."Project ID")  
  26. ORDER BY t."Log Date" 

      • Sticky Posts

      • Tip #28 - Plan less and deliver more using WIP limit in Zoho Sprints

        Hello, It's been a while since we met with a quick, interesting tip. As the saying goes, "Too much of anything is good for nothing", today the focus is on delivering your outcomes with the right amount of planning. Your plan should be practical, calculative, and achievable for driving a qualitative success.    Laura's plan   Laura has a habit of planning her project deliverables before assigning work to her team-mates. Once the plan is finalized, she schedules a general meeting with her team and
      • Tip # 3- Working on the Scrum board

        Continuing from our Tip #2 on leading to a sprint, let's see how to manage the work items on the Scrum board.  Once you start the sprint your work items are automatically displayed on the Scrum board where you will actually manage the work items. It is a snapshot of the backlog items identified for the current sprint.    The layout of the Scrum board Simply put, the scrum board is just like a physical board with sticky notes on which the work items of the active sprint are displayed.  The scrum board
      • Tip#2- Leading you to a Sprint

        Product Backlog After the user stories are written and finalized, they are sorted to create the Product Backlog for the project during the Backlog Grooming meeting. This is a master list of all the work items that have been identified for the project and sorted by priority. Requirements are not constant during this period.The Product Backlog is dynamic and is an ongoing process. Every user story in the Product Backlog is customer centric. The Product Backlog includes: User centric stories based on
      • Tip #1- Why swimlanes?

        Lanes define a clear path to reach your destination. In Agile, swimlane is one such concept that sets a simple and clear process of the work that you do.   The concept of swimlane can be related to the pool, where the swimmers gather in their respective lanes to start off. Similar to the pool, work items are grouped in different categories. Each category is referred as a lane and is displayed in horizontal format. Swimlanes are effective in categorizing the work items with respective to specific