@jamedjo also pointed out (thanks) that the markdown table on that issue also changed during the move with the the first row missing some columns and one of the link descriptions changing from [pdf] to the title of the file.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Hi! I'm new to the project but I've got a few OS commits under my belt with other projects. I'd love to take a shot at this issue if it's still open? Cheers!
Thanks @richiethomas. Please go ahead with this issue and you can open a merge request when you are ready and you can ping me there and I can help get it to the right folks to review.
I’ll assign this issue to yourself now so people know.
Thanks for working on this @richiethomas! We've removed the ~"Accepting merge requests" label to avoid having multiple people working on the same issue.
@richiethomas great! I expect that the issue here is that when we move the issue, we don't copy the values from the system_notes_metadata table, which are used to provide the icons.
Cool, thanks for the guidance. Any timetable for this issue that I should be aware of? I'm thinking a few weeks here, since I'm unfamiliar with the codebase and it's a busy holiday season for me.
Here's an update from my end- when I perform some actions on an issue and then move it to another project, I'm able to see the system notes icons from the previous project:
Still investigating and will update when I know more, but so far I'm unable to reproduce the issue on my local.
Hey y'all, FYI I haven't had much bandwidth to work on this issue lately. Not sure when I'll be able to pick it up in the near future, so I'm happy to un-assign myself if that's best. I look forward to contributing to GitLab at some point in the future.
Something I noticed while testing this is that moving an issue shows the banner "Something went wrong" But it seems that nothing did go wrong because you are quickly redirected to the issue in its new location.
@Qwertie@jprovaznik should we close this issue, then? Or maybe it happens when an issue is moved across groups, not just between two projects in the same group?