Skip to content
Snippets Groups Projects

Limit project description length to 250 visible characters

    • Closed Issue created by Samuli @samulig

    Problem to solve

    Currently non-technical users would benefit having links to certain views of GitLab from their home pages, instead of having to navigate through multiple views and options. I've found it useful to add the links into the project description.

    I would like to create for example this kind of a description

    View the [focus board](/my-org-name/my-project-name/-/boards/1/), [report a bug](/my-org-name/my-project-name/issues/new?issuable_template=Bug), make a [feature request](/my-org-name/my-project-name/issues/new?issuable_template=Feature+Request), or see [high priority issues](/my-org-name/my-project-name/issues/?sort=priority).

    Which would look rendered as

    "View the focus board, report a bug, make a feature request, or see high priority issues.", but cannot, since the URLs take most of the characters, even though they're not visible in the description.

    Intended users

    The primary users would be non-technical users, that would like to have quick links to appropriate views in GitLab.

    Further details

    Currently the project description accepts markdown syntax and allows embedding links to it. However the maximum length is 250 characters, so you can embed only two or three links, because the link urls take space, even though they're not visible, which is the reason given here, for not increasing the limit: https://forum.gitlab.com/t/project-description-characters-limit-to-250/2588/2

    I would love to write a nice README.md, but it is pushed way down by the files list. One can hide the files list from the settings (Preferences -> Behaviour -> Project overview content), but this setting cannot be set as default for new or existing users, but must be toggled by the each user themselves.

    Proposal

    Either increase the project description character limit, or calculate the limit from visible characters only, i.e. the rendered Markdown content.

    Permissions and Security

    No permissions.

    Availability & Testing

    No risks.

    What does success look like, and how can we measure that?

    I would be able to create description with links.

    What is the type of buyer?

    Core / Free

    Edited by Samuli

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply