DependencyTrack / DependencyTrack/dependency-track

Inactive parent when its actual active

Open
#3,601 1 comment 0 reactions 0 assignees View on GitHub
defect in triage
Dominant language
Java
Stars
4.2k
Forks
811
Avg merge
8h 39m
Merged PRs (30d)
237

Description

### Current Behavior

I have 2 branches of the projetc:
- master
- release-test

Both projects are active on dep-track
![image](https://github.com/DependencyTrack/dependency-track/assets/77077842/78c69f9b-80cb-45d4-9dc8-432da38aa9ea)
(and it's not a web ui bug, the query gives the same information)

When I try to set the master project as parent for release-test it gives out:
request:
![image](https://github.com/DependencyTrack/dependency-track/assets/77077842/fcab6fe9-619a-4b9a-87ef-02b7d072c54d)
response:
![image](https://github.com/DependencyTrack/dependency-track/assets/77077842/038c6bde-6d81-410a-b576-851bcee92ac1)

#### UPDATE:
This problem is solved if, before assigning a parent to a child project, you send a post request updating the parent of the project and specifying active:true

### Steps to Reproduce

1.Create project via bom upload (with flag autocreate=true) via curl command
2. Try to create child project via curl (also with a bom upload and with flag autocreate=true)
4. Try to give parent for the child project via curl

### Expected Behavior

Parent for the active project is set correctly

### Dependency-Track Version

4.10.1

### Dependency-Track Distribution

Container Image

### Database Server

H2

### Database Server Version

_No response_

### Browser

N/A

### Checklist

- [X] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [X] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.