Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leaf2nd Level Support
You are here:
  • Forums
  • General discussion

Content

Input "Estimated time" as days?

Added by Michael Freitter about 8 years ago

Greeting,

it es possible to change the format from the field “Estimated time” from hours to days?

Regards
Michael


Replies (11)

RE: Input "Estimated time" as days? - Added by Robin Wagner almost 8 years ago

Hello Michael,

thanks for your question.
The format for “Estimated time” is hard-wired to hours.
However, you could create a work package custom field to get this behavior:

Best,
Robin

RE: Input "Estimated time" as days? - Added by Michael Freitter almost 8 years ago

Hello Robin,

thanks, for answer!

The format for “Estimated time” is hard-wired to hours.

Bad; 95% of my customers plan in days and not in hours.
It is possible to change this point an only one place in the source code or on many places?

However, you could create a work package custom field to get this behavior:

Yes, this is possible, but with the original field is input to many calculations, or?

It is possible to configurate a calculation between two fields?
I have a custom field “days” and I give a value of 4 and he calculate the value of 32 (=4*8 hours) in the original houre field?

Regards
Michael

RE: RE: Input "Estimated time" as days? - Added by Barbara Vici about 5 years ago

We have the same need: we would like to manage estimated time in days and not in hours.
I know the discussion is quite old, but have you found a solution?
Thanks
Barbara

RE: Input "Estimated time" as days? - Added by Patrick Albert almost 5 years ago

Same problem here:
All PM in the company calculate estimated / spent time in days.

It would be really helpful if this column would be configurable.

RE: Input "Estimated time" as days? - Added by Sven Ludwig over 4 years ago

Same request here, we calculate things in the time unit of "man days". Hours could also be interesting in some scenarios, where for example a freelance coworker is billing in hours instead of days. However, a very common time unit is days.

RE: Input "Estimated time" as days? - Added by Oliver Günther over 4 years ago

Hi everyone,

personal opinion: the backend is already capable to do these different kinds of input (the field is technically an ISO8601 duration format), but the frontend forcefully uses hours for formatting. I think this could be solved with a simple setting.

Best,

Oliver

RE: Input "Estimated time" as days? - Added by Sven Ludwig over 4 years ago

Hi Oliver, hi everyone,

from user perspective, a setting within a project or for a whole hierarchy of projects, that determines whether the unit is hours or days, could be fine. I would in my projects then always set it to days.

However, a more flexible solution to fill the field in days and/or hours within a project or whole project hierarchy would also be nice. Is the backend already agnostic regarding the time unit when it does its calculations, nowhere assumptions in the code that the field has hours? If so, this could perhaps be an easy solution option, giving the users more flexibility, too. (Perhaps as simple as a change in the frontend.)

RE: Input "Estimated time" as days? - Added by Patrick Albert over 4 years ago

Or maybe it is possible to support extended GUI inputs like "12d" or "12h"? Then the default value of "hours" can remain (as it is now) and each user can decide whether to enter the time in days or in hours - without any additional configuration.

RE: Input "Estimated time" as days? - Added by Alexandre Charvier over 4 years ago

Hi,

Same issue here !

It would be great to fill estimated cost in hours / days / weeks.

Moreover,

  • Is it possible to add a workload percentage option meaning that the assignee works during 80% of the estimated cost.
  • Is it possible to get some kind of workload plan per member or a group of people (with GANTT chart view !). It would be very useful in case a person is assigned a task during two weeks at 40% of his time, I know I can assign him other tasks during those 2 weeks regarding the remaining 60%.

BR,

Alex

RE: Input "Estimated time" as days? - Added by Robin Wagner over 4 years ago

Hi Alex,

feel free to open a feature request for the estimated time in days and weeks.

Resource management / capacity planning is not yet possible in OpenProject. We are currently looking for a sponsor for this feature.

Regarding the workload per member (with a Gantt chart) you can use the global work package page (click on the "Module" entry, select "Work packages", then group by "Assignee"). Then activate the Gantt chart. This gives you an overview of the tasks assigned to each user across all projects. Optionally, you can filter e.g. by the finish date (e.g. finish date in the current week). The view does not differentiate between the workload of the user but you can get a general overview of the assigned tasks for each user. You can then of course save this in a view for easier future access.

Here is an example:

RE: Input "Estimated time" as days? - Added by Christopher Moriarty almost 4 years ago

Hi - I'm also interested in having the Estimated Time fields allow for hours/days/weeks.  Has there been any progress on this?  My team is about to start entering their estimates and I instructed them to use "days", although of course, they cannot...

  • (1 - 11/11)
Loading...