[#58160] project stage columns on project list

[EinLama]

Ticket

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

What are you trying to accomplish?

All Project::LifeCycleStepDefinition instances show up in the Configure View modal. For each row/project with an active Project::LifeCycleStep configured, its cell will display the date values of the stage or gate fitting that definition.

Please note that as of now, sorting and filtering is not supported for these new columns.

In order to see and test this locally, you must first set up some life cycle step definitions and then populate some projects with the corresponding life cycle steps.

Screenshots

Above, you can see that life cycle columns are now visible in the project list. They must be active and assigned to any of the projects. Additionally, they must be added via the configure view modal. Only then will they show up. Cells with no active, associated life cycle step are left empty. The appropriate icon and color for the specific definition is displayed.

Above, you can see the columns when some life cycle definitions have been added.

Above, you can see the action menu for the new columns. For now, they cannot be used for sorting or filtering. This will be done in later work packages.

What approach did you choose and why?

Merge checklist

• Added/updated tests
• Added/updated documentation in Lookbook (patterns, previews, etc)
• Tested major browsers (Chrome, Firefox, Edge, ...)

[dombesz]

The functionality works nicely @EinLama !👏
I just left a few notes, but overall it looks good.

[dombesz]

Good job @EinLama , thank you! 👏
I just made a minor comment on a suggestion on using index_by instead of group_by.

[dombesz]

Oops, I just realised that we have to put the whole implementation behind the feature flag :stages_and_gates.
We cannot show the stages and gates as selectable fields in the table configuration, nor show the columns.

[EinLama]

Thank you for pointing out the necessity for the feature flag. I thought the new columns would be hidden by them being set to inactive by default, but that wasn't true :)

[dombesz]

Well done @EinLama ! 👏