Skip to content

Implementation/62981 show and edit linked phases on work packages #18574

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 11 commits into
base: dev
Choose a base branch
from

Conversation

ulferts
Copy link
Contributor

@ulferts ulferts commented Apr 8, 2025

Ticket

https://community.openproject.org/wp/62981

What are you trying to accomplish?

Screenshots

image
  • Work pages receive a new attribute: The phase they belong to.

    • The name of the attribute is "Project phase".

    • A work package can be assigned to a single phase. There is no multi assignment.

  • The attribute can be administrated same as every other attribute (e.g. status, assignee, version).

    • It can be moved in and out of an attribute group.

    • Existing installations are not migrated to have the attribute activated for their existing types.

  • The attribute's value is displayed including the colored type indicator prefix in the split/full.

    • The autocompleter displays the colored icon as well
    • Currently, the icon is only displayed shortly as first an HalResource is passed into the display field only for the field to be rerendered with a HalLink being passed in right afterwards. That HalLink does not have a reference to the phase definition so there is no means to get the color.
  • The attribute can be changed via an ng-select.

  • In case the associated phase is later disabled in the project administration, the value is no longer displayed

  • The API v3 has a dedicated resource for phases

    • GET endpoint for referencing a selected phase

    • GET endpoint for selecting all available (active) phases of the project when selecting the value of the attribute.

  • The new functionality is hidden behind the feature flag

Not part of the original scope

  • Fix permissions on copying work packages. Before, the user had to have the move_work_packages permission as well in order to access the form for duplicating work packages to a different project. The autocompleter for selecting target projects also relied on the move permission. Both are changed without checking if there are any other places the code relies only on the move permission.

Cases to consider:

  •  Moving a work package between projects where
    • the currently linked phase is not active
    • the currently linked phase is active
  • Copying a work package to another project where
    • the currently linked phase is not active
    • the currently linked phase is active

Sorry, something went wrong.

@ulferts ulferts force-pushed the implementation/62981-show-and-edit-linked-phases-on-work-packages branch 5 times, most recently from 509673b to 174e490 Compare April 14, 2025 15:37
@ulferts ulferts force-pushed the implementation/62981-show-and-edit-linked-phases-on-work-packages branch from 174e490 to 414d75c Compare April 17, 2025 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant