On user and organization pages, security advisory credit is currently lumped in with issue credit. Working on a security advisory generally requires more effort than the average issue. We should call those out more-prominently.

For organization pages, we may want to consider showing more than the last 3 months of security advisories. For user pages, we should go ahead and show all security advisories credited on.

The existing Views used for this on user & organization pages should be filtered to issues-only. Then add displays for the security advisories, and place them on the pages above issue credit.

Issue fork drupalorg-3220873

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drumm created an issue. See original summary.

drumm credited xjm.

drumm’s picture

This came up in a security team triage meeting.

drumm’s picture

To start, let’s show all security advisory credits on user pages, and the last 1 year on organization pages.

B_man made their first commit to this issue’s fork.

  • B_man committed 0bd8c6d on 7.x-3.x
    Issue #3220873 by B_man, drumm, xjm: Display security advisory credit...
B_man’s picture

Assigned: Unassigned » B_man
Status: Active » Fixed

Deployed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.