add custom fields/attribute to issues #8326

Open
opened 2025-11-02 08:02:27 -06:00 by GiteaMirror · 7 comments
Owner

Originally created by @andrewchenshx on GitHub (Jan 8, 2022).

Feature Description

I think it would be great if custom attributes/fields could be added to issues.
Taiga has this feature while it's too heavyweight compared to Gitea.
thanks :)

Screenshots

No response

Originally created by @andrewchenshx on GitHub (Jan 8, 2022). ### Feature Description I think it would be great if custom attributes/fields could be added to issues. Taiga has this feature while it's too heavyweight compared to Gitea. thanks :) ### Screenshots _No response_
GiteaMirror added the type/proposal label 2025-11-02 08:02:27 -06:00
Author
Owner

@andyculmer commented on GitHub (Sep 15, 2022):

I agree that this would be a valuable feature. I would certainly be keen to migrate more projects to Gitea if custom fields were supported.

I note that this is a duplicate of #8665 and #20466, which were closed as not planned on the 24th July 2022.

The fact that 3 issues have been raised suggests there is some interest in this feature.

@andyculmer commented on GitHub (Sep 15, 2022): I agree that this would be a valuable feature. I would certainly be keen to migrate more projects to Gitea if custom fields were supported. I note that this is a duplicate of #8665 and #20466, which were closed as not planned on the 24th July 2022. The fact that 3 issues have been raised suggests there is some interest in this feature.
Author
Owner

@andyculmer commented on GitHub (May 28, 2024):

GitHub has had this feature for 2 years now, but I notice there's been no further comment on this proposal.

The issue tracker seems to be one area where Gitea doesn't quite match GitHub's feature set. I appreciate that Gitea does not have the development resources that GitHub has, so it would be great to understand whether this is a gap that's likely to be closed in the next year or so, or whether there's perhaps a strategic reason that this isn't being looked at. For example, is the strategy to defer to an external issue tracker for those that need this level of functionality and keep development effort focused on those areas that can't be so easily offloaded?

Any insights would be genuinely appreciated and would help with our longer term planning for tool selection. We may also be in a position to develop and contribute patches for some of this functionality, but I'm concerned that we could be paddling up stream.

@andyculmer commented on GitHub (May 28, 2024): GitHub has had this feature for 2 years now, but I notice there's been no further comment on this proposal. The issue tracker seems to be one area where Gitea doesn't quite match GitHub's feature set. I appreciate that Gitea does not have the development resources that GitHub has, so it would be great to understand whether this is a gap that's likely to be closed in the next year or so, or whether there's perhaps a strategic reason that this isn't being looked at. For example, is the strategy to defer to an external issue tracker for those that need this level of functionality and keep development effort focused on those areas that can't be so easily offloaded? Any insights would be genuinely appreciated and would help with our longer term planning for tool selection. We may also be in a position to develop and contribute patches for some of this functionality, but I'm concerned that we could be paddling up stream.
Author
Owner

@lunny commented on GitHub (May 29, 2024):

I think yes, we have far less resources than Github.

Can you link some documentation or design about how Github support custom fields? I never used this feature on Github.

@lunny commented on GitHub (May 29, 2024): I think yes, we have far less resources than Github. Can you link some documentation or design about how Github support custom fields? I never used this feature on Github.
Author
Owner

@andyculmer commented on GitHub (May 29, 2024):

Thanks for your reply @lunny

GitHub adds two more types of View in addition to Gitea's Kanban board. These are Roadmap and Table. In the Table view, you can not only customize the columns in the table to add the standard issue fields, but you can also create new fields.

The documentation is as follows:

@andyculmer commented on GitHub (May 29, 2024): Thanks for your reply @lunny GitHub adds two more types of _View_ in addition to Gitea's Kanban board. These are _Roadmap_ and _Table_. In the _Table_ view, you can not only customize the columns in the table to add the standard issue fields, but you can also create new fields. The documentation is as follows: * [Custom fields](https://docs.github.com/en/issues/planning-and-tracking-with-projects/understanding-fields/about-text-and-number-fields) * [The different view layouts](https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/changing-the-layout-of-a-view) * [The tables view](https://docs.github.com/en/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-the-table-layout)
Author
Owner

@lunny commented on GitHub (May 29, 2024):

I have a PR #30205, maybe it's related.

@lunny commented on GitHub (May 29, 2024): I have a PR #30205, maybe it's related.
Author
Owner

@andyculmer commented on GitHub (May 29, 2024):

Some great features there, but looks mainly focused on labels. I didn't see any mention of custom fields in the list of resolved issues.

@andyculmer commented on GitHub (May 29, 2024): Some great features there, but looks mainly focused on labels. I didn't see any mention of custom fields in the list of resolved issues.
Author
Owner

@KevinKrueger commented on GitHub (Jul 14, 2025):

Table View with custom fields....... game changer! Excel good bye!

@KevinKrueger commented on GitHub (Jul 14, 2025): Table View with custom fields....... game changer! Excel good bye!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8326