Skip to content
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

Open
thomaswacker opened this issue Jul 22, 2023 · 7 comments
Open

Custom fields for projects, issues, epics #89

thomaswacker opened this issue Jul 22, 2023 · 7 comments
Assignees
Labels
enhancement New feature or request feature New feature to implement help wanted Extra attention is needed

Comments

@thomaswacker
Copy link

I often need custom fields, especially for issues. The scope for a custom field should be

  • for all project
  • for selected projects

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.

@mihaisolomon
Copy link
Collaborator

Could you put some screenshots to have an idea. I worked a long time ago with redmine.

@thomaswacker
Copy link
Author

thomaswacker commented Jul 23, 2023

Here are some screenshots from my Redmine.

Overview:

admin_custom_fields_overview

Create field - first step:

admin_create_custom_field_2

Create field - second step:

admin_create_custom_field_1

@mihaisolomon mihaisolomon added enhancement New feature or request feature New feature to implement labels Jul 24, 2023
@mihaisolomon
Copy link
Collaborator

Could you put the Redmine task view with some custom fields added, so we will know how it will look in the end.

@thomaswacker
Copy link
Author

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.

@mihaisolomon
Copy link
Collaborator

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:

  • Create the interface where we can add delete update the custom fields.
  • Update the create of the ticket view to add those custom fields in the flow.
  • Update the editing of the ticket to make possible the editing for the tickets.

If I'm missing something please add here.

@thomaswacker
Copy link
Author

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).

redmine_custom_fields.txt

@mihaisolomon
Copy link
Collaborator

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.

@mihaisolomon mihaisolomon added the help wanted Extra attention is needed label Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature New feature to implement help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants