Skip to content

[JENKINS-72988] checking the displayname for jobs inside folders is performed against items in root #16406

@jenkins-infra-bot

Description

@jenkins-infra-bot

How to reproduce:

  1. Install folder plugin
  2. Create a freestyle job with name "project"
  3. create a folder with name "folder"
  4. create a freestyle job in the folder with name "subproject" 
  5. open configure page of "subproject" click on Advanced, enter in displayname "project"
  6. leave the text field
    -> You get a warning that the name "project" is already in use as a name by a job although in the folder is no conflicting job
  7. create a second job in the folder with name "p2"
  8. try to set the displayname of that second job to "subproject"
    No warning is shown although there is a conflict

 


Originally reported by mawinter69, imported from: checking the displayname for jobs inside folders is performed against items in root
  • assignee: mawinter69
  • status: Resolved
  • priority: Minor
  • component(s): core
  • resolution: Fixed
  • resolved: 2024-10-30T14:51:16+00:00
  • votes: 0
  • watchers: 1
  • imported: 2025-11-24
Raw content of original issue

How to reproduce:

  1. Install folder plugin
  2. Create a freestyle job with name "project"
  3. create a folder with name "folder"
  4. create a freestyle job in the folder with name "subproject" 
  5. open configure page of "subproject" click on Advanced, enter in displayname "project"
  6. leave the text field -> You get a warning that the name "project" is already in use as a name by a job although in the folder is no conflicting job
  7. create a second job in the folder with name "p2"
  8. try to set the displayname of that second job to "subproject" No warning is shown although there is a conflict

 

  • environment: Jenkins 2.453
1 attachment

Metadata

Metadata

Assignees

No one assigned

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions