Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • 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
    • Enterprise 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?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. General discussion

Not all work packages can change status as expected

Added by Paul Moore over 6 years ago

I have several work packages setup in such a manner, but for this example I’ll use ‘phase’. I have a user group called ‘Tech Leads’ that I am a member of.

I setup ‘Tech Leads’ to allow all/every transition of status in workflow editor. However, only most ‘phase’ workpackages can transition from status to status. There are a few that can’t be changed, and are stuck on ‘New’ with no option to change status.

How can I change this?


Replies (3)

RE: [SOLVED] Not all work packages can change status as expected - Added by Paul Moore over 6 years ago

As it turns out, the work package instances that were stuck in ‘New’ belonged to projects where ‘Tech Leads’ had no Role Permissions. I added ‘Tech Leads’ to the projects in question, and everything wokred out fine

RE: Not all work packages can change status as expected - Added by Oliver Günther over 6 years ago

Hi Paul,

your second comment is exactly what happened, and this does happen quite often when moving to different types (and workflows on the instance that are different).

This bug has already been fixed for 8.0. as part of

Best,
Oliver

RE: Not all work packages can change status as expected - Added by Julia Metz about 6 years ago

We still have that problem. What can we do?

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