bountysource / bountysource/core

Enable bugzilla queries to be bound to trackers (less magic, more control)

Open
#813 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
643
Forks
199
PR merge metrics
No merged PRs in 30d

Description

With various projects and bugzilla instances I have the issue that I would love to bind specific queries ?component=bounty&module=frontend to a tracker.
This would enable organizing queries into trackers and let trackers be organized into projects (later these could be organized into super-teams).

I can't get a reliable way to bind queries to a tracker. There is too much magic going on.

Not sure how to solve this, but perhaps make it configurable, which query is actually used or remove unlogical magic.
##

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/2681357-enable-bugzilla-queries-to-be-bound-to-trackers-less-magic-more-control?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

Open the contributing guide

Research direction

No implementation files or tests are named. Start by tracing how Bugzilla queries are currently associated with trackers, then inspect the tracker and project organization flow. Done means a documented, configurable way to bind a specific query to a tracker without relying on implicit 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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.