Since JIRA can be extensively customized based on the way different organizations use the software, there may be instances where it doesn't make sense to display the Root Cause Analysis plugin features on a issue view.
For example, an organization may only be interested in tracking the Root Cause Issues from the JIRA Issue Type labeled Bug. Alternatively, another organization may be interested in having Root Cause Analysis performed on all JIRA Issue Types except for one custom Issue Type Leads created to keep track of sales leads.
The Root Cause Analysis plugin provides the ability to explicitly define which JIRA Issue Types you can attribute Root Cause Issues from.
