FHIR Chat · Reference Jira ticket from Zulip · JIRA/Confluence

Stream: JIRA/Confluence

Topic: Reference Jira ticket from Zulip


view this post on Zulip Alexander Henket (Dec 04 2019 at 16:48):

I see the GF#... are still routed to gForge rather than Jira, and I could not find how to reference a Jira ticket with a similar macro.

Would it be possible change the GF#... to point to Jira, so historic pointers lead somewhere?
Does it make sense to keep GF#... as pointer for Jira or does HL7#... make more sense for future reference? (better not put the tool name in there, I think)

@Arianne van de Wetering

view this post on Zulip Lloyd McKenzie (Dec 04 2019 at 16:49):

GF# should be routing to Jira now. J# will also route to Jira

view this post on Zulip Lloyd McKenzie (Dec 04 2019 at 16:50):

Testing: GF#12773 J#12773

view this post on Zulip Lloyd McKenzie (Dec 04 2019 at 16:50):

Looks like it's working to me...

view this post on Zulip Arianne van de Wetering (Dec 04 2019 at 17:15):

Looks like it's working to me...

I just noticed that zulip stuff in stream:committers topic:tracker-item still routes to gForge.

https://chat.fhir.org/#narrow/stream/179165-committers/topic/tracker-item/near/153852302

view this post on Zulip Yunwei Wang (Dec 04 2019 at 17:17):

Related question: How do I reference JIRA ticket in Confluence page? I know using "Insert - JIRA Issue" to do that. Is there a quick way like using J# directly in Confluence?

view this post on Zulip Lloyd McKenzie (Dec 04 2019 at 18:00):

@Arianne van de Wetering It looks like the shortcut creates a hyperlink at the time the chat comment is recorded. So all hyperlinks created prior to the migration will point to gForge. All those created after will point to Jira. We don't have a way of going back and redirecting all of the old hyperlinks.


Last updated: Apr 12 2022 at 19:14 UTC