You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clean: Refactor docs on configuring who can ignore issues CY-3647 (#516)
* clean: Move "which users can ignore issues" to "roles and permissions"
* clean: Link "Configurable" cells in table to new section
* style: Tweak admonition indicating availability of feature
* clean: Link "which users can ignore issues" and "Ignoring an issue"
* fix: Adjust heading level
* fix: Update URL fragment link
* fix: Update superscript numeral
@@ -161,7 +161,7 @@ Depending on your role on the Git provider you will have different permissions o
161
161
</tr>
162
162
<tr>
163
163
<td rowspan="2">Bitbucket Cloud and Bitbucket Server</td>
164
-
<td>Read, Write<sup><a href="#note-4">4</a></td>
164
+
<td>Read, Write<sup><a href="#note-3">3</a></td>
165
165
<td>Yes<sup><a href="#note-2">2</a></sup></td>
166
166
<td>No</td>
167
167
<td>No</td>
@@ -185,7 +185,16 @@ Depending on your role on the Git provider you will have different permissions o
185
185
186
186
<supid="note-1">1</sup>: Outside Collaborators and External Users aren't supported as Members of organizations on Codacy. However, you can [add them](managing-people.md#adding-people) so that Codacy analyzes their commits to private repositories.<br/>
187
187
<supid="note-2">2</sup>: Joining an organization may need an approval depending on your setting for [accepting new people](managing-people.md#joining).<br/>
188
-
<supid="note-3">3</sup>: Depending on your setting for [configuring which users can ignore issues](configuring-which-users-can-ignore-issues.md).<br/>
189
-
<supid="note-4">4</sup>: Codacy can't distinguish the Bitbucket roles Read and Write because of a limitation on the Bitbucket API.
188
+
<supid="note-3">3</sup>: Codacy can't distinguish the Bitbucket roles Read and Write because of a limitation on the Bitbucket API.
190
189
191
190
See [managing people](managing-people.md) to list and manage the members of your organization.
191
+
192
+
## Configuring who can ignore issues {: id="configure-ignore-issues"}
193
+
194
+
!!! info "Applies only to GitHub Cloud and GitHub Enterprise"
195
+
196
+
By default, only users with Admin permission on a repository can [ignore issues](../repositories/issues-view.md#ignoring-an-issue), but you can change this. In your Organization's settings, you can find **Members privileges** where you can define the lowest permission required to ignore issues for your organization.
197
+
198
+

199
+
200
+
Codacy doesn't allow changing the role of a user, as the roles on Codacy are mirrored from your Git provider and applied to each repository.
Copy file name to clipboardExpand all lines: docs/repositories/issues-view.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -23,10 +23,15 @@ Each pattern has a pre-defined severity level and at the moment, it's not possib
23
23
24
24
## Ignoring an issue
25
25
26
-
For an issue you disagree with or false positives, you can either ignore that instance or disable the pattern across the whole repository. To do so, click on the cogwheel and select the desired option:
26
+
You can ignore issues that you disagree with, either because they're not relevant or because you won't tackle them in the immediate future.
27
+
28
+
To do so, click on the cogwheel and select the desired option:
27
29
28
30

29
31
32
+
!!! tip
33
+
Organization owners can [configure who is allowed to ignore issues](../organizations/roles-and-permissions-for-synced-organizations.md#configure-ignore-issues).
34
+
30
35
### Reinstating ignored issues
31
36
32
37
To reinstate ignored issues, click on the **Current Issues** box, and select **Ignored Issues** from the drop-down menu.
0 commit comments