Skip to content

move skeleton service element requirements - #1007

Open
sahithi-nukala wants to merge 2 commits into
eclipse-score:mainfrom
sahithi-nukala:sah_mv_skeleton_service_element_requirements
Open

move skeleton service element requirements#1007
sahithi-nukala wants to merge 2 commits into
eclipse-score:mainfrom
sahithi-nukala:sah_mv_skeleton_service_element_requirements

Conversation

@sahithi-nukala

Copy link
Copy Markdown
Contributor

No description provided.

@sahithi-nukala
sahithi-nukala force-pushed the sah_mv_skeleton_service_element_requirements branch from 67892b4 to 5d29861 Compare August 25, 2026 14:46
@sahithi-nukala
sahithi-nukala marked this pull request as ready for review August 26, 2026 06:52

@LittleHuba LittleHuba left a comment

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.

@crimson11 @bemerybmw is it fine if we loose some old linkage here?
E.g. we had previously 26 linked requirements and now only 7.

@bemerybmw

Copy link
Copy Markdown
Contributor

@crimson11 @bemerybmw is it fine if we loose some old linkage here? E.g. we had previously 26 linked requirements and now only 7.

No, we should not lose any linkages. Only the requirements which have been moved should be changed, the old ones should stay as they are and should be updated when they're moved. I think something like this would be fine:

RecordProperty("Verifies", "SCR-17563743, SCR-21553554");
RecordProperty("lobster-tracing", "Communication.SkeletonFieldClassUpdate");

Then when SCR-17563743 and SCR-21553554 are moved to the correct location, they can be added to the lobster-tracing section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

3 participants