JIRA. Time tracking and issue workflow

7,052 views

Published on

JIRA. Time tracking and issue workflow

Published in: Technology, Business
1 Comment
3 Likes
Statistics
Notes
  • There are also tools that integrate with Jira and speed up time capture. Such an addon is Cronforce Time Tracking for Jira. You can read more here: http://cronforce.com/integrations/jira.html . It allows you to run a timer while working on a ticket in Jira. This you can capture your time and when you stop the clock it gets transferred to the Jira Worklog and the Cronforce application.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
7,052
On SlideShare
0
From Embeds
0
Number of Embeds
66
Actions
Shares
0
Downloads
137
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

JIRA. Time tracking and issue workflow

  1. 1. Time tracking and issue workflow
  2. 2. JIRA. Time tracking Why do I need it ?
  3. 3. JIRA. Time tracking Why do we need it ?
  4. 4. JIRA. Time tracking 1. Aims of time tracking
  5. 5. JIRA. Time tracking - “Ordnung muss sein” 1. Aims of time tracking
  6. 6. JIRA. Time tracking 1. Aims of time tracking - “Ordnung muss sein” - Flexible timetable report
  7. 7. JIRA. Time tracking 1. Aims of time tracking - “Ordnung muss sein” - Flexible timetable report - Overtime calculation
  8. 8. JIRA. Time tracking 1. Aims of time tracking - “Ordnung muss sein” - Flexible timetable report - Overtime calculation - Projects analysis
  9. 9. JIRA. Time tracking 1. Aims of time tracking - “Ordnung muss sein” - Flexible timetable report - Overtime calculation - Projects analysis - Issue retrospective view
  10. 10. JIRA. Time tracking 1. Aims of time tracking - “Ordnung muss sein” - Flexible timetable report - Overtime calculation - Projects analysis - Issue retrospective view - Projects bugdeting
  11. 11. JIRA. Time tracking 2. Dashboards configuration - Start your workday with JIRA personal dashboard - “Assigned to me” gadget (filter results gadget for QA) - “Tempo User Timesheet” gadget - Project activity stream, Saved filters, Quick links and other
  12. 12. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory.
  13. 13. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory. - Log time spent just after sending task to QA or before the workday end. Next day morning all time has to be logged
  14. 14. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory. - Log time spent just after sending task to QA or before the workday end. Next day morning all time has to be logged - Log real time spent on project tasks, not 8h/day.
  15. 15. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory. - Log time spent just after sending task to QA or before the workday end. Next day morning all time has to be logged - Log real time spent on project tasks, not 8h/day. - Log time spent for common issues to “Internal” project (Meetings, Self-development, etc)
  16. 16. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory. - Log time spent just after sending task to QA or before the workday end. Next day morning all time has to be logged - Log real time spent on project tasks, not 8h/day. - Log time spent for common issues to “Internal” project (Meetings, Self-development, etc) - Easy-logging with TEMPO
  17. 17. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory. - Log time spent just after sending task to QA or before the workday end. Next day morning all time has to be logged - Log real time spent on project tasks, not 8h/day. - Log time spent for common issues to “Internal” project (Meetings, Self-development, etc) - Easy-logging with TEMPO - Overtime logging with “Plan time” functionality in TEMPO
  18. 18. JIRA. Time tracking 3. Worktime logging - Workload report for each task is mandatory. - Log time spent just after sending task to QA or before the workday end. Next day morning all time has to be logged - Log real time spent on project tasks, not 8h/day. - Log time spent for common issues to “Internal” project (Meetings, Self-development, etc) - Easy-logging with TEMPO - Overtime logging with “Plan time” functionality in TEMPO - Work logging is mandatory for managers, designers, QA, etc: rules are the same for everyone
  19. 19. JIRA. Issue workflow 1. New issue workflow
  20. 20. JIRA. Issue workflow 2. Issue status - Issue creation: new mandatory fields “component”, “fix version”, “estimate” - Issue author fills in estimates, developer can modify them if needed, before progress start. In future estimates modification will be tech lead role - Use “start” and “stop” progress button to notify what task you are working on now. - No more resolving tasks by developers - that’s a QA or manager function. - There is no need for reopening and reassigning tasks for developers. Just push it to testing - QA has to see all issues assigned with “In testing” status - Task can be closed only by manager
  21. 21. JIRA Hints If you’re using Eclipse as IDE, or anything based on it, you can try IDE Connectors to make work with JIRA tasks faster. https: //www.atlassian.com/software/ide- connectors/overview Also if you’re using Chome, use can try some extensions to make work with JIRA tasks faster. https://chrome.google. com/webstore/search-extensions/jira? hl=ru
  22. 22. YOU
  23. 23. PS. All the worktime, spent for this presentation was logged to JIRA:)

×