You are using a bulk operation to move a few stories from a company-managed project...

When moving stories from a company-managed project to a team-managed project using a bulk operation, certain issue attributes are preserved, while others may change or be lost due to differences in project configurations. The definite outcome is thattheir comments will remain the same(Option A), as comments are retained during issue moves.

Explanation of the Correct Answer (Option A):

Commentsare part of an issue’s data and are preserved when moving issues between projects, whether from a company-managed to a team-managed project or vice versa. The bulk move operation retains all comments attached to the stories, ensuring they remain visible in the target team-managed project.

Exact Extract from Documentation:

Move issues in Jira Cloud

When moving issues between projects:

Comments: All comments are retained, including their content, author, and timestamps.To move issues:

Select issues and chooseBulk change>Move issues.

Choose the target project and issue type.

Map fields and statuses as needed.Note: Comments are preserved regardless of the source or target project type (company-managed or team-managed).(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Why This Fits: The bulk move operation ensures that comments are transferred with the stories, makingtheir comments will remain the samea definite outcome.

Why Other Options Are Incorrect:

Their keys will remain the same (Option B):

Issuekeys(e.g., PROJ-123) are project-specific, consisting of the project key and an issue number. When moving issues to a different project (from a company-managed to a team-managed project), the issues are assigned new keys based on the target project’s key (e.g., NEWPROJ-456). The original keys do not remain the same.

Extract from Documentation:

When moving issues to a different project, the issue keys change to reflect the target project’s key. The original key is preserved in the issue history as a reference.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Their issue links will be lost (Option C):

Issue links(e.g., “blocks,” “is related to”) are generally preserved during a move, provided the linked issues remain accessible in the target project and the link types are supported. While there could be rare cases where links to restricted issues are affected, it is not a definite outcome that links will be lost.

Extract from Documentation:

Issue links are retained during a move unless the linked issues are inaccessible in the target project due to permissions or restrictions.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Their issue history will be lost (Option D):

Theissue history(e.g., status changes, field updates) is preserved during a move. The history is transferred to the target project, maintaining a record of all changes, including those from the source project.

Extract from Documentation:

The issue history, including all changes and updates, is retained when moving issues between projects.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Additional Notes:

Steps for the bulk move:

Run a filter to select the stories inIssues > Search for issues.

ChooseBulk change > Move issues.

Select the team-managed project and map statuses or fields as needed.

The operation requires theMove Issuespermission in the source project andCreate Issuespermission in the target project.

Other attributes (e.g.,status,custom fields) may need mapping due to differences between company-managed and team-managed projects, but comments are always preserved.