bountysource / bountysource/core
Support for issue tracker URL changes
- Dominant language
- Ruby
- Stars
- 643
- Forks
- 199
- PR merge metrics
- No merged PRs in 30d
Description
If a issue tracker changes its URL, all bounties will be left behind now. Support for issue tracker URL changes must be needed.
##
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/14560537-support-for-issue-tracker-url-changes?utm_campaign=plugin&utm_content=tracker%2F47&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47&utm_medium=issues&utm_source=github).
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by tracing how issue trackers and bounties are stored and associated, then determine how a changed tracker URL could be detected or migrated. Done means existing bounties remain attached after a tracker URL changes, with coverage for the supported migration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100