Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #7913 Raise the size of the email prefix field
    Actions
    Infos
    #7913
    BEN MANSOUR Med Rafik (benm)
    2015-05-05 14:35
    2015-03-06 11:20
    7926
    Details
    Raise the size of the email prefix field
    - Raise the size of the email prefix field and change it to a textera.
    - display a message when the field size exceeds its maximum characters's number.
    SCM/Git
    7.10
    Empty
    • [x] enhancement
    • [ ] internal improvement
    Camille CLIQUENNOIS (ccliquennois)
    Stage
    BEN MANSOUR Med Rafik (benm)
    Closed
    2015-05-05
    Attachments
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    BEN MANSOUR Med Rafik (benm)2015-04-03 16:17
    Hello Nicolas,

    No news from end user … It didn’t seem a priority for him so I’m afraid we can just let it go for now.

    Regards,
    Rafik
    User avatar
    Nicolas Terray (nterray)2015-03-09 17:34
    Please remember that prefix is only the part enclosed in brackets: [xXXXXX/XX:"ProjectName"]

    The following part (tag xx…xx created) is added by git notification hook. Therefore, if you put a prefix with 128 characters it won't help since all email notifications will begin by the same 128 characters long prefix. I don't see how this can be usable.

    Cannot the end user use a shorter name for his project in the prefix? By the way, what is her usage of the prefix?
    User avatar
    BEN MANSOUR Med Rafik (benm)2015-03-09 14:39
    last edited by: BEN MANSOUR Med Rafik (benm) 2015-03-09 15:54
    After discussing the matter again with end user, the need is to have both the project name and the git component name in the prefix like: [<projet>] <component> has been updated -
    Followed by the generated part.
    Unfortunately, component names are often long and if we take the example of "[xXXXXX/G6] XXXXXXXXX-XXXX-arch-development-filesystem-profile_pkg_ext has been updated - "
    It doesn’t fit and is truncated as follow:[xXXXXX/G6] XXXXXXXXX-XXXX-arch-development-filesystem-profile_p

    Even just 128 characters may not be enough with this kind of naming rule but at least it would be better. And a warning message when it won’t fit would allow to make exceptions to the rule when it is still too long instead of having truncated titles…
    • CC list set to Camille CLIQUENNOIS (ccliquennois)
    User avatar
    Nicolas Terray (nterray)2015-03-06 20:50
    Could you please give us some example of prefix that takes more than 64 characters?

    We agree that there should be a feedback to the user when the chosen prefix is too long, however 64 characters is somewhat decent for a prefix…
    User avatar
    BEN MANSOUR Med Rafik (benm)2015-03-06 16:22
    it's a request done by our client, He said :
    <<
    For each git repository, we can set a notification with a dedicated "notification prefix".
    The maximum size of this prefix is too small. Is it possible to get at least twice what is possible today?
    >>
    One more thing, when you type more than 64 character, only the 64 first chars are stored, the rest is ignored without notifying the user of the maximum supported length .
    User avatar
    Nicolas Terray (nterray)2015-03-06 13:58
    Why do you need to increase the length of the prefix? Which issue does it solve?
    • Status changed from New to Waiting for information