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

[CONCEPT] TraceX - it must be possible to define the issue far more granular #384

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

Comments

@wiegerterik
Copy link

Description

it must be possible to define it far more granular when and where an issue happened or should be checked

  • site / location

  • shift (date and time)

  • select 100 cars and start investigation for related engines

Impact

Important for business acceptance

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
@jzbmw
Copy link

jzbmw commented Jan 8, 2024

@wiegerterik discussion necessary regarding the 3rd bulletpoint.

@mkanal mkanal changed the title TraceX - it must be possible to define the issue far more granular [CONCEPT] TraceX - it must be possible to define the issue far more granular Jan 10, 2024
@jzbmw jzbmw added the open decision Mark issues that need special focus during planning label Jan 17, 2024
@mkanal
Copy link

mkanal commented Jan 22, 2024

Alignment during Open Refinement: 22.01.2024

  • Conceptual phase for this feature and/or conceptual meeting is required from Cofinity-X how to implement these features.
  • Technical solution concept is required.

@jzbmw

  • Get in contact with Trace-X Spec Team for further alignments

@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
@stephanbcbauer
Copy link
Member

Hello @wiegerterik

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 mkanal moved this from Work in progress to Done in Release Planning Jun 13, 2024
@mkanal
Copy link

mkanal commented Jun 13, 2024

Won't do. There will be not further contribution to this. There is no contribution for 24.8 as well.

@mkanal mkanal closed this as completed Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
foss RM FOSS definition 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