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
      • Hierarchy leafWiki
You are here:
  • Forums
  • General discussion

Content

Can't change status on work packages

Added by ciuino magno over 8 years ago

Hi guys, i’ve installed openproject (3.1 pre) via repository (ubuntu 12.04) and installed all the plugins, now when i create a work package i can’t change the status and it show me only the default value

it’s a bug or there is a method to change status?


Replies (21)

RE: Can't change status on work packages - Added by Christian Ratz over 8 years ago

Hello ciuino,

yes it sounds like a bug.
If you use a pre version of OpenProject the chance to find a bug are very high and we can’t guarantee stability but we will find and fix the most of them before we release the next version.

For production use we strongly recommend the usage of the stable branch. The dev branch (pre version) should be used for development and for brave ;)

Best
Ratzi

RE: Can't change status on work packages - Added by ciuino magno over 8 years ago

Thanks for the advice

where can i find the stable branch in packager.io site ? in packager.io the 3.0.1 version is 3.1pre…

RE: Can't change status on work packages - Added by ciuino magno over 8 years ago

I Installed the 3.0.4 version, but there is the same bug…

RE: Can't change status on work packages - Added by Patrick _ over 8 years ago

I confirm this happening on 3.0.8 as well. Only the default value can be set when a plugin is installed. When I change the default value, the selectable value in the workpackage changes to the new default value as well.

This doesn’t occur on the demo instances, even though all plugins are installed there. What could possibly be the reason for that?

RE: Can't change status on work packages - Added by Patrick _ over 8 years ago

Try to reinstall the plugins. This worked for me, even without changing anything in the database (-> no data loss).

Backup your changed files (probably config/configuration.yml, config/database.yml, config/environments/production.rb, Gemfile.plugins) to a folder outside (cp filename ..). Then run git clean -df and git checkout -- .. Copy the files back, run bundle install followed by RAILS_ENV=production bundle exec rake assets:precompile. Now RAILS_ENV=production bundle exec server run, hope that helps.

RE: Can't change status on work packages - Added by ciuino magno over 8 years ago

I did as you told me, and I set all the parameters of the project, and re-appeared all variables, thanks for the support :)

RE: Can't change status on work packages - Added by Brendan Dunn over 8 years ago

I have the same issue but for the stable environment
I have tested with and without the plugins and I still cannot get a dropdown.
I have deleted the work package types and re-added them, but no change.
I have tried the following as well

cd /home/openproject
mkdir bck
cd bck
cp  ../openproject/config/environments/production.rb .
cp  ../openproject/Gemfile.plugins .
cp  ../openproject/config/database.yml .
cp  ../openproject/config/configuration.yml .
cd ../openproject
git clean -df
git checkout --
cd ../bck
cp  production.rb ../openproject/config/environments/production.rb 
cp  Gemfile.plugins ../openproject/Gemfile.plugins 
cp  database.yml ../openproject/config/database.yml 
cp  configuration.yml ../openproject/config/configuration.yml 
cd ../openproject
bundle install

I get the message
Your branch is up-to-date with ‘origin/stable’

Is there something else I can try ?

RE: Can't change status on work packages - Added by Christian Ratz over 8 years ago

Hello all,

to change the status of a work packages you have to have a proper workflow. A workflow defines the possible status transitions of a work package type depending on your role in the project.

You can setup such a workflow in the admin area. Create a wp typ than go to workflow and select the role, wp typ and click on edit. In this view you can define the workflow. To allow all status transitions just check all checkboxes (e.g. with checkmark in the upper left corner of the table).

There is no difference between dev or stable branch in how to setup a workflow.

Best
Ratzi

RE: Can't change status on work packages - Added by Brendan Dunn over 8 years ago

thanks
I fixed the setup and now it works

RE: Can't change status on work packages - Added by Griselda Adkinson over 8 years ago

Hi Brendan

What exactly did you do?

I am still struggling with this issue.

Best

Griselda

RE: Can't change status on work packages - Added by Christian Ratz over 8 years ago

Hello,

create a Role (e.g. Developer)
create some work package statuses (e.g. new, in development, developed, resolved)
create a work package typ (e.g. Bug)
Got to ‘Workflows’ in the admin area
Select Role (Developer) select Type (Bug) and hit the edit button (uncheck ‘Only display statuses that are used by this type’)
Hit the checkmark in the upper left corner of the table
Click on save

update: Add a user as a member to a project with role Developer

This will allow all status transitions for a developer on a work package of the type Bug.

You can adapt the workflow to the current workflow of your company
e.g. only allow developers to change the status from new -> in development -> developed
and allow a tester the transition from developed -> resolved

Best
Ratzi

RE: Can't change status on work packages - Added by Griselda Adkinson over 8 years ago

Thanks Ratzi for the reply.

I just followed your explanation but unfortunately without success.
When I add a new work package, the drop-down box “Status” is purely a “-”. Consequently I cannot complete the new work package as “Status” is a mandatory field.

I have also carried out the following, also without success:

  1. git clean -df
  2. git checkout —
  3. run bundle install
  4. RAILS_ENV=production bundle exec rake assets:precompile

Thanks again and kind regards

RE: Can't change status on work packages - Added by Brendan Dunn over 8 years ago

Hi

My problem was a noob mistake.
I did not associate the “Admin” user (and role) to the project hence the workflow did not work.
As Ratzi is saying, the symptom is in the workflow but the cause was with assigning a workflow through a role to the user.

RE: Can't change status on work packages - Added by Christian Ratz over 8 years ago

Thanks Brendan

I missed this important step.

RE: Can't change status on work packages - Added by ciuino magno over 8 years ago

Hi guys, i solved the problem easly by setting all the project options, and administator options;

I think it’s a bug, but for now it works…

RE: Can't change status on work packages - Added by Christian Ratz over 8 years ago

Hello ciuino,

it’s not bug but complicated if you do it the first time and there is no documentation about workflows currently. We will create one once there is a bit “free” time.

Best
Ratzi

RE: Can't change status on work packages - Added by ciuino magno over 8 years ago

Well, good to know;
i’ll wait you in the next questions, bye :)

RE: Can't change status on work packages - Added by Griselda Adkinson over 8 years ago

Well, I don’t appear to understand this.
I don’t even have a drop-down box to operate, it’s simply not there. I have tried all possible combinations of assigning work-flows, roles, users, groups… to a project and I still have no drop-down box available.

Is this really that complicated? Can someone post a step-by-step description of how to go about this. I would like to rule out possible errors with my build.

RE: Can't change status on work packages - Added by Brendan Dunn over 8 years ago

Hi

I have just attached “setup” a cheat sheet I created.
It gets a standard, out of the box OP going with a couple of minor changes.
You then get to see how it works.
Please be aware that I am an OP noob. I created the cheat sheet so I could reliably get a project server going.
The application is very flexible and these set of instructions do not get into any of those details.
I will not have set this up in the most optimal way as I am still learning but it will get you a project mgt tool.

I have also attached the latest version of how to create an ubuntu OP production server. I have run this more than 5 times and it is solid.

RE: Can't change status on work packages - Added by Griselda Adkinson over 8 years ago

Thanks a lot Brendan, your documentation is a great help.

I have worked through your notes and have learned a lot about openproject. But unfortunately I still have no status drop-down box on work package available.
Additionally I am now also getting a Error 500 when selecting Backlogs. But that, I believe, is a different issue.

Best wishes

RE: Can't change status on work packages - Added by Griselda Adkinson over 8 years ago

Problem solved. I reinstalled/configured the database and went again through the setup procedure. Now everything appears to be working as expected. That’s great, but I am not sure where I went wrong in the first place. Anyhow, it works. Brendan, your documentation is first class! Thanks for that :+1:

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