eclipse-tractusx / eclipse-tractusx/traceability-foss

Remove action sending Quality Alerts/Investigation on asPlanned Parts (all Views)

Open
#484 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

DISCUSSION_NEEDED frontend
Dominant language
Java
Stars
17
Forks
28
PR merge metrics
No merged PRs in 30d

Description

As an User
I want to have only logically justified actions available on asPlanned parts
so that I do not accidentally execute functionality without reasonable justification

Hints / Details

Acceptance Criteria

  • Function sending quality alerts is removed from asPlanned Views
  • Function sending quality investigation is removed from asPlanned Views

Out of Scope

  • ...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by locating the asPlanned views and the actions that send quality alerts or quality investigations, then trace how those actions are exposed across all views. Done means neither action is available in any asPlanned view and the affected behavior is covered by the relevant existing checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.