ManageIQ/miq_bot

move_issue command should also move any existing comments

Open

#504 opened on May 14, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Ruby (38 forks)auto 404
enhancementhelp wanted

Repository metrics

Stars
 (16 stars)
PR merge metrics
 (PR metrics pending)

Description

If some conversation took place in the original issue before it was discovered that it needed to be moved, those comments would be stuck in the old issue. It would be better to have all the context in the same place. This would also presumably carry over mentions and add mentions to people who might have commented, but were not the reporter.

Here is an issue where I had to manually copy over content from a comment I made to the new issue after a move: https://github.com/ManageIQ/manageiq/issues/20172

Contributor guide

Research direction
Examine the current implementation of the move issue command to understand how it transfers an issue. Identify where comments are not being transferred and add logic to move all comments from the old issue to the new one.
Tech stack
ruby
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Ruby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65