Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TraceX - alerts / investigation cannot be forwarded within trace-X but new ones have to be set up (tiresome) #385

Closed
1 task done
wiegerterik opened this issue Dec 12, 2023 · 2 comments
Labels
foss RM FOSS definition PI12 CX-ART PI Issues Prep-PI12 CX-ART PI Preparation Issues for Consortia Planning trace-x Feature/Bug for Trace-x component

Comments

@wiegerterik
Copy link

wiegerterik commented Dec 12, 2023

Description

image

Additional requirement to increase the number of users and to allow using tracex even if suppliers are not yet a tracex user.
idea: view via invitation (“share this alert via mail and ask partners to register”)
-->

Link

Impact

Scalability and usage enabler

Additional information

  • I'm willing to contribute to this feature
@jzbmw jzbmw added trace-x Feature/Bug for Trace-x component Prep-PI12 CX-ART PI Preparation Issues for Consortia Planning foss RM FOSS definition labels Jan 8, 2024
@mkanal
Copy link

mkanal commented Jan 10, 2024

  • Trace-X should support forwarding of notifications in both directions over more tier levels respecting data sovereignty
  • Forwarding has to be acknowledged on each forwarding tier level
  • Responses for notifications should be forwards as well (acknowledge is required on tier level)

Questions/Considerations

  • As Trace-X MUST be interoperable with other solutions, this functionality might be standardized

Invitation of companies which are not C-X members (via email) should be a separate story.

@jzbmw jzbmw added the open decision Mark issues that need special focus during planning label Jan 17, 2024
@jzbmw jzbmw moved this from Inbox to Backlog in Release Planning Jan 22, 2024
@jzbmw jzbmw removed the open decision Mark issues that need special focus during planning label Jan 22, 2024
@jzbmw jzbmw added this to the 24.05 milestone Jan 23, 2024
@jzbmw jzbmw moved this from Backlog to Work in progress in Release Planning Jan 23, 2024
@mkanal mkanal added the PI12 CX-ART PI Issues label Feb 29, 2024
@jzbmw jzbmw moved this from Work in progress to Backlog in Release Planning Mar 19, 2024
@jzbmw jzbmw added the Prep-PI13 Open Planning Preparation Issues for R24.08 label Apr 10, 2024
@jzbmw jzbmw modified the milestones: 24.05, 24.08 Apr 10, 2024
@jzbmw jzbmw moved this from Backlog to Inbox in Release Planning Apr 10, 2024
@jzbmw jzbmw removed this from the 24.08 milestone Apr 10, 2024
@jzbmw jzbmw removed the Prep-PI13 Open Planning Preparation Issues for R24.08 label Apr 10, 2024
@mkanal mkanal moved this from Inbox to Backlog in Release Planning May 2, 2024
@MaximilianHauer
Copy link
Contributor

Closed by NSC because no progress. Please reopen and assign an upcoming release if needed.

@github-project-automation github-project-automation bot moved this from Backlog to Done in Release Planning Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
foss RM FOSS definition PI12 CX-ART PI Issues Prep-PI12 CX-ART PI Preparation Issues for Consortia Planning trace-x Feature/Bug for Trace-x component
Projects
Status: Done
Development

No branches or pull requests

4 participants