The question involves managing versions in a company-managed project in Jira Software Cloud. Maia wants to move all issues from version 1.1 to version 1.2 and remove version 1.1 as an available option in theFix Versionsfield. The two operations that meet both requirements areArchiveandMerge.
* Explanation of the Correct Answers:
* Archive (Option B):
* Archiving a version removes it from theFix Versionsfield as an available option for new issues, while preserving the version's association with existing issues. Additionally, archiving allows you to move issues to another version (e.g., version 1.2) during the process, meeting both requirements.
* Exact Extract from Documentation:
Archive a version
Archiving a version removes it from the list of available versions in fields like Fix Versions, so it can't be selected for new issues. You can also move issues to another version during the archiving process.
To archive a version:
* Go to your project'sReleasespage.
* Find the version (e.g., version 1.1) and selectArchive.
* Optionally, choose to move issues to another version (e.g., version 1.2).Archived versions are still visible in reports and issue details but are no longer selectable in fields.Note: You need project admin permissions to archive versions.(Source:
Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Archiving version 1.1 removes it from the Fix Versions field, preventing it from being selected for new issues, and allows Maia to move all issues to version 1.2 during the archiving process, fulfilling both requirements.
* Merge (Option D):
* Merging a version moves all issues from one version (e.g., version 1.1) to another (e.g., version 1.2) and deletes the source version, effectively removing it from the Fix Versions field. This meets both requirements, as it reassigns issues and eliminates version 1.1 as an available option.
* Exact Extract from Documentation:
Merge versions
Merging versions allows you to combine two versions by moving all issues from one version to another. The source version is deleted after the merge.
To merge versions:
* Go to your project'sReleasespage.
* Find the version to merge (e.g., version 1.1) and selectMerge.
* Choose the target version (e.g., version 1.2) to move issues to.After merging, the source version (version 1.1) is removed from the Fix Versions field and is no longer available for selection.Note: Merging is permanent and cannot be undone, so ensure the target version is correct.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Why This Fits: Merging version 1.1 into version 1.2 moves all issues to version 1.2 and deletes version 1.1, ensuring it is no longer an option in the Fix Versions field, thus meeting both requirements.
* Why Other Options Are Incorrect:
* Delete (Option A):
* Deleting a version removes it from the Fix Versions field, but it also removes the version from all issues associated with it without reassigning them to another version. This does not meet the requirement to move issues to version 1.2.
* Extract from Documentation:
Delete a version
Deleting a version removes it from the project and clears it from the Fix Versions field of all associated issues. Issues are not reassigned to another version automatically.
Note: Use caution, as this action cannot be undone, and issues lose their version association.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Build and release (Option C):
* Building and releasing a version marks it as complete and moves unresolved issues to another version, but it does not remove the version from the Fix Versions field. Released versions remain selectable unless archived or deleted.
* Extract from Documentation:
Release a version
Releasing a version marks it as complete and optionally moves unresolved issues to another version. The released version remains available in the Fix Versions field unless archived.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Additional Notes:
* BothArchiveandMergeare suitable, but they have different implications:
* Archiving preserves version 1.1 in reports and issue histories, making it ideal if historical data needs to be retained.
* Merging permanently deletes version 1.1, which may be preferred if the version is no longer relevant.
* The operations require project admin permissions in a company-managed project, and the Releasespage is accessed viaProject Settings > Releases.
:
Atlassian Support Documentation:Manage versions in company-managed projects Atlassian Support Documentation:Configure releases and versions