Uploaded image for project: 'Security Advisory Application'
  1. Security Advisory Application
  2. SPAPP-41

Allow to provide the impacted packages when creating an advisory

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • 2.3.0
    • None
    • Unknown

    Description

      When creating an advisory in the wiki, the edit form doesn't allow to provide its impacted packages (ecosystem, package identifier, vulnerable versions range, patched versions): the form only displays the impacted packages that already exist. The only way to add one is to click "Edit" > "Objects" after saving the advisory and add a SecurityAdvisoryImpactedPackageClass object, which requires the advanced user type.

      The patched versions of the impacted packages are needed to compute the embargo date, so an advisory created in the wiki can't get a computed embargo date without going through the object editor.

      Expected: the advisory edit form allows to add, edit and remove impacted packages.

      Attachments

        Activity

          People

            Unassigned Unassigned
            surli Simon Urli
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: