I'm looking for a part-time remote job.

Hire me

I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).

Follow me:

Feature #2018

database query cutsom field type

Added by Terence Miller over 12 years ago. Updated over 10 years ago.

Status:
Open
Priority:
Normal
Assignee:
Andriy Lesyuk
Category:
-
Target version:
-
Start date:
05 Apr 2012
Due date:
% Done:

0%

External issue:

Description

Would be great to be able to configure an sql query that is used to popolate and new cutsom list field type

History

#1 Updated by Andriy Lesyuk over 12 years ago

  • Status changed from New to Open
  • Assignee set to Andriy Lesyuk

You have many interesting ideas, Terence! Thanks for sharing them!

#2 Updated by Terence Miller over 12 years ago

The idea is that one custom field specify filter parameters for an sql query, where result of the query will fill some issue attributes. User then can decide if he changes that filled fields by return values manually or just takes’em.

#3 Updated by Fred Leeflang almost 12 years ago

Maybe it would be a good idea to fill an extended field with values obtained from a REST request. MySQL servers are not always easily reachable, HTTP servers much more often.

#4 Updated by Andriy Lesyuk over 10 years ago

As I get it for now:

  1. We have the custom field type, e.g., “SQL List”.
  2. We specify the query like: SELECT id, title FROM news WHERE project_id = @project.
    Where id is taken as select option id and title is taken as select option value.
  3. Redmine renders the custom field using data, returned by the query.
  4. Administrators are forced to use custom field view template to render the value.

Please specify the similar detailed workflows for your cases.

Also available in: Atom PDF

Terms of use | Privacy policy