ManageIQ/miq_bot

move_issue needs to respect relative issue numbers

Open

#349 opened on Jun 27, 2017

View on GitHub
 (1 comment) (1 reaction) (0 assignees)Ruby (38 forks)auto 404
bughelp wantedpinned

Repository metrics

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

Description

When you move an issue, the original issue number text gets linked afterward and doesn't correspond to the previous reference. See here: https://github.com/ManageIQ/manageiq-ui-classic/issues/1616

That is, if you reference issue #1 on the core repo, when the issue is moved it now incorrectly references issue #1 for whatever repo it moved to, which is pretty confusing.

Contributor guide

Research direction
Investigate how the bot handles issue migration, specifically the logic that transforms relative issue numbers (#1) into cross repository references. Look at the code that processes moved issues and check for mapping or conversion steps.
Tech stack
ruby
Domain
toolingdevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60