Markus,
I agree that preserving the issue reporter and watchers would have been a
good thing. However, having worked with the GitHub issue import API myself
for the migration of the JSR 371 issues, I can confirm that the API doesn't
support setting the issue creator. So basically the issue creator is
automatically set to the GitHub user account running the import. Same
applies to the authors of issue comments. Of course this is not optimal for
the migration, but it seems to be a restriction of the GitHub API.
Christian
2017-04-25 20:07 GMT+02:00 Markus KARG <markus_at_headcrashing.eu>:
> I really appreciate the move to Github away from java.net and JIRA.
>
> Bit it would have been nice if the glassfishrobot would have looked up
> existing user accounts in github instead of automatically setting itself as
> the reporter: Now everybody has to check manually the issues to find out
> about changes, as auto-notification will not work anymore.
>
> -Markus
>
> -----Original Message-----
> From: Pavel Bucek [mailto:pavel.bucek_at_oracle.com]
> Sent: Dienstag, 25. April 2017 14:03
> To: jsr370-experts_at_jax-rs-spec.java.net
> Subject: Issue tracker migration - https://github.com/jax-rs/api/issues
>
> Dear experts,
>
> issue tracker provided by java.net was is shutting down. All existing
> issues were migrated to Github: https://github.com/jax-rs/api/issues -
> please don't use java.net JIRA any more, if you'd like to file an issue,
> please do it on Github.
>
> Thanks and regards,
> Pavel
>
>
--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal