New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add feature: Custom Fields #807

Open
xet7 opened this Issue Feb 8, 2017 · 116 comments

Comments

Projects
None yet
@xet7
Member

xet7 commented Feb 8, 2017

From @xet7 on January 10, 2017 16:50

Similar to Trello feature:
http://blog.trello.com/trello-custom-fields

Existing discussion at original Wekan forum:
https://discuss.wekan.io/t/any-way-to-add-new-data-on-cards/362/2

This wish is from original Wekan Gitter user @TutloTutlo

I did not find any existing pull request for this yet from original Wekan.

Wefork already has Due Date, so this new feature Custom Fields is separate from that.

If somebody has more information about this, please add it so it's ready here when somebody starts implementing this.

This issue is related to #43 and making Wekan programmable.

Copied from original issue: wefork#61

@xet7

This comment has been minimized.

Member

xet7 commented Feb 8, 2017

From @ehausen on January 24, 2017 21:14

In Trello custom fields are kind of a hack and only available per board. I'm thinking a better logic would be to define Card Types - like content types! This would very handy: Project card type, a Contact card type (for CRM purposes), etc...

Looking at Trello... Please someone (or me later) continue

  • User can define custom field types

    • Field Name
    • Field type (text, number, checkbox, date, dropdown, location? card reference? list reference? link? )
    • Is it displayed on the Card Front Badge when card not open
  • If fields are set they are listed at the top of the card

  • Fields should integrate with search and filters (not in trello)

@xet7

This comment has been minimized.

Member

xet7 commented Feb 8, 2017

From @tugal on January 25, 2017 15:0

Hi

i agree @ehausen, card types would be really interesting, letting every users to customize their card..

@xet7

This comment has been minimized.

Member

xet7 commented Feb 8, 2017

From @ehausen on January 25, 2017 15:4

Well I was actually thinking more along the lines of defining these at team or organization level - when there will be implemented. Probably the best would be to have permission where the admin can define which roles can do what.

@xet7 xet7 added the Feature label Feb 8, 2017

@tugal

This comment has been minimized.

Contributor

tugal commented Feb 9, 2017

Hi,

I'm trying to develop it.

Design
Add new menu entry (I'm actually planning in provide a list of available custom field names)

capture d ecran 2017-02-09 a 10 17 48

capture d ecran 2017-02-09 a 10 18 27

Then, display it (quick UI only to POC)

capture d ecran 2017-02-09 a 10 19 49

Is it what we need ?
thanks,

@jLouzado

This comment has been minimized.

Contributor

jLouzado commented Feb 9, 2017

@tugal yup, this looks awesome. :)

A few thoughts though:

  • The 'Custom field' title seems redundant, instead it could just be the field name as the h3 and the value below it.
  • What's the limit on number of custom fields that can be created?
@xet7

This comment has been minimized.

Member

xet7 commented Feb 9, 2017

@tugal @jLouzado

Can you look at Wekan forum https://discuss.wekan.io/ and search these Wekan github issues and mention them with @ github name? So we could get more info what is required? I have not used Custom Fields and didn't read description of it.

@xet7

This comment has been minimized.

Member

xet7 commented Feb 9, 2017

@tugal @jLouzado Please work on this together, and then submit pull request to Wekan devel branch.

@jLouzado

This comment has been minimized.

Contributor

jLouzado commented Feb 9, 2017

@tugal please DM me on wekan chat and we can take it forward. :)

@tugal

This comment has been minimized.

Contributor

tugal commented Feb 9, 2017

Hi

The 'Custom field' title seems redundant, instead it could just be the field name as the h3 and the value below it.

In my mind, the first field (CustomFieldName) should be a select, where the user can select a predefined custom field, and then the second field is its value

What's the limit on number of custom fields that can be created?

No limit, since a Card have X custom fields (i think, we should create a new Collection to store that information)

I checked : http://blog.trello.com/trello-custom-fields.
Maybe we should start small : to be trello-like, we need an Admin Ui to build all customs fields, and finally a new entry in card's menu

Where can we add new UI to create customs field ?

@jLouzado

This comment has been minimized.

Contributor

jLouzado commented Feb 9, 2017

@tugal come online on the wekan channel, we'll discuss it further if that's okay with you? https://chat.vanila.io/channel/wekan

I think a good place to start would be to see the code you've already written first? Then we can add what's missing.

@tugal

This comment has been minimized.

Contributor

tugal commented Feb 9, 2017

@jLouzado : i will joint you later.

Î am trying to copy Trello. It's ok for thé UI, but i struggle on the new modèl to create.

Is someone able to Help me or available to develop this pièce ?

Thanks

@jLouzado

This comment has been minimized.

Contributor

jLouzado commented Feb 9, 2017

@tugal can you share the code you have so far? either your repo directly or else you can create a pull-request.

@tugal

This comment has been minimized.

Contributor

tugal commented Feb 10, 2017

Hi,

It's a work in progress : https://github.com/tugal/wekan
The model piece is quite complicated for a meteor newbie like me :)

@xet7

This comment has been minimized.

Member

xet7 commented Feb 10, 2017

@tugal @jLouzado

Can you look is any code from this pull request useful?
#413

It currently has some conflicts.

@tugal

This comment has been minimized.

Contributor

tugal commented Feb 10, 2017

@xet7 : Do you want us to check this PR ? this one is not related to custom fields

@xet7

This comment has been minimized.

Member

xet7 commented Feb 10, 2017

@tugal

In that PR is adding of manHour, which is like added Custom Fields, but otherwise it's not related. If it does not have anything you need in your Custom Fields implementation, just ignore it for now.

@jLouzado

This comment has been minimized.

Contributor

jLouzado commented Feb 13, 2017

@tugal I think I might be able to help you out with the model; just taking a look at this today. 🙂

@ChangePlaces

This comment has been minimized.

ChangePlaces commented Mar 8, 2017

Any update on this? Awesome absolutely essential feature for real-world use!

@jLouzado

This comment has been minimized.

Contributor

jLouzado commented Mar 9, 2017

@ChangePlaces didn't realize it was such a desired feature... will work on it next week. :)

@xet7

This comment has been minimized.

Member

xet7 commented Jun 17, 2017

#1063 has code related to this, but there is merge errors.

@jonculver

This comment has been minimized.

jonculver commented Jul 6, 2017

Is there any news on this? I'd love to try out wekan and this feature is a must-have for my usecase. It looks like #1063 has been closed but I'm not sure if a new pull request has been made yet?

@xet7

This comment has been minimized.

Member

xet7 commented Jul 7, 2017

@jonculver

Current pull request for Custom Fields is #1079

It still has merge errors.

@xet7

This comment has been minimized.

Member

xet7 commented Jul 13, 2017

Moved to here from #1115

  • Add complexity field to card
  • Filtering and sorting by complexity field
@therampagerado

This comment has been minimized.

therampagerado commented May 31, 2018

I would like to see another addition...

Link field - just a normal text field where the imput is link and can be clicked.

In our case it will help with organizing working files - the user can make new order, attach the pdf for it but the working files are big sometimes and I wish we can keep them out of the DB.

@feuerball11

This comment has been minimized.

Contributor

feuerball11 commented May 31, 2018

Some things i found while creating my own board:

  • Type of Custom Fields cant be changed, i dont think thats terrible bad, you still can delete it and redefine (remapping all existing values could lead to problems anyway) but it should be greyed out, so you know you cant edit
  • Dropdown Items on Card display there ID, not there Value
  • Missing Type: Float Numbers
  • Missing Type: Calculated (Thats kinda one dream from me, that you can have fields that contain calcualated values. For example for recipes: Total Wight = SUM( Butter, Milk, Flour))
    ANd for Advanced Filters:
  • Additional Feature: Wildcards
@feuerball11

This comment has been minimized.

Contributor

feuerball11 commented May 31, 2018

I would post a public Wekan Board where i keep track of what i'm doing with custom Fields, But becouse of #1623 thats currently not possible. Sry.

@sfahrenholz

This comment has been minimized.

sfahrenholz commented May 31, 2018

Hallo there!

i have a question about the custom fields. Currently there are four types supported, how complexity is it to support for example URL? Thanks for the answer.

@xet7

This comment has been minimized.

Member

xet7 commented May 31, 2018

@sfahrenholz

If Custom Field would support Markdown in text field like at my comment above, URL could be added as markdown like this:

[Wekan website](https://wekan.github.io)

I have not tested yet does text field have Markdown support.

@therampagerado

This comment has been minimized.

therampagerado commented May 31, 2018

The markdown is not an option in some cases. If I'm pushing this system to peers that have written everything on hand by now it will be very hard to convince them to learn how to format the URLs...

It have to be copy&paste job.

@xet7

This comment has been minimized.

Member

xet7 commented May 31, 2018

@therampagerado

Ok, then there should be new URL field type, where link name and URL can be pasted to their 2 input fields.

@therampagerado

This comment has been minimized.

therampagerado commented May 31, 2018

Why do we need name in this field?

@therampagerado

This comment has been minimized.

therampagerado commented May 31, 2018

One more fix would be if Details field recognizes ftp and http/s links and convert them to URLs. Currently we have to copy/paste from there.

Then it will be easy, they can write:

Working file 1 - http://some_link
Working file 2 - http://some_other_link

@xet7

This comment has been minimized.

Member

xet7 commented May 31, 2018

@therampagerado

Because links can be long, see #1389
It easier to click on short descriptive name.

@DejfCold

This comment has been minimized.

DejfCold commented May 31, 2018

@therampagerado I suppose that if you had a long link, it would clutter the card with it. So I guess it would be better if we did have a name field

@therampagerado

This comment has been minimized.

therampagerado commented May 31, 2018

I think this can be fixed with max_width or some URL truncating where the middle part of those nasty long URLs is hidden so the field containing it is displayed in a nice manner...

@xet7

This comment has been minimized.

Member

xet7 commented May 31, 2018

I think Details view is fine as it is currently. I did have enough trouble with removing emoji code automatic conversion, because it did break MAC addresses and other formatting. If you need http(s) or ftp link to be made clickable, you should use Custom Field for that.

@xet7

This comment has been minimized.

Member

xet7 commented May 31, 2018

Sure if someone adds pull request to implement making http(s) and ftp links etc, and it does not break anything, it's OK. Anyone can add any feature, if it does not break anything.

xet7 added a commit that referenced this issue Jun 14, 2018

- Markdown support in Custom Fields, and view on minicard
- Fixes to Advanced Filter, you are now able to filter for Dropdown and Numbers,
  also Dropdown are now correctly displayed on minicard
- Fix Issue with custom fields shown on card
- Fix showing public board in list mode
- Fix for not able to remove Custom Field "Show on Card"

Related #807

Closes #1659,
closes #1623,
closes #1683
@feuerball11

This comment has been minimized.

Contributor

feuerball11 commented Jun 14, 2018

Now you can see my private wekan board i use for keeping track on the custom field features:
https://wekan.maschath.de/b/auEh7ahYZB4txQm6p/wekandev
(and sometimes some other stuff)

@sfahrenholz

This comment has been minimized.

sfahrenholz commented Jun 21, 2018

@feuerball11 thanks for the overview.

i have a question about the custom field. Currently only the card information will be exported to json, is there any plan to export the custom field settings and the import of this?

@xet7 xet7 removed this from Needs checking in Wekan Roadmap Jun 24, 2018

@danielgoletz

This comment has been minimized.

danielgoletz commented Jul 11, 2018

@feuerball11 is it possible to set a coustom field as a standard field for new cards?

@xet7

This comment has been minimized.

Member

xet7 commented Aug 29, 2018

@nicosmaris

This comment has been minimized.

nicosmaris commented Sep 4, 2018

For a newcomer like me, it is a bit confusing to see custom fields in the latest stable release at snap while this PR is still open.

After some hours of editing my board, I created a custom field, added it to a card, deleted the field from the board and now it seams that I have to try the workaround below to get my data back...

#1703 (comment)

@xet7

This comment has been minimized.

Member

xet7 commented Sep 5, 2018

@nicosmaris

Maybe this could also help #1872 (comment)

This issue is open, because not all Custom Fields features are implemented yet.

Pull requests to for fixing Custom Fields and other bugs welcome.

Fixing bugs is also on my Roadmap, when I get some free time for it.

@nicosmaris

This comment has been minimized.

nicosmaris commented Sep 6, 2018

Thanks.

I understand that the project is open source and that as most software there is no warranty but I assume that the end user of wekan is not only DBAs with mongoDB experience :)

@xet7

This comment has been minimized.

Member

xet7 commented Sep 6, 2018

@nicosmaris

Yes, it takes time before everything is easy point and click, and that day is coming nearer every day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment