[Trace-X] R24.5 Release Checks

[mkanal]

Important

Follow the guidance on how to use the templates.

RELEASE

• HELM Charts: 1.3.38
• Release 11.0.1

Release Info

Please provide information on what you want to be included in the Eclipse Tractus-X release.
If you are not owner of this issue, please provide the information as comment to the issue.
Make sure to assign this issue to expert(s) for their approval, as soon as you have finished preparation. Multiple assignees allowed; they will un-assign themselves once review completed.

Version to be included in Eclipse Tractus-X release: 11.0.1
Leading product repository: https://github.com/eclipse-tractusx/traceability-foss/

Compliance Verifications

This issue tracks all checks, that need to be performed for a product release in Eclipse Tractus-X.

• Interoperability checks performed
• Data Sovereignty checks performed
  Data Sov Tests in progress: Final alignment on Wednesday. https://jira.catena-x.net/browse/TEST-1918

General Checks

• Tractus-X Release Guidelines(TRGs) fulfilled QG 4 checks (Release 24.05) traceability-foss#955
• UUX Checks Compliant with the Style Guide
  • AppWalkThrough on 8.5.2024 @jjeroch
  • UUX Review of app
  • Provided user accounts for Trace-X Instances Trace-X and BMW
    [Trace-X] R24.5 Release Checks #611 (comment)

Note

Note: most criteria for documentation and security are now covered in TRGs

Security Checks

• Thread Modelling Analysis passed

Test Results

• E2E Integration Test passed
  https://jira.catena-x.net/browse/TEST-1887 Done
  https://jira.catena-x.net/browse/TEST-1892 Done
  https://jira.catena-x.net/browse/TEST-1888 Done
  Findings:
• CLOSED [Bug] Title not received after sending notification traceability-foss#956 (identified as not a bug - so I closed it again)
• OPEN [R24.5][Bug] Not all affected parts are received after sending notification traceability-foss#957
• OPEN [R24.5][Bug] Available parts filter is falsely reset traceability-foss#958
• User Journey approved

Helpful Links

• Eclipse Tractus-X openAPI specs on SwaggerHub

[mkanal]

User journey was approved by PO @jzbmw.

[mkanal]

Good morning @guenterban, @bs-jokri, @pablosec,

in both products (Trace-X FOSS and IRS) there are no relevant system-related changes compared to R23.12 and R24.3. For this reason, we request the release of the QGC "Threat Modeling Analysis passed" based on version R23.12 & R24.3.
If you come to a different conclusion, we will be happy to provide you with dates for the threat modeling analysis.

Sig-Release:
Trace-X: #611
IRS: #670

Thank you very much
IRS and Trace-X Team

[mkanal]

Good morning @almadigabor,

would you please again support the Team Trace-X regarding TRG checks for the upcoming release R24.5?

Thank you very much

Martin

[guenterban]

Threat Modeling Analysis approved

[almadigabor]

I've opened the TRG checks issue for Trace-X. eclipse-tractusx/traceability-foss#955

[ThomasObermeyer]

Performed interoperability QGate review based on the provided information:

ItemRelationShipService:
#670

Updated Interoperability Documents:
2024-05-13 R24.5 InterOp for TraceX and IRS

@kelaja Approved!

[cbrugg]

E2E Tests were successfully performed. INT Tests need to be documented/updated. Data Sov Tests outstanding. Thank You!

[RolaH1t]

QG review 14-May:
data sov in progress; no blockers expected
TRG completion soon expected; successful collaboration across products & with SystemTeam
two findings identified within E2E tests; will be fixed with patch version
minor version expected for final release (11.0.1 & 1.3.38)
no follow-up mtg required

[KMA-2019]

@vialkoje , @cbrugg , @mkanal as aligned referencing here notes / feedback from E2E Tests for Data Sovereignty.
No blocking issues for current Rel 24.05 but main items to be considered for next release(s):

• Note: additional tests (from customer perspective) only partially possible
• specific usage policies not transparent enough - in UI for Admin Role: "publish Asset" only shows name of policy, not actual policies, i.e. create contract offer, as well as in contract view (at time of test not working correctly --> planned for 24.08)
• app relies mainly on backend configuration of policies, no UI yet for definition and maintenance of Company specific Rules
• concept of default policy to be used in case no specific one is available for auto-negotiation should be re-assessed with customer base
• currently no check for traceability specific FrameworkAgreement Constraint, successfull negotiation with Quality Framework (align with upcoming changes to Data Exchange Governance by Association / in ORDL Repo)
• ContractReference Constraint can be manually added, however not obvious to configure policies specific to ONE partner only
• in case of non-matching policies (tested in various scenarios) no negotiation takes place but there is not visualization or specific Error message to user
• no validation of the Schema "profile": "cx-policy:profile2405" (required to ensure interop with other traceability apps) --> planned interface with Policy Hub, requires check of dev dependencies

[vialkoje]

@vialkoje Data Sov Tests were performed successfully as referenced in the Ticket above (next to the Data Sov Checkmark). From Testmanagement perspective I can give my approval as there are only PASSED and N/A. In how far this substitutes an alignment with you and the Trace X Team I may not say.

I'd expect that there is either a written evaluation of the QG-Checklist https://confluence.catena-x.net/x/NTeJBg - which may refer to successfully passed tests or an invitation for an alignment via telco with me to make sure the sovereignty criteria are passed successfully. The Test-cases themself are not sufficient.

[ds-lcapellino]

Hi @vialkoje,
Trace-X uses the IRS for EDC communication and the Policy-Store for managing policies. Since IRS is compliant to the Dava Sov QGate criteria as seen here (
#670 (comment))
and tested by (https://jira.catena-x.net/browse/TEST-1918?focusedCommentId=83975&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel), I kindly ask for Data Sov approval.

[cbrugg]

As discussed in the Daily TM approval is given if UI/UX findings are identified as Known Knowns and adressed in R24.08. Thank you.

[RolaH1t]

Hi @ds-crehm and @ds-lcapellino
I believe @mkanal is unavailable these days - so may I ask you to finally close-out the last items on data sov and documentation of knownknowns?
Pls reach out to a committer to also formally check the boxes on top once completed.
Hope we can fully approve the QG asap

[ds-lcapellino]

Hi @RolaH1t,
yes, @mkanal is currently on vacation.
For the known kowns, we have created a new release, which addresses most of the findings. However, we listed all of them on the release page: https://github.com/eclipse-tractusx/traceability-foss/releases/tag/11.0.1
Regarding data sov, we are currently in contact with @vialkoje.

@cbrugg, @jjeroch: I kindly ask you for your approval by checking the boxes on the top.
Thank you very much!

[ds-mmaul]

Hi @cbrugg , @jjeroch ,
Thank you for the feedback. For the new release 11.0.1 we worked on the UUX findings with the highest priority. Here you can find the current state of the findings (Also listed in known knowns of the latest release):

User Experience

ITEM 1 → Done with eclipse-tractusx/traceability-foss#989

ITEM 2 → Done with eclipse-tractusx/traceability-foss#914

ITEM 3 → Done with eclipse-tractusx/traceability-foss#991

ITEM 4 → Done with eclipse-tractusx/traceability-foss#992

ITEM 5 → Not replicable, will be investigated

ITEM 6 → not blocking, issue existing, will be implemented

ITEM 7, 8, 9 → Done with eclipse-tractusx/traceability-foss#994

ITEM 10 → Done with eclipse-tractusx/traceability-foss#995

ITEM 11 → not blocking, issue existing, will be implemented

ITEM 12 → Done with eclipse-tractusx/traceability-foss#915

ITEM 13 → Done with eclipse-tractusx/traceability-foss#997

ITEM 14 → Done with eclipse-tractusx/traceability-foss#998

ITEM 15 → Issue existing, will be conceptualized and implemented

Styleguide Compliance

ITEM 1 → Issue existing, will be conceptualized and implemented

ITEM 2 → Done with eclipse-tractusx/traceability-foss#914

ITEM 3 → Done with eclipse-tractusx/traceability-foss#914

ITEM 4 → Done as part of eclipse-tractusx/traceability-foss#913

Responsiveness

ITEM 1 → Issue existing, will be conceptualized and implemented

ITEM 2 → not blocking, will be implemented

ITEM 3 → Not replicable, will be investigated

We hope that this is sufficient to get your approval. Thank you very much!

[ds-lcapellino]

Hi @cbrugg , @jjeroch ,
Thank you for the feedback. For the new release 11.0.1 we worked on the UUX findings with the highest priority. Here you can find the current state of the findings (Also listed in known knowns of the latest release):

User Experience

ITEM 1 → Done with eclipse-tractusx/traceability-foss#989

ITEM 2 → Done with eclipse-tractusx/traceability-foss#914

ITEM 3 → Done with eclipse-tractusx/traceability-foss#991

ITEM 4 → Done with eclipse-tractusx/traceability-foss#992

ITEM 5 → Not replicable, will be investigated

ITEM 6 → not blocking, issue existing, will be implemented

ITEM 7, 8, 9 → Done with eclipse-tractusx/traceability-foss#994

ITEM 10 → Done with eclipse-tractusx/traceability-foss#995

ITEM 11 → not blocking, issue existing, will be implemented

ITEM 12 → Done with eclipse-tractusx/traceability-foss#915

ITEM 13 → Done with eclipse-tractusx/traceability-foss#997

ITEM 14 → Done with eclipse-tractusx/traceability-foss#998

ITEM 15 → Issue existing, will be conceptualized and implemented

Styleguide Compliance

ITEM 1 → Issue existing, will be conceptualized and implemented

ITEM 2 → Done with eclipse-tractusx/traceability-foss#914

ITEM 3 → Done with eclipse-tractusx/traceability-foss#914

ITEM 4 → Done as part of eclipse-tractusx/traceability-foss#913

Responsiveness

ITEM 1 → Issue existing, will be conceptualized and implemented

ITEM 2 → not blocking, will be implemented

ITEM 3 → Not replicable, will be investigated

We hope that this is sufficient to get your approval. Thank you very much!

[vialkoje]

As IRS functionality is used: Configuration of acceptable policies in the IRS has to be communicated to the consuming entity - along with the fact to arbitrarily chose the first acceptable offer if multiple exist. Please point me to the documentation where this is described. Technically everything is implemented. Expert approval granted.

[cbrugg]

Thank you @ds-lcapellino as written above Testmanagement approval is hereby given as the issues are adressed as known knowns. I myself cannot check the boxes can a contributor of your team take care of this? Thanks!

[ds-lcapellino]

Thank you for your feedback @vialkoje @cbrugg. We will update the checkboxes in the description accordingly.
I've created eclipse-tractusx/traceability-foss#1007 to address the data sov aspects in Trace-X and the things @vialkoje pointed out.
Thanks to everyone!

[jjeroch]

Hi @cbrugg , @jjeroch , Thank you for the feedback. For the new release 11.0.1 we worked on the UUX findings with the highest priority. Here you can find the current state of the findings (Also listed in known knowns of the latest release):

User Experience

ITEM 1 → Done with eclipse-tractusx/traceability-foss#989

ITEM 2 → Done with eclipse-tractusx/traceability-foss#914

ITEM 3 → Done with eclipse-tractusx/traceability-foss#991

ITEM 4 → Done with eclipse-tractusx/traceability-foss#992

ITEM 5 → Not replicable, will be investigated

ITEM 6 → not blocking, issue existing, will be implemented

ITEM 7, 8, 9 → Done with eclipse-tractusx/traceability-foss#994

ITEM 10 → Done with eclipse-tractusx/traceability-foss#995

ITEM 11 → not blocking, issue existing, will be implemented

ITEM 12 → Done with eclipse-tractusx/traceability-foss#915

ITEM 13 → Done with eclipse-tractusx/traceability-foss#997

ITEM 14 → Done with eclipse-tractusx/traceability-foss#998

ITEM 15 → Issue existing, will be conceptualized and implemented

Styleguide Compliance

ITEM 1 → Issue existing, will be conceptualized and implemented

ITEM 2 → Done with eclipse-tractusx/traceability-foss#914

ITEM 3 → Done with eclipse-tractusx/traceability-foss#914

ITEM 4 → Done as part of eclipse-tractusx/traceability-foss#913

Responsiveness

ITEM 1 → Issue existing, will be conceptualized and implemented

ITEM 2 → not blocking, will be implemented

ITEM 3 → Not replicable, will be investigated

We hope that this is sufficient to get your approval. Thank you very much!

Hi @ds-lcapellino thanks a lot. Known Knowns are looking good. Can you please share a trace-x version where the fixes can get tested.

[ds-mwesener]

Hi @jjeroch it is included in the latest release 11.0.1 of trace-x and deployed on:

https://traceability-portal-int-a.int.demo.catena-x.net

Please use your own user and realm: BMW.

If you have any questions please let me know.

Thanks in advance.

Kind regards

[KMA-2019]

Hi @ds-mwesener, @ds-lcapellino, @mkanal, cc: @jjeroch
Regarding UUX findings please see the retest results:

All items not mentioned below have been retested successfully. Thanks!
Note: User Experience, ITEM 5 – blocking - Scroll Bar now existing, can also be closed

**Still open are the following.
@jjeroch can you please review and decide about granting final approval. **

User Experience

ITEM 6 – not blocking - issue existing, will be investigated eclipse-tractusx/traceability-foss#993

• ITEM 9 – blocking - no change for user. Still there is no option to edit/change and hence the Icon and Counter do not make sense to the user.

ITEM 11 – not blocking - issue existing, will be implemented eclipse-tractusx/traceability-foss#996

• ITEM 12 – blocking - has been updated, Thanks. Noticed, though, that HELP is missing Section for “Administration -> BPN – EDC Configuration”

• !! ITEM 13 – blocking – thanks for providing more test data. Now multiple Policies are available. However, still cannot see relevant policy details. !!

ITEM 15 – blocking - Issue existing, will be conceptualized and implemented eclipse-tractusx/traceability-foss#1001

Styleguide Compliance

ITEM 1 – blocking - Issue existing, will be conceptualized and implemented eclipse-tractusx/traceability-foss#1001

• ITEM 2 – blocking - Information of Record Numbers available. However, frame still missing (see out of scope in [CONCEPT] Improve UUX on quality incidents widget on Dashboard traceability-foss#914) , “View All” Button is now completely disabled and not only when table is empty or few entries.

• ITEM 3 – blocking – see ITEM 2 for different table

Responsiveness

ITEM 1 – blocking - Issue existing, will be conceptualized and implemented eclipse-tractusx/traceability-foss#999
ITEM 2 – not blocking - will be implemented eclipse-tractusx/traceability-foss#787
ITEM 3 – blocking - not replicable, will be investigated eclipse-tractusx/traceability-foss#1000

Old comments (leftovers)

o TRACEFOSS-897 (and moved to eclipse-tractusx/traceability-foss#491)

- @ds-mwesener Can you please comment on these two items?

[jjeroch]

UI/UX Findings existing, still gateway approved with documentation of findings inside the changeLogs under KnownKnowns

[RolaH1t]

@almadigabor may I ask you to complete the final checkbox on top, so QG can be approved? THX

[almadigabor]

Hey @RolaH1t, do you mean the "UUX Checks Compliant with the Style Guide" box? That's the only unchecked box I see. I can mark it, though I don't really know the process behind.

[RolaH1t]

yes, please => thats the one Currently there is not (yet) a process behind, because the relevant TRG is still in draft => but pls refer to @jjeroch s comment this morning (see above)

[RolaH1t]

Congrats:
Quality Gate fully approved with all necessary pre-requisites fulfilled!
Thanks for all your efforts,
Roland

[ds-mwesener]

Congrats: Quality Gate fully approved with all necessary pre-requisites fulfilled! Thanks for all your efforts, Roland

Thank you very much! We appreciate it!

[stephanbcbauer]

Hello @mkanal

Since the feature is a 24.05 feature and the development phase for 24.08 is coming to an end, we need a status on the feature. Can you please update the status?

• Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• Please check whether the status (backlog, work in progress ...) is set correctly
• Please comment on the current status of the feature
• Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.
• Is there a spillover planned?

If you need any clarification, please get in touch, thank you very much.

Stephan

[mkanal]

"Congrats:
Quality Gate fully approved with all necessary pre-requisites fulfilled!
Thanks for all your efforts,
Roland"
Ticket will be set as done and set to close.