DependencyTrack / DependencyTrack/dependency-track

Jira ticket is missing affected project list for NEW_VULNERABILTIY notification

Open
#5,837 0 comments 1 reaction 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

In OWASP Dependency Track 4.13.6 the Jira alerts for NEW_VULNERABILTIY create tickets that are missing the affected projects.

Image

### Steps to Reproduce

1. Set up the Jira integration
3. Create a project as a collection of projects
4. Create an alert that uses the default Jira template for NEW_VULNERABILTIY and limit it to the previously created project and its children
5. Create a project with the previously created collection project as parent
6. Upload an SBOM with at least one vulnerable component to the project
7. Observe that OWASP Dependency Track creates a ticket for each vulnerability but all of them are missing the list of affected projects

### Expected Behavior

The ticket should contain a list of affected projects.

### Dependency-Track Version

4.13.6

### Dependency-Track Distribution

Container Image

### Database Server

PostgreSQL

### Database Server Version

_No response_

### Browser

Mozilla Firefox

### 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.