-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
Custom fields for projects, issues, epics #89
Comments
Could you put some screenshots to have an idea. I worked a long time ago with redmine. |
Could you put the Redmine task view with some custom fields added, so we will know how it will look in the end. |
It looks like every other field. You can't see any difference between custom fields and default fields, except they are placed below the default fields. |
I found this packaged https://github.com/sunel/eav that could solve a part o the problem, let's say managing the custom fields. The only thing that needs done it's the interface and the way we create the tickets to add those fields into the views. From my point we have to do the followings:
If I'm missing something please add here. |
That would be one possibility. Another possibility would be to use only one table for the values - that's how Redmine does it. You can use "textarea" as the data type for the field. Attached are all the tables from a Redmine instance for custom fields ("custom_field_enumerations" was never filled). |
The structure is almost the same with the one generated by this library https://github.com/sunel/eav . The only difference is that we have some of the logic already done. I will start soon a PR with some basic functionalities and we go from there. |
I often need custom fields, especially for issues. The scope for a custom field should be
In Redmine you can do this very easy. I know its not as easy to implement as you need for Filament. But it would be a great enhancement.
The text was updated successfully, but these errors were encountered: