In a company-managed project, adding a second issue type can often be accommodated within the same project by configuring issue type-specific settings (e.g., fields, layouts). However, if the second issue type requires adifferent workflow, a separate project may be necessary unless the project'sworkflow schemeis modified to support multiple workflows. Since the question implies a configuration thatrequiresa separate project,different workflows per issue type(Option E) is the most likely to necessitate this, as it involves complex workflow management that is often easier to handle in separate projects.
* Explanation of the Correct Answer (Option E):
* In a company-managed project, aworkflow schememaps workflows to issue types. It is possible to assign different workflows to different issue types within the same project by configuring the workflow scheme. However, managing multiple workflows within a single project can become complex, especially if the workflows have significantly different statuses, transitions, or rules.
Creating a separate project for the second issue type simplifies workflow management by isolating the workflows, as each project can have its own workflow scheme. The question's phrasing suggests a scenario where a separate project is required, likely due to the complexity or isolation needed for distinct workflows.
* Exact Extract from Documentation:
Configure workflow schemes
A workflow scheme maps workflows to issue types in a company-managed project.
To use different workflows:
* Go toSettings > Issues > Workflow schemes.
* Create or edit a scheme and assign different workflows to issue types (e.g., one for Issue Type A, another for Issue Type B).
* Apply the scheme to the project inProject settings > Workflows.Note: For complex or conflicting workflows, separate projects may be preferred to simplify management and avoid configuration conflicts.(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Why This Fits: While different workflows can technically be managed within one project via a workflow scheme, the complexity or need for isolation (e.g., different teams, permissions, or configurations) often necessitates a separate project for the second issue type's workflow, making Option E the correct answer.
* Why Other Options Are Incorrect:
* Different custom fields per issue type (Option A):
* Different custom fields can be configured for eachCustom field contextsorscreen schemes allow different fields to be shown or hidden for specific issue types within the same project. A separate project is not required.
* Extract from Documentation:
Custom field contexts or screen schemes can restrict fields to specific issue types within a single project.
Separate projects are not needed.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Different card colors per issue type (Option B):
* Card colors on boards (e.g., Kanban, Scrum) are configured per issue type usingboard settings(e.g., based on issue type or priority). This is managed within a single project and does not require a separate project.
* Extract from Documentation:
Card colors are configured inBoard settings > Card colorsand can vary by issue type within the same project.
(Source: Atlassian Support Documentation, "Configure boards in Jira Cloud")
* Different components per issue type (Option C):
* Componentsare project-specific, not issue type-specific. While components can be assigned to issues, they are not tied to issue types, and different components can be used within the same project without needing a separate project.
* Extract from Documentation:
Components are project-specific and can be assigned to any issue type within the same project.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Different issue layouts per issue type (Option D):
* Issue layoutscan be configured per issue type within a single project inProject settings > Issue layout. Different layouts for each issue type do not require a separate project.
* Extract from Documentation:
Issue layouts can be customized for each issue type inProject settings > Issue layoutwithin the same project.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Additional Notes:
* Steps to configure different workflows:
* Create a new workflow for the second issue type inSettings > Issues > Workflows.
* Update the project's workflow scheme inProject settings > Workflowsto map the new workflow to the second issue type.
* Alternatively, create a new project with its own workflow scheme for simplicity.
* Configuring workflows and schemes requiresJira administratorprivileges.
* A separate project may be preferred for organizational reasons (e.g., different teams, permissions), but technically, a single project can handle different workflows. The question's emphasis onrequiringa separate project points to workflows due to their complexity.
:
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure boards in Jira Cloud
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Configure issue layouts in Jira Cloud