Skip to content

Deprecated techniques should not show any content #116

@isaisabel

Description

@isaisabel

As a maintainer of ATT&CK, I want to make sure people don't continue to use deprecated techniques, but I want users to be able to tell that a technique is deprecated and the justification for the deprecation.

The first paragraph of a deprecated technique's description in the STIX should be the deprecation justification and/or a list of replacing objects. Further paragraphs of the description (the previous content of the object) will be omitted from the page. They’ll persist in the STIX but not on the site.

The "DEPRECATED" marking will be added automatically and needn't be added to the first paragraph of the deprecated object's description.

Metadata

Metadata

Labels

enhancementNew feature or requestpriority/highHigh priority Issuetimescale/imminentReady to be assigned to developersuiThe user interface can be improved

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions