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

[Solved] Work package status not shown

Added by Fritz Müller over 8 years ago

Hi

I created new entries for work package status in the admin area. But they don’t show off in the project when creating or changing single work packages there. What have I done wrong?

Regards,
Fritz


Replies (8)

RE: Work package status not shown - Added by Robin Wagner over 8 years ago

Hi Fritz,

after creating the work package status you need to decide which roles and types can use them via “Workflow”:

In the admin settings select “Workflow” in the left menu, select the role and Type to which you want to assign the status. Then uncheck “Only display statuses that are used by this type” and click “Edit”.

In the table check the transitions you want to allow for the selected role and type and click “Save”:

Make sure you have the specified role as well as the selected type activated in the project you want to use the status.

Best,
Robin

RE: Work package status not shown - Added by Fritz Müller over 8 years ago

It doesn’t work. I did all changes under workflow but I can not see thze new statuses.

Maybe I screwed up something. I deleted some of the standard statuses before I created new ones. So now when I create a new workpackage I can not select its status. There is only “open” as a a fixed value, no more drop down box to choose an alternative.

Regards,
Fritz

RE: Work package status not shown - Added by Robin Wagner over 8 years ago

I assume “Open” is a status you created yourself?

Did you set this status as default (by clicking on the status under “Types” in the admin settings and checking “Default value”)?

There is probably no allowed transition for the status you selected as default and the project role and type you are using.
Therefore, it is not possible to change the status - there is no dropdown.

The easiest way to fix this would be to set a standard status - such as “New” as default (via “Types” (in admin settings)).
To do this click on the status you want to have as a default value and check “Default value”.

Alternatively, you can define valid status transitions for your default status for the roles and types you are using.

Best,
Robin

RE: Work package status not shown - Added by Fritz Müller over 8 years ago

1. Setting “new” as standard status: worked. Thanks. The drop down box is back again.

2. The new status “in Bearbeitung” doesn’t show itself in the drop down box allthough I changed settings in “workflow” accordingly.

3. What is “status transitions”? Can OP change status automatically when other values are changed? F.e. when I change a work package with status new to 30% work done, does the status change from “new” to “working on it” by itself?

Regards,
Fritz

RE: Work package status not shown - Added by Fritz Müller over 8 years ago

To Nr. 2: I checked every possibility there is to check at workflow for every status except its own one which I unchecked. Now I can see all statuses in the drop down box. Dunno if this is usage as expected. Any way: it works now.

To Nr. 3: still interested if such a feature exists.

Regards,
Fritz

RE: Work package status not shown - Added by Robin Wagner over 8 years ago

Concerning your third question:

The options “Additional transitions allowed when the user is the author” and “… when the user is the assignee” allows you to adjust the workflow for the special cases that the user created a work package or is assigned to it. Normally however, you won’t need these options.

It is possible to calculate the progress based on the selected status (but not the other way around). In order to do this go to “Settings”, then to the “Work package tracking” tab and set “Calculate the work package done ratio with” to “Use the work package status”.

Now you can go to each status and specify to what progress the work package should be set once this status is selected.

If you now set a work package to that status and save, the progress is updated accordingly:

RE: Work package status not shown - Added by Fritz Müller over 8 years ago

Very informative, really. Maybe I fiddle around with it later.

Thanks a lot for your help. Subject closed ;-)

Greets,
Fritz

RE: Work package status not shown - Added by Robin Wagner over 8 years ago

Glad to hear the workflow is working now.

Just for your information:
The entries in the rows are the selected statuses and values in the columns are the ones that can be selected.
If you select all entries you allow transitions from the status to all other status and vice versa.
There may be cases where you want to limit this behavior (e.g. when you want a work package type that is set to a status “closed” not to be set to a status “open” anymore)

Provided you have the specified role in the project and select the type for which the workflow was specified you can then select the status for which there is a valid transition from the currently selected status (in this case from “New”) (The available options are the same as specified in the row in the image above):

Best,
Robin

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