Skip to content

[2240] Update the choice of occurrence elements in portion kind creation tool selection dialog#2248

Merged
AxelRICHARD merged 1 commit into
mainfrom
gco/enh/filter-selectable-portionkind
Jun 2, 2026
Merged

[2240] Update the choice of occurrence elements in portion kind creation tool selection dialog#2248
AxelRICHARD merged 1 commit into
mainfrom
gco/enh/filter-selectable-portionkind

Conversation

@gcoutable
Copy link
Copy Markdown
Member

@gcoutable gcoutable commented May 28, 2026

Bug: #2240
Signed-off-by: Guillaume Coutable guillaume.coutable@obeo.fr

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@AxelRICHARD AxelRICHARD force-pushed the gco/enh/filter-selectable-portionkind branch from 4d7e671 to 0e7cb1a Compare June 2, 2026 08:14
Bug: #2240
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the gco/enh/filter-selectable-portionkind branch from 0e7cb1a to d77387f Compare June 2, 2026 09:01
@AxelRICHARD AxelRICHARD merged commit dfc5059 into main Jun 2, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the gco/enh/filter-selectable-portionkind branch June 2, 2026 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

On nodes, only allow to create timeslices & snapshots with the same type as the node on which they are created

2 participants