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 #1876

Custom fields

Added by Daniel Seifert over 12 years ago. Updated over 12 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
Andriy Lesyuk
Start date:
20 Oct 2011
Due date:
% Done:

100%

External issue:

Description

The list of provided profile fields is not ideal for everybody (e.g. in my setup half of the fields are never filled out and I miss other fields like phone number(s), Skype and other IM accounts, etc.). It would be better to have fewer fields pre-defined and instead allow the administrator to define custom fields.

History

#1 Updated by Andriy Lesyuk over 12 years ago

  • Status changed from New to Incomplete

Actually this was what I thought about too... But - here is the table of fields:

Field Reason to include
Company Displayed as <a href="[Company website]">[Company]</a> what can’t be achieved otherwise.
Company website Displayed as <a href="[Company website]">[Company]</a> what can’t be achieved otherwise.
Position
Project of interest Can’t be added otherwise.
Personal website Rendered as a link. Has hint “http://”.
Blog Rendered as a link. Has hint “http://”.
Facebook ID/username Rendered as a link. Has hint “e.g. 100000066953233”.
Twitter username Rendered as a link, displayed as @[Twitter username]. Has hint “e.g. twitter”.
LinkedIn Rendered as a link. Has hint “http://”.

As you see almost all of them have a reason to be included into Extended profile... However I believe I went the wrong way now!

This also answers your second question - right now custom fields are supported by core Redmine! For this the plugin is not needed!

Here is what I could do and what I believe could be a better solution:

  • Overwrite how custom fields are rendered. That is support some render types e.g.:
    • Link (href) with <choose another field> and Link (anchor) with <choose another field>;
    • Link (if just starts with href:// maybe);
    • Twitter mention.
  • Define new custom field type “Project list”.

Now these fields cannot be removed! Users will be suprised if I do this... What I can do is to provide a form in administration panel to disable them...

#2 Updated by Daniel Seifert over 12 years ago

Andriy Lesyuk wrote:

As you see almost all of them have a reason to be included into Extended profile...

I think this is the wrong way to look at it. Of course it’s better to render them “properly”, however this does not alleviate the problem that for some installations this set of provided fields does not match their list of required fields.

This also answers your second question - right now custom fields are supported by core Redmine! For this the plugin is not needed!

Ah, I entirely overlooked this option! Yes, this should solve some of these problems.

Here is what I could do and what I believe could be a better solution:

  • Overwrite how custom fields are rendered. That is support some render types e.g.:
    • Link (href) with <choose another field> and Link (anchor) with <choose another field>;
    • Link (if just starts with href:// maybe);
    • Twitter mention.
  • Define new custom field type “Project list”.

Now these fields cannot be removed! Users will be suprised if I do this... What I can do is to provide a form in administration panel to disable them...

Not sure what you mean by “cannot be removed”.

However the idea with render types is very nice. You could predefine some common types and otherwise have admins provide a template for displayed text and link.

#3 Updated by Andriy Lesyuk over 12 years ago

Not sure what you mean by “cannot be removed”.

I mean should not be removed! Saying you have 5,000 users 1,000 of which specified LinkedIn... If plugin upgrade removes a field these data will be lost.

#4 Updated by Daniel Seifert over 12 years ago

Of course. However there could be the option to automatically convert them. Alternatively it may be interesting to add an option to hide certain fields.

#5 Updated by Andriy Lesyuk over 12 years ago

  • Status changed from Incomplete to In Progress
  • % Done changed from 0 to 50

#6 Updated by Andriy Lesyuk over 12 years ago

  • % Done changed from 50 to 80

#7 Updated by Andriy Lesyuk over 12 years ago

  • % Done changed from 80 to 100

#8 Updated by Andriy Lesyuk over 12 years ago

  • Status changed from In Progress to Won't Fix

#9 Updated by Andriy Lesyuk over 12 years ago

Released Extended Profile 1.0.0 which is based on Extended Fields... This does what you wanted!

#10 Updated by Daniel Seifert over 12 years ago

Perfect! Thank you very much, this looks great!

Also available in: Atom PDF

Terms of use | Privacy policy