Scala-dev: JIRA not redirecting to new bug tracker?

[SethTisue]

e.g. at https://github.com/scalatest/scalatest/pull/1044 I clicked on the link to SI-8110 but I didn't land on scala/bug#8110, I landed on JIRA with a thud

I know we intended to do the redirect, not sure if it just hasn't happened yet, or we thought it happened but it isn't working

[adriaanm]

I haven't had a chance to ask Fabien about this.

[SethTisue]

For now, I at least updated the front matter at https://issues.scala-lang.org/secure/Dashboard.jspa to be more informative about the migration. (It had still said scala-dev and didn't say how to find migrated tickets.)

I want to also change the "Please use our new official issue tracker. This JIRA instance will be preserved as an archive only." to link to just scala/bug instead of scala/bug/issues, in the hopes that people will read the README before reporting an issue. But I can't find the setting. Do you remember where it is?

[adriaanm]

Done via https://issues.scala-lang.org/secure/admin/EditAnnouncementBanner!default.jspa

[ashawley]

I'm glad a redirect isn't enabled, yet. I wanted to see if any of my watched tickets in Jira were worth subscribing to on Github. Maybe add a note to a the dashboard that watched issues weren't exported? Get them before it's too late. Though maybe not a lot of people used it?

[adriaanm]

Not to worry! The original JIRA will remain available for the foreseeable
future as an archive
On Fri, Apr 21, 2017 at 17:49 Aaron S. Hawley [e-mail]
wrote:

I'm glad a redirect isn't enabled, yet. I wanted to see if any of my
watched tickets in Jira were worth subscribing to on Github. Maybe add a
note to a the dashboard that watched issues weren't exported? Get them
before it's too late. Though maybe not a lot of people used it?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scala/scala-dev/issues/372#issuecomment-296322780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFjy2QW1bKGxa_d3vbsJDmOnjonO3woks5ryTKNgaJpZM4M-G4c
.

[adriaanm]

(Even with the redirect in place there will be a way to not get redirected )
On Fri, Apr 21, 2017 at 18:04 Adriaan Moors [e-mail] wrote:

Not to worry! The original JIRA will remain available for the foreseeable
future as an archive
On Fri, Apr 21, 2017 at 17:49 Aaron S. Hawley [e-mail]
wrote:

I'm glad a redirect isn't enabled, yet. I wanted to see if any of my
watched tickets in Jira were worth subscribing to on Github. Maybe add a
note to a the dashboard that watched issues weren't exported? Get them
before it's too late. Though maybe not a lot of people used it?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/scala/scala-dev/issues/372#issuecomment-296322780,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFjy2QW1bKGxa_d3vbsJDmOnjonO3woks5ryTKNgaJpZM4M-G4c
.

[som-snytt]

Yet JIRA is a master of misdirection. That why it seems to work like magic.

To echo @ashawley I miss my list of "issues that interest me". I didn't like that JIRA subscribed me every time I chimed in with a stupid pun, but it was helpful to have a list of things I forgot I even cared about.

[retronym]

Searching for "is:issue user:scala involves:som-snytt" in the issues dashboard appears at least to find the puns. I don't believe that just subscribing or reacting to an issue is considered to be "involved" though.

[SethTisue]

@fsalvi is this something you might be interested in tackling? I still see people linking to the old JIRA tickets, and they still show up in Google searches.

and/or, how about removing the old JIRA from search engines, so people's searches take them to scala/bug instead? that's an easy-ish change, I think?

[fsalvi]

Yes, it looks reasonable to me.
I modified robots.txt to exclude the website from search engines.

[SethTisue]

awesome, thanks Fabien!

what about having the JIRA tickets redirect (automatically, or just by providing a link) to the corresponding scala/bug ticket...? is that too ambitious?

[SethTisue]

also, note to self: at the moment a Google Search such as
https://www.google.com/search?client=safari&rls=en&q=SI-907&ie=UTF-8&oe=UTF-8 still finds a JIRA ticket. it's probably just that Google hasn't noticed the robots.txt change yet, but we should check on it again in a month or so

[fsalvi]

Yes, I saw that.

Reading the google help, I found that:

If I block Google from crawling a page using a robots.txt disallow directive, will it disappear from search results?

Blocking Google from crawling a page is likely to decrease that page's ranking or cause it to drop out altogether over time. It may also reduce the amount of detail provided to users in the text below the search result. This is because without the page's content, the search engine has much less information to work with.

However, robots.txt Disallow does not guarantee that a page will not appear in results: Google may still decide, based on external information such as incoming links, that it is relevant. If you wish to explicitly block a page from being indexed, you should instead use the noindex robots meta tag or X-Robots-Tag HTTP header. In this case, you should not disallow the page in robots.txt, because the page must be crawled in order for the tag to be seen and obeyed.

And there's a link to the old issues page on every imported issue on github:
https://github.com/scala/bug/issues/907

I will try to find a better solution.
But, if everything is inside github, is it still useful to keep the old issues website ?

[adriaanm]

I don't think we need to keep the JIRA instance running anymore. For me, the ideal solution would be to redirect https://issues.scala-lang.org/browse/SI-(.*) to https://github.com/scala/bug/issues/(\1) and disable JIRA. Maybe we can archive the installation easily, just in case.

[fsalvi]

Ok, I added a redirect to the github issues. It's fine now.

[SethTisue]

sweeeeeeeeet, thanks Fabien!