r3pek/log4j-affected-db
1
0
Fork 0
mirror of https://github.com/cisagov/log4j-affected-db.git synced 2024-11-26 18:30:18 +00:00
Code Releases Activity
log4j-affected-db/.github/ISSUE_TEMPLATE/product-update-form.yml

81 lines
2.3 KiB
YAML
Raw Normal View History

Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
---
name: Update a Product
description: Update information about a product in the database
title: "[Product Update]: <vendor> - <product>"
body:
Add inputs to product update form Add product vendor and product name inputs to the update form. This will ensure that even if a submitter does not update the title we capture this information.
2021-12-28 17:21:46 +00:00
- type: input
id: product-vendor
attributes:
label: Product vendor
description: Who is the vendor for the product?
placeholder: Cisco, Dell, IBM, etc.
validations:
required: true
- type: input
id: product-name
attributes:
label: Product name
description: What is the name of the product?
placeholder: AppDynamics, BigFix Inventory, Centera, etc.
validations:
required: true
Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
- type: textarea
id: update-context
attributes:
label: Context
Add missing punctuation in description in product update form
2021-12-28 17:39:38 +00:00
description: Please provide context around the update.
Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
- type: input
id: product-versions
attributes:
label: Product version(s)
description: What version(s) of the product are affected?
- type: dropdown
id: product-status
attributes:
label: Product status
description: What is the current status of the affected product?
options:
- Unknown
- Affected
- Not Affected
- Fixed
- Under Investigation
Adjust markdown element in product update form Move the markdown element that explains available statuses down so it appears close to where a user is selecting the status. Given how form elements are rendered it has been adjusted to appear after the dropdown itself. This mirrors changes made in the product submission form.
2021-12-28 15:54:24 +00:00
- type: markdown
attributes:
value: |
Please use the information below when selecting a status.
- Unknown - Status unknown. Default choice.
- Affected - Reported to be affected by CVE-2021-44228.
- Not Affected - Reported to NOT be affected by CVE-2021-44228 and no
further action necessary.
- Fixed - Patch and/or mitigations available (see provided links).
- Under Investigation - Vendor investigating status.
Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
- type: dropdown
id: product-updated
attributes:
Update dropdown in the product update form Update the product update dropdown's label and options. Mainly focused on removing usage of Yes/No because these are boolean values in YAML and thus needed special handling compared to other strings. This mirrors changes done to the product submission form.
2021-12-28 18:59:16 +00:00
label: Product update
Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
description: Is there an update available for the product?
options:
Update dropdown in the product update form Update the product update dropdown's label and options. Mainly focused on removing usage of Yes/No because these are boolean values in YAML and thus needed special handling compared to other strings. This mirrors changes done to the product submission form.
2021-12-28 18:59:16 +00:00
- Available
- Not Available
Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
- type: input
id: product-update-link
attributes:
label: Product update link
Update description for product update link in forms Update the description for the product update link input in both the product submission and product update forms. Co-authored-by: dav3r <david.redmin@trio.dhs.gov> Co-authored-by: Shane Frasier <jeremy.frasier@trio.dhs.gov>
2021-12-28 19:25:47 +00:00
description: Where can the update be found, if one is available?
Add missing input to issue forms Added an input to provide information about the date of a product's last update.
2021-12-27 01:32:00 +00:00
- type: input
id: product-last-updated
attributes:
label: Last updated
description: When was the product last updated?
Add a placeholder to the product issue forms Add a placeholder value for the last updated input in both the product submission and product update issue forms. This will encourage the appropriate timestamp format.
2021-12-28 17:45:46 +00:00
placeholder: "2021-12-06"
Add an issue form for product updates Provide an issue form for product updates to complement the one for product submissions. This will encourage people to follow the specific workflows for submissions and updates.
2021-12-27 01:23:20 +00:00
- type: textarea
id: product-notes
attributes:
label: Notes
- type: textarea
id: product-references
attributes:
label: References
Copy permalink