Skip to content

Conversation

@gcoutable
Copy link
Member

@gcoutable gcoutable commented Jan 12, 2026

Bug: #1828
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 added this to the 2026.1.0 milestone Jan 12, 2026
@gcoutable gcoutable marked this pull request as draft January 12, 2026 16:38
@gcoutable gcoutable force-pushed the gco/enh/implements-derived-ref-usecase branch from 72eabe1 to 53ee916 Compare January 13, 2026 14:03
@gcoutable gcoutable marked this pull request as ready for review January 13, 2026 14:13
Copy link
Member

@AxelRICHARD AxelRICHARD left a comment

Choose a reason for hiding this comment

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

I will fix the comment, rebase and merge the PR, thank you!

Bug: #1828
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@AxelRICHARD AxelRICHARD force-pushed the gco/enh/implements-derived-ref-usecase branch from 53ee916 to b12bac4 Compare January 13, 2026 15:54
@AxelRICHARD AxelRICHARD merged commit c0e707c into main Jan 13, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the gco/enh/implements-derived-ref-usecase branch January 13, 2026 19:53
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.

Implement missing derived references of UseCaseUsage and UseCaseDefinition

3 participants