Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63104

The word "Project" in job page headers should be removed

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • Jenkins 2.222.3

      The <h1> header of Jenkins's job/project page (i.e., https://my-jenkins-instance.com/job/my-job) prepends the job's name with the word "Project". For example, if the job is called "My Job", the header will say "Project My Job". Every other page just refers to a job/project by its name, without the word "Project". Even on this page, the <title> tag lacks the word "Project". But for some reason, "Project" looks as if it's part of the job's name in this page's header. This frequently leads to mistakes such as:

      • Copying/pasting the whole header as the job's name into conversations
      • Including "Project" in the job's name when referring to it in documentation
      • Trying unsuccessfully to search for "Project My Job" using the search bar

      If removing the word from the page entirely is not an option, it should at least be separated from the <h1> tag and reformatted to look more like a label (e.g., "Project: My Job" or "Job: My Job").

          [JENKINS-63104] The word "Project" in job page headers should be removed

          Oleg Nenashev added a comment -

          Maybe we could replace the word by a logo to save space and improve look&feel. It is not only about "project", we also have "pipeline", "branch", "folder" and other types. Iconography there could help

          CC fqueiruga joseph_brueggen, WDYT?

           

          Oleg Nenashev added a comment - Maybe we could replace the word by a logo to save space and improve look&feel. It is not only about "project", we also have "pipeline", "branch", "folder" and other types. Iconography there could help CC fqueiruga joseph_brueggen , WDYT?  

          Steve Farbota added a comment -

          I like that idea. And thank you for adding the additional context.

          Steve Farbota added a comment - I like that idea. And thank you for adding the additional context.

          I cannot find what this issue refers to? Do you mean the "Full project name" string?

          Adding icons to identify item type is fine by me, but we'd need to do it in a way that can be applied to all types, even those provided by plugins.

           

          Félix Queiruga Balado added a comment - I cannot find what this issue refers to? Do you mean the "Full project name" string? Adding icons to identify item type is fine by me, but we'd need to do it in a way that can be applied to all types, even those provided by plugins.  

          Oleg Nenashev added a comment -

          > Adding icons to identify item type is fine by me, but we'd need to do it in a way that can be applied to all types, even those provided by plugins.

          We could actually do it in a compatible way:

          • Use item logo when specified. There are logos available for top-level items (see the "New Item" screen). API extension might be needed to support icons in other item types
          • If Icon is not available, put text as before

           

          Icon examples:

          Oleg Nenashev added a comment - > Adding icons to identify item type is fine by me, but we'd need to do it in a way that can be applied to all types, even those provided by plugins. We could actually do it in a compatible way: Use item logo when specified. There are logos available for top-level items (see the "New Item" screen). API extension might be needed to support icons in other item types If Icon is not available, put text as before   Icon examples:

          Oleg Nenashev added a comment -

          FTR about implementation and available API, see https://github.com/jenkinsci/jenkins/pull/2117 from recena. getIconFilePathPattern() is available for TopLevelItemDescriptor implementations, hence it will address the use-cases

          sfarbota would you like to try implementing it?

           

          Oleg Nenashev added a comment - FTR about implementation and available API, see  https://github.com/jenkinsci/jenkins/pull/2117  from recena . getIconFilePathPattern() is available for TopLevelItemDescriptor implementations, hence it will address the use-cases sfarbota would you like to try implementing it?  

          Steve Farbota added a comment -

          I'd be more than happy to. I'll start working on a PR tonight.

          Steve Farbota added a comment - I'd be more than happy to. I'll start working on a PR tonight.

          Steve Farbota added a comment - - edited

          And to clarify for fqueiruga - I am referring to the <h1> tag in this file: https://github.com/jenkinsci/jenkins/blob/337b44428f49a76100f7c915c6366e585e13966f/core/src/main/resources/hudson/model/Job/index.jelly#L30

          The relevant line is line 30:

                <h1 class="job-index-headline page-headline">${it.pronoun} <l:breakable value="${it.displayName}"/></h1>
          

          My original suggestion was to just remove "${it.pronoun} ". But I'm going to try to implement Oleg's proposal of replacing that text with the appropriate icon. I'll make the change for the other similar pages as well, such as branch pages (see Oleg's first attached screenshot).

          Steve Farbota added a comment - - edited And to clarify for fqueiruga - I am referring to the <h1> tag in this file: https://github.com/jenkinsci/jenkins/blob/337b44428f49a76100f7c915c6366e585e13966f/core/src/main/resources/hudson/model/Job/index.jelly#L30 The relevant line is line 30: <h1 class= "job-index-headline page-headline" >${it.pronoun} <l:breakable value= "${it.displayName}" /></h1> My original suggestion was to just remove " ${it.pronoun } ". But I'm going to try to implement Oleg's proposal of replacing that text with the appropriate icon. I'll make the change for the other similar pages as well, such as branch pages (see Oleg's first attached screenshot).

          Oleg Nenashev added a comment -

          sfarbota Hi! Do you still plan to work on it? If so, could you please assign the issue to yourself? If not, I might be able to take a look at it during one of the weekends

          Oleg Nenashev added a comment - sfarbota Hi! Do you still plan to work on it? If so, could you please assign the issue to yourself? If not, I might be able to take a look at it during one of the weekends

          Steve Farbota added a comment -

          Yep, I'll be looking at it this week as I've taken the week off from my day job. Just assigned to myself. Thanks for the reminder.

          Steve Farbota added a comment - Yep, I'll be looking at it this week as I've taken the week off from my day job. Just assigned to myself. Thanks for the reminder.

          Oleg Nenashev added a comment -

          Ack, thanks for the response! I will find another UX task from the backlog

          Oleg Nenashev added a comment - Ack, thanks for the response! I will find another UX task from the backlog

            sfarbota Steve Farbota
            sfarbota Steve Farbota
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: