Ideas

• Make it easier to set "Subtract breaks" from the Timesheet page
  • "Subtract breaks" option modifies how the Timesheet is assembled for the given user. If it is set, then the timestamps for the time of leave column will be earlier than the real timestamps, because the system subtracts the length of the Pause tasks from it.
  • This is important, so please add a helpful message with a link to the Timesheet page (/report/timesheet) that navigates the user to the Profile page (/user_mgt/edit) where the "Subtract Breaks" option can be toggled. The message should be specified in the localization.
• 168 hour timesheet view for habit tracking
  • For more info see: http://lauravanderkam.com/books/168-hours/manage-your-time/
• Emoji support
• Niko-niko calendar feature for mood tracking
  • It would be nice to track the mood of the users. For example, the user could toggle a 3 state button for each day on the tasks page. the collected data could be presented to the participants (or maybe show data to users that work on similar tasks, and team leads).
  • More info on the niko-niko calendar: https://www.agilealliance.org/glossary/nikoniko/
  • The collected data could be useful not only for teams, but also for individuals. If you look back, you can identify good or bad periods. If you are uncertain about what to do, you can always look at the hard data to justify a job change.
  • It would be cool to be able to track short notes that describe your mood, that you can read later like a journal.
  • For privacy reasons, it might be better if this journal is private by default.
• Configurable OAuth
• Make it easy to batch edit days
  • The Timesheet page could be enhanced to let the users quickly edit / fill their a whole month of data.
• Configurable smart links
  • If a task description contains text like M#1234, it will be converted to a link for a Mantis issue. The URL of the Mantis can be configured in the props files. It would be great to ditch this static link translation in favor of something more dynamic.
  • For example, we could provide an admin page where the link transformation rules could be set with regexes.
• Holiday management
• Optional pomodoro with notifications.
• Add user settings for fields used in the tasksheet, such as number of work hours per day or lunchtime length.
• Command Palette to Manage Tasks
  • As an alternative mechanism to the currently used mouse based user interface, this would provide a smart text input, where the user could issue various commands to interact with the TimeAdmin, à la Sublime Text.
• Fancy workload indicator based on interruptions
• Collaboration and Social feature + Avatar Picture for users
  • Make other users visible on the tasks page who work on the same task (or same project) in the same day (or week) as you.
  • Maybe we could show a notification if a new user starts working on the project, and provide a way to interact with them.
• Display creator, creation date and deactivation date for Tasks in the Projects page.
• User Defined Time Zones
  • Currently the application uses the server time zone to work with date and time data instead of user defined time zone.
• On the task page order available tasks by usage
  • The selectable tasks could be in this order:
    • pause
    • tasks from last month / week (alphabetically or by usage)
    • other tasks (alphabetically)
• Estimation
  • Project and Task estimation
    • When an admin creates a new project or task she would able to define an estimation for it. On tasks under an estimated project we should verify the estimation to not overflow the estimation defined in the parent. In this phase users unable to estimate on ad-hoc tasks.
    • The estimations and the time remaining will be reported on the project and task editor forms as a column chart. On a project all underlying items will be reported separately.
  • Estimation on Ad-Hoc tasks
    • When somebody creates an ad-hoc task, she would able to define an estimation for it. On tasks under an estimated project we should verify the estimation to not overflow the estimation defined in the parent. With adding estimation to ad-hoc tasks the business logic will be more complicated because the meta hierarchical items related to it.
    • We should consider the possibility of merging the project and task entities into one to prevent the complicated business logic of handling meta items in the hierarchy.
  • Report estimations and time spent on tasks page.
    • When somebody start tracking an estimated task, she should see a report about the estimations and time spent for the task and the project above. A column chart similar to the one mentioned in issue #72 would be fine.
  • Scope expansion and shrinking
    • When somebody creates a new task or ad-hoc task under an estimated project, she would be able to mark the estimation as an expansion for the project's scope. The expansion tasks and the time spent on them will be highlighted in reports.
    • When somebody inactivates a task, it will shrinks the project's scope and it will be highlighted in reports too.
  • Proxy enumeration
    • When estimating a project or a task the users can enumerate proxies for the current item. Each proxy must a have cardinality, a type (i.e.: screen, db table, entity or etc.) and an optional description. More about proxies: http://www.chambers.com.au/Sample_p/co_proxy.htm
  • Proxy-based estimation
    • When somebody starts a new proxy enumeration, the application able to suggest items and their estimations with similar proxies defined, so the user has some help to estimate the current item. More about proxies: http://www.chambers.com.au/Sample_p/co_proxy.htm