ManageIQ
Moved issues should bring along as many labels as possible
When I move an issue, there are no labels set in the destination. It would be nice if the bot could bring over the labels as well, or at least as many as it can. For example, I moved an issue from manageiq to manageiq-ui-classic with the labels ui and enhancement. I would like for enhancement to come over, but since the ui label doesn't exist in ui-classic, it would be ignored.
@Fryguy it looks like the problem of moving an issue with a label that doesn't exist at destination is causing problems,..or at least errors. I saw this last week and pinged @bdunne on it, and then found this enhancement request.
Here's an example of the error: Source issue with labels: api and providers https://github.com/ManageIQ/manageiq/issues/13454
Destination repo where api and providers as labels don't exist: https://github.com/ManageIQ/manageiq-api/issues/26
Now here's the strange thing,..it doesn't appear that the errors occurred when the issue was moved on Aug 20, 2017,..but they showed up 2 days ago after I added a comment, and then again, after Beni made another comment.
https://github.com/ManageIQ/manageiq-api/issues/26#issuecomment-458545749 https://github.com/ManageIQ/manageiq-api/issues/26#issuecomment-458545759
Here's another example: https://github.com/ManageIQ/manageiq-ui-classic/issues/2155
Oh that's funky...it's like an infinite loop because there were @miq-bot commands in the initial issue comment to which it responds to itself, but the response is an error to itself, and that triggers another response to itself.
@JPrause The sudden late reply is a known issue that we can't figure out... See related #335 #342
Thanks @Fryguy Yes, I saw those PRs as well. Crazy, perhaps miq_bot is the "singularity" we've all been fearing? It's self-aware and messing with us.
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation.
I looked into this a bit Friday, and there doesn't seem to be a documented API for it. Might have also been something that came from community feedback?
https://github.community/t/feature-request-ability-to-move-github-issue-to-a-different-repository-within-the-same-organization/1440
TIL: .community is a TLD.
