Not A Bug Reason
From this page, you can create and manage reasons used when a reported issue is marked as "Not a Bug." These reasons help QA and development teams document why a particular issue does not qualify as a bug, and can be configured separately for QA and developer contexts.
For example, a QA has added a bug in a task. Now if it's working correctly, then the developer can "not a bug" that task.
Reason:
Enter the reason that will be available for selection when an issue is marked as not a bug — for example, Coding Issues or Cache Issue.
For QA Reason:
Enable this toggle to make the reason available for selection by the QA team.
For Developer Reason:
Enable this toggle to make the reason available for selection by the development team.
With the Bulk Action feature, you can delete multiple not a bug reasons at once, streamlining the management process.