You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the existing issues for duplicate feature requests
I have checked that this feature request is not on our roadmap
What parts of Modrinth is your feature request related too?
API, Website
Is your suggested feature related to a problem? Please describe.
Projects owned by an organization are displayed on search as being owned by the org owner. While this makes some sense, when working in an org it's more often the case that different people create different projects in an org, so attribution of [project] by [owner] should be able to be overridden per project, for proper attribution and maybe some other stuff that could work with this as well.
Describe the solution you'd like
An option to designate an owner override in the Members setting of a project, if owned by an org, would be the simplest and ideal solution.
Describe alternatives you've considered
An alternative could be not transferring the mod to an org at all. However, that could cause confusion to end users in some cases.
Additional context
An example of this can be seen below.
The text was updated successfully, but these errors were encountered:
Please confirm the following.
What parts of Modrinth is your feature request related too?
API, Website
Is your suggested feature related to a problem? Please describe.
Projects owned by an organization are displayed on search as being owned by the org owner. While this makes some sense, when working in an org it's more often the case that different people create different projects in an org, so attribution of [project] by [owner] should be able to be overridden per project, for proper attribution and maybe some other stuff that could work with this as well.
Describe the solution you'd like
An option to designate an owner override in the Members setting of a project, if owned by an org, would be the simplest and ideal solution.
Describe alternatives you've considered
An alternative could be not transferring the mod to an org at all. However, that could cause confusion to end users in some cases.
Additional context
An example of this can be seen below.
The text was updated successfully, but these errors were encountered: