Skip to content

Convert agenda item into work package#23339

Open
oliverguenther wants to merge 1 commit into
devfrom
feat/turn-agenda-into-wp
Open

Convert agenda item into work package#23339
oliverguenther wants to merge 1 commit into
devfrom
feat/turn-agenda-into-wp

Conversation

@oliverguenther
Copy link
Copy Markdown
Member

Copy link
Copy Markdown
Contributor

@HDinger HDinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall.
There is one issue I found when the item already has an outcome: the outcome is taken into the description of the WP, leading to effectivly duplicating the outcome:

Image

with_item_group(menu) do
add_note_action_item(menu) if add_note_action?
add_outcome_action_items(menu) if add_outcome_action?
convert_to_work_package_action_item(menu) if convert_to_work_package_action?
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Figma, the option is below "Copy link to clipboard" not below "add outcome".

),
method: "GET"
} }) do |item|
item.with_leading_visual_icon(icon: :"package-dependents")
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ticket says package-dependents whereas in Figma op-work-packages is used. Don't know which is supposed to be correct.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package-dependents is correct as is

@oliverguenther
Copy link
Copy Markdown
Member Author

oliverguenther commented May 26, 2026

There is one issue I found when the item already has an outcome: the outcome is taken into the description of the WP, leading to effectivly duplicating the outcome:

Yes that's true, we could skip outputting the outcomes to the descriptions altogether. I'm not sure what path we should take here. It is implemented as specified, and I'm not sure if it's a big deal to duplicate that

@oliverguenther oliverguenther force-pushed the feat/turn-agenda-into-wp branch 2 times, most recently from c6da733 to 03ba623 Compare May 26, 2026 12:37
@oliverguenther oliverguenther force-pushed the feat/turn-agenda-into-wp branch from 03ba623 to 981e2dc Compare May 26, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants