aboutsummaryrefslogtreecommitdiffstats
path: root/sonar-core
diff options
context:
space:
mode:
authorViktor Vorona <viktor.vorona@sonarsource.com>2024-11-19 13:40:26 +0100
committersonartech <sonartech@sonarsource.com>2024-11-21 20:02:47 +0000
commit329046215eb485837bf33161fa4bcccc24e96395 (patch)
tree6edcb89075323064a7f8e483937ffa56b5e808c1 /sonar-core
parent865b3112294654f3f3bbf1fd25d7520a397bbf30 (diff)
downloadsonarqube-329046215eb485837bf33161fa4bcccc24e96395.tar.gz
sonarqube-329046215eb485837bf33161fa4bcccc24e96395.zip
SONAR-23653 Replace tours with Popovers
Diffstat (limited to 'sonar-core')
-rw-r--r--sonar-core/src/main/resources/org/sonar/l10n/core.properties38
1 files changed, 9 insertions, 29 deletions
diff --git a/sonar-core/src/main/resources/org/sonar/l10n/core.properties b/sonar-core/src/main/resources/org/sonar/l10n/core.properties
index 94f23f8c2c5..c9381b53d47 100644
--- a/sonar-core/src/main/resources/org/sonar/l10n/core.properties
+++ b/sonar-core/src/main/resources/org/sonar/l10n/core.properties
@@ -1236,6 +1236,9 @@ issues.facet.severities=Severity
issues.facet.scopes=Scope
issues.facet.projects=Project
issues.facet.issueStatuses=Status
+issues.facet.issueStatuses.help.title=Simplified issue lifecycle
+issues.facet.issueStatuses.help.description=<p1>Issue Resolution and Issue Status were merged and there are now five possible statuses in the issue lifecycle.</p1><p>Won't Fix was replaced with Accept. Marking issues as Confirmed and Fixed was deprecated.</p>
+issues.facet.issueStatuses.help.link=Learn more about new issue lifecycle
issues.facet.hotspotStatuses=Hotspot Status
issues.facet.assignees=Assignee
issues.facet.files=File
@@ -1245,7 +1248,12 @@ issues.facet.tags=Tag
issues.facet.rules=Rule
issues.facet.languages=Language
issues.facet.cleanCodeAttributeCategories=Clean Code Attribute
+issues.facet.cleanCodeAttributeCategories.help.title=Attributes group together conceptually similar issues.
+issues.facet.cleanCodeAttributeCategories.help.link=Learn more about clean code attributes
issues.facet.impactSoftwareQualities=Software Quality
+issues.facet.impactSoftwareQualities.help.title=What are software qualities?
+issues.facet.impactSoftwareQualities.help.description=<p1>Security is the protection of your software from unauthorized access, use, or destruction.</p1><p>Reliability is a measure of how your software is capable of maintaining its level of performance under stated conditions for a stated period of time.</p><p>Maintainability refers to the ease with which you can repair, improve and understand software code.</p>
+issues.facet.impactSoftwareQualities.help.link=Learn more about software qualities
issues.facet.codeVariants=Code Variant
issues.facet.createdAt=Creation Date
issues.facet.createdAt.all=All
@@ -3121,8 +3129,7 @@ severity_impact.LOW=Low
severity_impact.LOW.description=Potential for moderate to minor impact.
severity_impact.INFO=Info
severity_impact.INFO.description=Neither a bug nor a quality flaw. Just a finding.
-severity_impact.help.line1=Severities are now directly tied to the software quality impacted. This means that one software quality impacted has one severity.
-severity_impact.help.line2=They can be changed with sufficient permissions.
+severity_impact.help.description=<p1>Severities are now directly tied to the software quality impacted. This means that one software quality impacted has one severity.</p1><p>They can be changed with sufficient permissions.</p>
#------------------------------------------------------------------------------
#
@@ -5886,31 +5893,4 @@ component_report.unsubscribe_success=Subscription successfully canceled. You won
# GUIDING
#
#------------------------------------------------------------------------------
-guiding.issue_list.1.title=Introducing Clean Code Attributes
-guiding.issue_list.1.content.1=Clean Code attributes are the characteristics that your code must have to be considered Clean Code.
-guiding.issue_list.1.content.2=You can now filter by these attributes to evaluate why your code is breaking away from being clean.
-guiding.issue_list.2.title=Introducing Software Qualities
-guiding.issue_list.2.content.1=A software quality is a characteristic of software that contributes to its lasting value.
-guiding.issue_list.2.content.2=You can now filter by these qualities to evaluate the areas in your software that are impacted by the introduction of code that isn't clean.
-guiding.issue_list.3.title=Severity and Software Qualities
-guiding.issue_list.3.content.1=Severities are now directly tied to the software quality impacted. This means that one software quality impacted has one severity.
-guiding.issue_list.3.content.2=There are five levels: blocker, high, medium, low and info.
-guiding.issue_list.4.title=Type and old severity deprecated
-guiding.issue_list.4.content.1=Issue types and the old severities are deprecated and can no longer be modified.
-guiding.issue_list.4.content.2=You can now filter issues by:
-guiding.issue_list.4.content.list.1=Clean Code Attributes
-guiding.issue_list.4.content.list.2=Software Qualities
-guiding.issue_list.4.content.list.3=The severity of the software quality
-guiding.issue_list.5.title=Learn more
-guiding.issue_list.5.content=You can learn more about the approach to Clean Code in the {link}
-guiding.issue_accept.1.title=Simplified issue lifecycle
-guiding.issue_accept.1.content.1=Issue resolution and Issue status are now merged and there are only 5 possible statuses: Open, Accepted, False Positive, Confirmed and Fixed.
-guiding.issue_accept.2.title=Won't Fix becomes Accept
-guiding.issue_accept.2.content.1=Won't Fix is now called Accept and it keeps the same behaviour for now.
-guiding.issue_accept.2.content.2=In the future, Accepting issues will be counted as technical debt.
-guiding.issue_accept.2.content.link=Learn more about this status
-guiding.issue_accept.3.title=Confirm and Fixed deprecated
-guiding.issue_accept.3.content.1=Marking issues as Confirmed and Fixed is now deprecated.
-guiding.issue_accept.3.content.2=Consider Accepting issues, assigning the issue or using comments and tags instead.
-guiding.issue_accept.3.content.link=Learn more about issues statuses
guiding.step_x_of_y={0} of {1}