Changes for page Dependency-Track

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -76,7 +76,7 @@
76	76	Projects in the DevOps portal are mapped to the corresponding teams in Dependency-Track.
77	77	)))
78	78
79		-* When Dependency-Track is added as a tool to an existing or new project, a corresponding Dependency Track project is automatically created. Users assigned to the project in the DevOps Portal are then added to it with the roles defined in the configuration :
	79	+* When Dependency-Track is added as a tool to an existing or new project, a corresponding pris automatically created. Users assigned to the project in the DevOps Portal are then added to the subwiki with the roles defined in the configuration :
80	80	** Role mapping: (((
81	81	|=Project Role in DevOps Portal|=Permissions in Dependency-Track
82	82	|Admin|POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
...	...	@@ -83,6 +83,8 @@
83	83	|Master|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
84	84	|Developer|(% colspan="1" %)POLICY_VIOLATION_ANALYSIS, VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY, VULNERABILITY_ANALYSIS
85	85	|Viewer|VIEW_POLICY_VIOLATION, VIEW_PORTFOLIO, VIEW_VULNERABILITY
	86	+
	87	+A detailed description of the XWiki role model can be found [[here>>https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Access%20Rights/Permission%20types/]]
86	86	)))
87	87
88	88	= Main Features =
...	...	@@ -89,20 +89,32 @@
89	89
90	90	Inside DevOps-as-a-Service, deptrack is mainly used for writing specifications and documentations. See below for a list of the main features of XWiki.
91	91
92		-(% class="wikigeneratedid" id="HCollaborativeContentEditing" %)
93		-Auditing Basics
	94	+== Collaborative Content Editing ==
94	94
95		-(% class="wikigeneratedid" %)
96		-Dependency‑Track offers a robust auditing workflow: you can triage findings on individual projects, add comments, and record analysis decisions. The platform logs a complete audit trail for each action. Users with the VULNERABILITY_ANALYSIS permission can perform these audits, and audit histories are visible to anyone with the VIEW_VULNERABILITY permission. docs.dependencytrack.org +1
	96	+* WYSIWYG and wiki syntax editors
	97	+* Version control and history tracking
	98	+* Inline and structured content editing
	99	+* Commenting and annotations
97	97
98		-(% class="wikigeneratedid" %)
99		-Impact Analysis
	101	+== Advanced Page & Document Management ==
100	100
101		-(% class="wikigeneratedid" %)
102		-Dependency‑Track enables organizations to assess how a vulnerability affects their environment. If a vulnerability is published in a supported datasource (e.g., NVD, GitHub Advisories, OSS Index, VulnDB), the platform dynamically identifies all affected projects. This allows you to answer: "What is affected?" and "Where am I affected?" at a glance. docs.dependencytrack.org
	103	+* Hierarchical page structure (nested pages)
	104	+* Templates for creating structured documents
	105	+* Tags, categories, and metadata support
	106	+* File attachments and preview
103	103
104		-(% class="wikigeneratedid" %)
105		-3. Analysis States Dependency‑Track tracks the status of findings through their lifecycle via "analysis states". These help teams understand whether findings are new, under review, suppressed, or resolved. You can reference the Analysis States section in the documentation for full details on available statuses and workflows. docs.dependencytrack.org +1
	108	+== Powerful Search and Navigation ==
106	106
	110	+* Full-text search (Solr-based)
	111	+* Faceted search filters
	112	+* Page index, breadcrumbs, and navigation panels
107	107
	114	+== Macros and Widgets ==
	115	+
	116	+* Built-in and custom macros (charts, galleries, diagrams)
	117	+* Embedding of rich media (videos, iframes, etc.)
	118	+* Markdown and LaTeX support
	119	+
	120	+
	121	+
108	108