Stream: JIRA/Confluence
Topic: Redirects
Grahame Grieve (Nov 18 2019 at 07:53):
@Lloyd McKenzie can you please explain what lies behind this:
Redirects in the core spec and in chat.fhir.org have already been changed to the new platform, though IGs that were published using older templates may still end up directing to gForge.
Lloyd McKenzie (Nov 18 2019 at 10:11):
Tracker permalink has changed to point at Jira instead of gForge
Grahame Grieve (Nov 18 2019 at 10:50):
so that's for non-tasks. But existing task specific references, they're not redirected, right?
Lloyd McKenzie (Nov 18 2019 at 10:54):
Correct - though I'm not aware of any task-specific references in the core spec. Any references that spell out the full gForge URL won't auto-redirect.
Lloyd McKenzie (Nov 18 2019 at 10:54):
They'll take you to gForge, but it'll be read-only
Grahame Grieve (Nov 18 2019 at 10:55):
there's quite a few... can I do search and replace on them?
Lloyd McKenzie (Nov 18 2019 at 11:00):
Yes, I suppose. I'm sorry, I didn't realize we had such links in the spec or we could have strategized before R4 went out.
Grahame Grieve (Nov 18 2019 at 11:04):
so search
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=
And replace with
http://jira.hl7.org/browse/fhir-
Lloyd McKenzie (Nov 18 2019 at 11:05):
Probably also search for http:// as the https is new-ish
Grahame Grieve (Nov 18 2019 at 11:06):
y
Grahame Grieve (Nov 18 2019 at 12:31):
an old discussion... can we now prepopulate the standards context in the link to 'propose a change'? If so, how would we go about that?
Lloyd McKenzie (Nov 18 2019 at 13:27):
In theory, yes. However, I need to do some digging to figure out how best to make it happen. It's on my list :)
Grahame Grieve (Nov 18 2019 at 15:50):
ok. thanks. 194k published links to gForge.hl7.org in hl7.org/fhir
Lloyd McKenzie (Nov 18 2019 at 15:57):
Good lord. Why?
Grahame Grieve (Nov 18 2019 at 15:58):
every page has at least one
Lloyd McKenzie (Nov 18 2019 at 16:13):
Why? The link at the bottom for R4 and the CI build (and possibly other releases) isn't to gForge (or Jira). It's to a permalink.
Grahame Grieve (Nov 18 2019 at 17:22):
I don't know why. I just searched...
Grahame Grieve (Nov 21 2019 at 10:06):
I see someone already fixed the GF# short cut to link to Jira not gForge
Grahame Grieve (Nov 21 2019 at 10:06):
I'm going to add J#[number] as another shortcut for people not steeped in gForge history, but it will work the same
Grahame Grieve (Nov 21 2019 at 10:09):
test: J#22551
Josh Mandel (Nov 21 2019 at 10:15):
Do we want the ability to link to non-fhir projects in jira? Just thinking ahead a bit..
Grahame Grieve (Nov 21 2019 at 10:23):
I thought about that. that would be, for instance. JCDA#12345
Lloyd McKenzie (Nov 21 2019 at 14:48):
When that happens, we could add JFHIR# too, though given the theme of the site, J# defaulting to FHIR is still appropriate.
Michael Donnelly (Feb 03 2020 at 00:04):
Have we looked into having a redirect rule on the gForge server itself? I've hit a couple of links in chat.fhir.org this weekend that go to gForge and die.
Lloyd McKenzie (Feb 03 2020 at 00:11):
The problem is that gForge is still there and running and in use for at least a few other purposes. We can't put something that will respond at those URLs when Jira is already there.
Lloyd McKenzie (Feb 03 2020 at 00:12):
Once everything is off gForge and we're confortable shutting it down, then we could theoretically stand up redirects, though by that point, we may decide there's no point
Lloyd McKenzie (Feb 03 2020 at 00:12):
To find an issue with a given id in Jira, it's http://jira.hl7.org/browse/FHIR-[yourid]
Last updated: Apr 12 2022 at 19:14 UTC
