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

Affected project name not shown in Jira ticket summary for NEW_VULNERABLE_DEPENDENCY notification type #3744

Closed
2 tasks done
lgrguricmileusnic opened this issue May 22, 2024 · 1 comment · Fixed by #3745
Closed
2 tasks done
Labels
defect Something isn't working good first issue Good for newcomers integration/jira Related to the Jira integration p2 Non-critical bugs, and features that help organizations to identify and reduce risk size/S Small effort
Milestone

Comments

@lgrguricmileusnic
Copy link
Contributor

Current Behavior

Currently, the name of the project containing the vulnerable dependency is not being shown in the ticket summary (title), when using the default Jira publisher and NEW_VULNERABLE_DEPENDENCY. This is happening because of a mistake in the project name identifier "subject.dependency.project.name" in the default Jira Pebble template, where "dependency" should actually be "component" or "subject.component.project.name" in full.

Steps to Reproduce

  1. Enable Jira Integration with DependencyTrack
  2. Create a DT project
  3. Create alert which uses the default Jira publisher and notification of type NEW_VULNERABLE_DEPENDENCY
  4. Limit alert to created project (possibly optional)
  5. Add a vulnerable component to the project via BOM upload or manually

Created ticket doesn't contain affected project name in ticket summary (title).

Expected Behavior

Ticket summary should contain project name as intended by the current version of the template.

Dependency-Track Version

4.11.0

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

No response

Browser

N/A

Checklist

@lgrguricmileusnic lgrguricmileusnic added defect Something isn't working in triage labels May 22, 2024
@nscuro nscuro added p2 Non-critical bugs, and features that help organizations to identify and reduce risk good first issue Good for newcomers size/S Small effort integration/jira Related to the Jira integration and removed in triage labels May 22, 2024
@nscuro nscuro added this to the 4.12 milestone May 23, 2024
@nscuro nscuro modified the milestones: 4.12, 4.11.2 Jun 1, 2024
Copy link
Contributor

github-actions bot commented Jul 1, 2024

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
defect Something isn't working good first issue Good for newcomers integration/jira Related to the Jira integration p2 Non-critical bugs, and features that help organizations to identify and reduce risk size/S Small effort
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants