dependency-track icon indicating copy to clipboard operation
dependency-track copied to clipboard

[Notifications] Empty Affected project(s) in JIRA when limit to parent project and Group NEW_VULNERABILITY

Open snieguu opened this issue 2 years ago • 3 comments

Current Behavior

The Child project is not listed in created JIRA ticket in the Affected project(s) section when Alert is limited to the Parent Project. Technically it seems that the template field subject.affectedProjects is empty, however, it is filled correctly when Limit to projects is removed from JIRA alert configuration.

Steps to Reproduce

  1. Create a Parent project
  2. Create Jira Alert with:
    • Publisher set to Jira
    • Scope set to PORTFOLIO
    • Group set to NEW_VULNERABILITY
    • limit to->Limit to projects set to Parent project
    • Notification Level set to INFORMATIONAL
    • Configure Destination and Jira ticket type

JiraAlert

  1. Create a Child project which is a child of Parent project
  2. Upload sbom(With vulnerability) to Child project
  3. Observe that created ticket in JIRA has an empty section Affected project(s) in the description

AffectedProjects

Expected Behavior

Created Ticket in JIRA should contain the Child project in the Affected project(s) section in the description.

Dependency-Track Version

4.8.2

Dependency-Track Distribution

Container Image

Database Server

PostgreSQL

Database Server Version

11.13.0

Browser

Other

Checklist

snieguu avatar Jun 29 '23 10:06 snieguu

Can confirm we are seeing the same behavior. Leaving the comment to bump the issue so the fix hopefully gets prioritized.

jovanz-getbgd avatar Nov 01 '23 12:11 jovanz-getbgd

Also detected same behaviour.

lgrguricmileusnic avatar Dec 05 '23 13:12 lgrguricmileusnic

This issue still appears in version 4.10.1. It would be great if child projects would be included in the listing. Our use case is to group different versions under a parent project so that notification for the parent can be sent to one corresponding Jira project. Hence, it is relevant to know which version / which child project is the one affected by the vulnerability.

Is there perhaps a workaround to access child projects in the template syntax?

rogu-beta avatar Mar 15 '24 12:03 rogu-beta