Skip to content

[1977] Display the PortionKind in the label of OccurrenceUsage graphical nodes#1985

Merged
AxelRICHARD merged 1 commit intomainfrom
gco/enh/portion-kind-prefix
Feb 12, 2026
Merged

[1977] Display the PortionKind in the label of OccurrenceUsage graphical nodes#1985
AxelRICHARD merged 1 commit intomainfrom
gco/enh/portion-kind-prefix

Conversation

@gcoutable
Copy link
Member

@gcoutable gcoutable commented Feb 11, 2026

Bug: #1977
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.

@gcoutable gcoutable linked an issue Feb 11, 2026 that may be closed by this pull request
@gcoutable gcoutable added this to the 2026.3.0 milestone Feb 11, 2026
@gcoutable gcoutable force-pushed the gco/enh/portion-kind-prefix branch 2 times, most recently from 4c38c3a to 5ce2eee Compare February 12, 2026 12:04
…cal nodes

Bug: #1977
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the gco/enh/portion-kind-prefix branch from 5ce2eee to 90b9f91 Compare February 12, 2026 15:22
@AxelRICHARD AxelRICHARD merged commit ddf7d17 into main Feb 12, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the gco/enh/portion-kind-prefix branch February 12, 2026 16:05
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.

Display the "timeslice" prefix

2 participants