đŸ”„Let’s Do DevOps: Creating 60k GitHub Auto-Link References to Jira

Kyler Middleton
2 min readApr 10, 2023

This blog series focuses on presenting complex DevOps projects as simple and approachable via plain language and lots of pictures. You can do it!

Hey all!

GitHub is a fantastic place for code, but probably isn’t where you’re managing your ticket queue, right? You could use GitHub Issues to keep track of specific issues with a code-base, but your project manager isn’t going to be happy with that — they’d much rather see an aggregate queue of work on all the different team boards in something like Atlassian’s Jira ticketing system.

So all the work comes from Jira, and is implemented in GitHub. Those ticket numbers are all over your code commits, your PR comments, and your git history.

And GitHub has a tremendously useful feature that helps you find your way back to Jira — it’s called an auto-link reference, and it means once configured on a repo, any string in any context (commit message, comment, PR message, etc.) will become a hyperlink and link back to your ticketing system! That could save a heck of a lot of time.

Unfortunately it doesn’t live within an Org configuration — it lives at the Repo level. I have 42 ticket projects to watch for, and I have 1,426 repositories to configure.

That means I need


--

--

Kyler Middleton
Kyler Middleton

Written by Kyler Middleton

DevNetSecOps, DevRel, cloud security chick. I will teach you, it’s unavoidable. She/Her đŸłïžâ€đŸŒˆđŸłïžâ€đŸŒˆ, INFJ-A, support the EFF!

Responses (1)