ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Add custom queries (Task #162)

Added by Enderson Maia at 2011-02-08 11:17 pm. Updated at 2011-02-22 05:39 pm.

Status:Closed Start date:2011-02-08
Priority:Normal Due date:
Assignee:Felix Schäfer % Done:

0%
Category:chiliproject.org Website
Target version:-
Remote issue URL:

Description

Add public custom queries to help contributors find better issues to help.

Suggestions:

  • Open bugs
  • Open features
  • Unassigned issues
  • Feature patches
  • Translations Patches
  • ...

History

#1
Updated by Felix Schäfer at 2011-02-09 04:28 pm

  • Open bugs
  • Open features
  • Unassigned issues

OK with me.

  • Feature patches
  • Translations Patches

That's something involved should do for himself.

What do the others think?

#2
Updated by Ivan Cenov at 2011-02-09 05:09 pm

May be templates for issues are the solution... These templates may be stored in their own table, be private, per user group, per project, per project hierarchy, global public.

Possible operations:
  1. Create template from selected issue
  2. Edit & delete template
  3. Copy template to another template
  4. Create issue from template

Templates may use defined variables. Then when one creates an issue, a dialog may appear where he/she may enter values of these variables.

Ivan

#3
Updated by Eric Davis at 2011-02-09 08:06 pm

Felix Schäfer wrote:

  • Feature patches

Since we are using git more than uploaded patches (and there isn't an "attachment" column in the Query) we could do this:

  1. Add a custom field for "branch location". This would point to a git url(s) where the code is stored at and should be updated when someone writes code for an issue.
  2. Use a custom query to look for non-empty "branch location" AND Tracker=Feature
  • Translations Patches

Just the Translation category maybe?

#4
Updated by Felix Schäfer at 2011-02-14 08:43 am

My question was more something like "do we really need global queries for feature patches/translation patches"? I feel those 2 should rather be queries the people that need them can do for themselves. So again: do we really need those 2?

Eric Davis wrote:

Felix Schäfer wrote:

  • Feature patches

Since we are using git more than uploaded patches (and there isn't an "attachment" column in the Query) we could do this:

  1. Add a custom field for "branch location". This would point to a git url(s) where the code is stored at and should be updated when someone writes code for an issue.

What about diffs attached or pasted in? I wouldn't want to lose contributors just because they don't have some internet-reachable repo or whatever.

  1. Use a custom query to look for non-empty "branch location" AND Tracker=Feature

We already have the "Ready for review" status, to which issues with patches attached/linked to should be set to, so that would make the search "status='ready for review' and tracker='feature'".

#5
Updated by Felix Schäfer at 2011-02-22 05:39 pm

I've created the following three:

  • Open Bugs
  • Open Feature Requests
  • Unassigned Issues

Re-open here if you think the other proposed ones are indispensable.

  • Assignee set to Felix Schäfer
  • Status changed from Open to Closed

Also available in: Atom PDF