atlassian / atlassian/github-for-jira
Github for Atlassian marked as LEGACY – what's the support or replacement timeline?!?!
- Dominant language
- No language data
- Stars
- 655
- Forks
- 194
- PR merge metrics
- No merged PRs in 30d
Description
> This app may stop working after December 2026, as it's running on a platform that will be unsupported from that date. Read [Connect End of Support: What it means for Marketplace apps](https://www.atlassian.com/blog/developer/connect-end-of-support-what-it-means-for-custom-apps-and-how-to-migrate-to-forge) for more details about this change.
>
> For migration plans or other available options, [contact the vendor directly](https://marketplace.atlassian.com/apps/1219592?tab=support).
Given it's an Atlassian product it's pretty poor product management. I get integration with Github isn't magic AI sprinkles, but it's quite a core integration (hence it's an in-house solution).
Can we get some idea what's going on here?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue asks for a support or replacement timeline rather than naming a code change, file, test, or entry point. Read the linked Atlassian Connect end-of-support notice and Marketplace support page first; done would require a maintainer-confirmed migration plan or timeline, not a repository edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100