What is gajira?

Atlassian's gajira project connects GitHub and Jira so that activity in your code repository automatically updates your issue tracker. It lets your development workflow handle task management in the background without requiring manual updates. The project provides a set of GitHub Actions, essentially automated tasks you can plug into your GitHub repository, that communicate with Jira's system. You set up a workflow in GitHub, and these actions handle the connection. For example, when you merge a pull request with a Jira issue key in its name, the action finds that key and marks the corresponding Jira issue as done. It can also create new Jira issues whenever someone opens a GitHub issue, add comments to Jira tasks when commit messages mention specific keys, or turn // TODO: comments in your code into Jira issues. It works by first logging into your Jira account, then searching for references to issues across your commits or branch names, and finally updating the matching task in Jira. This would be useful for development teams that use Jira to track work but find it tedious to manually keep Jira in sync with what's happening in GitHub. If a project manager wants Jira tickets to close automatically when developers merge code, or a team lead wants every TODO comment in the codebase to become a tracked task, this automates that bridge. One important caveat: the repository is no longer maintained and all of its actions have been deprecated. This means that while the code is still available to look at or learn from, relying on it for a production workflow would carry risk since it won't receive updates or fixes.