This message was deleted.

In addition, it would be nice if Graphite would convert Graphite links to GitHub links in order to save me a couple clicks to get the autolinkable reference. In addition to that, it would be nice if Graphite would convert GitHub autolink references to Graphite autolink references when clicking on them. 😄

This works for me 🤔 We reference Jira tickets by writing

[PROJECTCODE-NUMBER]

in the PR description and GH auto links it to the Jira ticket. The same exact thing works on Graphite from what I have experienced. Unless I understand your request wrong

I believe Raimundo was talking about how GitHub converts GitHub links to a neat PR name and number

Oh, I see

Actually, I am referring to Dimitris point. I have an autolink reference set up in github that detects my linear issue numbers and make them clickable FOO-321. I see them clickable in github PR descriptions but not in Graphite PR description

I have something that links the PR to JIRA when I mention a ticket even without linking, I didn’t know you could also link in the other direction. Did you just link the apps, or was there other setup to enable that behavior?

This is what ive configure in Gh https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources#

Do you mind clarifying the issue here? ie what you are seeing and what you expect to see?

I have an autolink reference [in Github](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-featu[…]ettings/configuring-autolinks-to-reference-external-resources) set up, so if a PR description in Github contains the string “FSY-XXX”, github automatically transforms this into a clickable link that takes me to the URL i set up (in my case Linear)

@David Balatero can you take a look here?

there's a lot of different things in this thread i think, but it sounds like GitHub has a feature where: • in a pr description or comment • if you have the string

JIRA-123

• it will convert that to something like

[JIRA-123](<https://jira.example.com/issue?query=123>)

in order to support this, we would need to: 1. sync and ingest all autolink configurations foreach repo using these APIs 2. make a feature that renders the autolink configurations on our UI which would need to be prioritized and scoped

For the record, JiraBot parses

[<board>-<ticket_number>]

formatted issues. e.g.

[ABC-123]

, which it will turn into

[ABC-123](<https://jira.example.com/issue?query=123>)

. It will not parse

<board>-<ticket_number>

, e.g.

ABC-123

. The above is in fact working on the graphite pr page. I just wrote something like

[<board>-<ticket_number>]

and it took a few seconds but it got turned into a link. As far as I understand, Graphite doesn't do anything for this on its own. Graphite updates the github description, the jirabot on github changes the tag to a link, and that triggers an update back to Graphite's pr description.

that makes sense!