Skip to content

[JENKINS-17575] Incorrect redirection after delete of job in folder in view #14484

Description

@jenkins-infra-bot

If you create a top-level list view v, to which you add a folder d, and add a job j inside the folder, then delete j, you are redirected to /view/v/ rather than /view/v/job/d/ as expected.

This is because in AbstractProject.doDoDelete, req.findAncestorObject(View.class) is v, whose url is view/v/. In this case we would be better served by using the super method's logic (the branch where view == null), since parent.url is view/v/job/d/ which is what we want. The use of view.url is only appropriate in case that view's view group is the same as this job's parent.


Originally reported by jglick, imported from: Incorrect redirection after delete of job in folder in view
  • status: Resolved
  • priority: Minor
  • component(s): core
  • label(s): 1.509.4-fixed, folders
  • resolution: Fixed
  • resolved: 2013-04-11T15:39:37+00:00
  • votes: 0
  • watchers: 3
  • imported: 2025-11-24
Raw content of original issue

If you create a top-level list view v, to which you add a folder d, and add a job j inside the folder, then delete j, you are redirected to /view/v/ rather than /view/v/job/d/ as expected.

This is because in AbstractProject.doDoDelete, req.findAncestorObject(View.class) is v, whose url is view/v/. In this case we would be better served by using the super method's logic (the branch where view == null), since parent.url is view/v/job/d/ which is what we want. The use of view.url is only appropriate in case that view's view group is the same as this job's parent.

No activity

Activity on this issue will appear here.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions