This issue has been created
There are 2 updates.
 
 
Security Advisory Application / cid:jira-generated-image-avatar-e6adb0c2-ea46-407f-a13d-5a1ee7fcac8d SPAPP-31 Open

Embargo date is not recomputed if a new version is added after it has been computed

 
View issue   ยท   Add comment
 

Issue created

 
cid:jira-generated-image-avatar-7c6f2216-8f32-4a4b-bcf3-7d4e720c6e70 Simon Urli created this issue on 01/Jul/26 10:05
 
Summary: Embargo date is not recomputed if a new version is added after it has been computed
Issue Type: cid:jira-generated-image-avatar-e6adb0c2-ea46-407f-a13d-5a1ee7fcac8d Bug
Affects Versions: 2.0.0
Assignee: Unassigned
Created: 01/Jul/26 10:05
Priority: cid:jira-generated-image-static-major-d0714ee5-27df-4f98-88c3-776da8f65425 Major
Reporter: Simon Urli
Description:

Reproduction steps:

  • Create an advisory with 2 patched versions and mark it announced
  • Creates the release notes for those versions
  • Embargo date is computed as well as release dates
  • Update the advisory to add another patched version
  • Create a release note for that version

Expected result:

  • the advisory is updated to mark the version released and to update the embargo date

Obtained result:

  • the version is always marked not released and the embargo date is not updated
 
 

2 updates

 
cid:jira-generated-image-avatar-7c6f2216-8f32-4a4b-bcf3-7d4e720c6e70 Changes by Simon Urli on 01/Jul/26 10:05
 
Fix Version: 2.1.0
Assignee: Simon Urli