Skip to content

[2237] Leverage the selection dialog to create framed concern usages#2238

Open
gcoutable wants to merge 4 commits into
gco/enh/frames-compartmentfrom
gco/fix/frames-compatment-item-label
Open

[2237] Leverage the selection dialog to create framed concern usages#2238
gcoutable wants to merge 4 commits into
gco/enh/frames-compartmentfrom
gco/fix/frames-compatment-item-label

Conversation

@gcoutable
Copy link
Copy Markdown
Member

@gcoutable gcoutable commented May 22, 2026

  • [2237] Leverage the selection dialog to create framed concern usages

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 added 3 commits May 21, 2026 17:12
Bug: #2231
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
Bug: #2231
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
Bug: #2231
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@gcoutable gcoutable added this to the 2026.7.0 milestone May 22, 2026
@gcoutable gcoutable changed the base branch from main to gco/enh/frames-compartment May 22, 2026 15:08
@gcoutable gcoutable force-pushed the gco/fix/frames-compatment-item-label branch from 8b50992 to 8ff0be0 Compare May 22, 2026 15:11
@gcoutable gcoutable marked this pull request as ready for review May 22, 2026 15:21
@gcoutable gcoutable requested a review from AxelRICHARD May 22, 2026 15:21
@AxelRICHARD AxelRICHARD force-pushed the gco/enh/frames-compartment branch from a0e1c74 to e9ceedc Compare May 22, 2026 16:14
Bug: #2237
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@gcoutable gcoutable force-pushed the gco/fix/frames-compatment-item-label branch from 8ff0be0 to 1ac40c8 Compare May 22, 2026 16:17
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.

The item label of some RequirementUsage and RequirementDefinition compartments is not right

1 participant