When releasing a version in a company-managed project that contains unresolved issues, you can choose to ignore these issues and proceed with the release. The unresolved issuesare left unresolved(Option C), meaning they retain their current status and resolution state without being automatically moved or transitioned.

Explanation of the Correct Answer (Option C):

In Jira, releasing a version marks it as complete and updates theRelease DateandReleasedstatus for the version. If unresolved issues (issues without a resolution, e.g., not in a Done status) are included, you can choose to ignore them during the release process. Ignoring unresolved issues means they remain in their current state—unresolved, with no changes to their status, resolution, or version association. They are not automatically moved to another version, transitioned, or reordered in the backlog.

Exact Extract from Documentation:

Release a version in company-managed projects

When releasing a version:

You can choose to ignore unresolved issues (issues without a resolution).

Ignored unresolved issues: Remain in their current status and resolution state, with no automatic changes.To release:

Go toProject settings > Releases.

Select the version and clickRelease.

Choose to ignore unresolved issues if prompted.Note: Unresolved issues are not moved to another version or transitioned unless explicitly configured.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

Why This Fits: Ignoring unresolved issues during a version release leaves them unchanged in their current unresolved state, making Option C the correct answer.

Why Other Options Are Incorrect:

They are moved to the next version (Option A):

Moving unresolved issues to the next version is an option during the release process, but it is not the default or required action when choosing toignoreunresolved issues. Ignoring them explicitly avoids moving them to another version.

Extract from Documentation:

When releasing, you can move unresolved issues to another version or leave them unchanged. Ignoring unresolved issues keeps them in their current version.

(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

They are transitioned to Done (Option B):

Transitioning issues toDone(or setting a resolution) requires a workflow transition and is not automatic when releasing a version. Ignoring unresolved issues means no status or resolution changes occur.

Extract from Documentation:

Releasing a version does not transition issues or set resolutions unless explicitly configured via a workflow post function.

(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

They are moved to the top of the backlog (Option D):

Releasing a version does not affect the backlog order or automatically reorder issues. The backlog is managed separately, and ignoring unresolved issues leaves them in their current position.

Extract from Documentation:

Releasing a version does not modify the backlog order. Unresolved issues remain in their current position unless manually reordered.

(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")

Additional Notes:

Releasing a version requiresproject adminprivileges and is done inProject settings > Releases.

If you choose to move unresolved issues to another version instead of ignoring them, Option A would apply, but the question specifiesignoringthe issues.

Unresolved issues may still be associated with the released version unless manually updated.