Possibility to add project specific user information #9196

New Issue

GiteaMirror · 2025-11-02T08:32:02-06:00

GiteaMirror commented

2025-11-02 08:32:02 -06:00

Originally created by @xeruf on GitHub (Jul 8, 2022).

Feature Description

When opening or commenting issues, one usually should state the version of the product in use.
This can quickly get tiring as one adds the same information over and over, potentially having to look it up repeatedly.

This could be separated into general information (e.g. operating system on my computer, browser I usually use) and project-specific information (e.g. OS of a server VM, software version). Gitea could then show this information combined when hovering over a user while browsing an issue.

Implementation

I would imagine this as a freetext key-value list, one should probably consider limiting the length and number of entries.

If one deviates in a specific issue (maybe while backtracing a regression), one can always still mention that in the issue description, but I think this feature can already save lots of back and forth.

Future

In the future, one could integrate this elegantly with issue templates by giving structured elements in issue templates keys and making them non-mandatory when those keys are already provided in the profile. Or maybe even better, simply prefill them :)

This would provide a serious advantage over Github for active users!

Screenshots

No response

Originally created by @xeruf on GitHub (Jul 8, 2022). ### Feature Description When opening or commenting issues, one usually should state the version of the product in use. This can quickly get tiring as one adds the same information over and over, potentially having to look it up repeatedly. This could be separated into general information (e.g. operating system on my computer, browser I usually use) and project-specific information (e.g. OS of a server VM, software version). Gitea could then show this information combined when hovering over a user while browsing an issue. ## Implementation I would imagine this as a freetext key-value list, one should probably consider limiting the length and number of entries. If one deviates in a specific issue (maybe while backtracing a regression), one can always still mention that in the issue description, but I think this feature can already save lots of back and forth. ## Future In the future, one could integrate this elegantly with issue templates by giving structured elements in issue templates keys and making them non-mandatory when those keys are already provided in the profile. Or maybe even better, simply prefill them :) This would provide a serious advantage over Github for active users! ### Screenshots _No response_

GiteaMirror added the type/feature type/proposal labels 2025-11-02 08:32:02 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9196