A company-managed project uses a single workflow for two issue types: Blogs and Ideas.

In a company-managed project, a single workflow can be shared across multiple issue types (e.g., Blogs and Ideas) via aworkflow schemethat maps workflows to issue types. To satisfy a requirement that necessitates a second workflow, the requirement must involve workflow-specific differences that cannot be handled within a single workflow. The requirement thatBlogs should allow reopening after they are closed, but not Ideas(Option D) requires a second workflow, as reopening involves a transition that must be present for Blogs but absent for Ideas.

Explanation of the Correct Answer (Option D):

The requirement to allowBlogsto be reopened after being closed, but notIdeas, means the workflow for Blogs must include a transition from theClosedstatus to an open status (e.g.,OpenorReopened), while the workflow for Ideas must not include this transition. In a single workflow, transitions apply to all issue types using that workflow, so it is impossible to have a transition for Blogs but not Ideas. Therefore, a second workflow is needed: one for Blogs (with a reopen transition) and one for Ideas (without a reopen transition). These workflows can be assigned to the respective issue types via the project’sworkflow scheme.

Exact Extract from Documentation:

Configure workflows in company-managed projects

Workflows define statuses and transitions for issues. A workflow scheme maps workflows to issue types in a project.

To use different workflows for different issue types:

Create separate workflows (e.g., one for Blogs with a reopen transition, one for Ideas without).

Go toSettings > Issues > Workflow schemes.

Edit the project’s workflow scheme to assign the appropriate workflow to each issue type (e.g., Blogs to Workflow A, Ideas to Workflow B).Note: A single workflow applies the same transitions to all issue types it governs. To have different transitions (e.g., reopening for Blogs but not Ideas), use separate workflows.(Source: Atlassian Support Documentation, "Configure workflow schemes")

Why This Fits: The need for a reopen transition for Blogs but not Ideas requires distinct workflows, as a single workflow cannot differentiate transitions by issue type, making Option D the correct answer.

Why Other Options Are Incorrect:

Blogs should be auto-closed after 3 days, but not Ideas (Option A):

Auto-closing issues after 3 days can be achieved using aJira automation rule(e.g., a scheduled rule that transitions Blogs toClosedbased on a time condition). This does not require a workflow change, as the transition toClosedcan exist in a shared workflow, and the automation rule can filter by issue type (Blogs).

Extract from Documentation:

Use Jira automation to transition issues based on time conditions (e.g., close Blogs after 3 days). Filter by issue type to exclude Ideas. This does not require separate workflows.

(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")

Blogs should be editable after they are closed, but not Ideas (Option B):

Editability after closing is controlled by theEdit Issuespermission and workflow properties (e.g., jira.issue.editable). A workflow property can be set on theClosedstatus to allow editing for Blogs but not Ideas, or a separatefield configuration schemecan make fields read-only for Ideas. This can be managed without a second workflow.

Extract from Documentation:

Use workflow properties (e.g., jira.issue.editable=true) or field configuration schemes to control editability by issue type. Separate workflows are not required.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Blogs should be sent to the project lead each Friday, but not Ideas (Option C):

Sending issues to the project lead each Friday can be handled with aJira automation rule(e.g., a scheduled rule that sends an email or creates a task for Blogs). This is independent of the workflow, as it involves notifications or actions, not status transitions.

Extract from Documentation:

Use Jira automation to send notifications or tasks for specific issue types (e.g., Blogs) on a schedule (e.g., every Friday). This does not require workflow changes.

(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")

Additional Notes:

Creating a second workflow requiresJira administratorprivileges to modify workflows (Settings > Issues > Workflows) and update the workflow scheme (Project settings > Workflows).

The workflow scheme can assign different workflows to Blogs and Ideas, ensuring the reopen transition is only available for Blogs.

Options A, B, and C can be addressed with automation or other configurations, but Option D fundamentally requires distinct workflows due to the transition difference.