Skip to content

[JENKINS-12548] Read-only system configuration browsing #12412

Open
16 of 18 issues completed
Open

Description

@jenkins-infra-bot

It would be useful if the read-only version of the configuration page is rendered substantially different from the editable configuration page.

For example, read-only config page shouldn't show any options that aren't checked,
and every "advanced" sections should be expanded out of the box. (or perhaps even
render to a plain text instead of HTML)


Originally reported by kohsuke, imported from: Read-only system configuration browsing
  • status: In Progress
  • priority: Major
  • component(s): core
  • label(s): jcasc-compatibility
  • resolution: Unresolved
  • votes: 5
  • watchers: 10
  • imported: 2025-11-24
Raw content of original issue

It would be useful if the read-only version of the configuration page is rendered substantially different from the editable configuration page.

For example, read-only config page shouldn't show any options that aren't checked, and every "advanced" sections should be expanded out of the box. (or perhaps even render to a plain text instead of HTML)

Activity

  1. jenkins-infra-bot commented on Jan 26, 2012

    @jenkins-infra-bot
    Author
  2. jenkins-infra-bot commented on May 27, 2019

    @jenkins-infra-bot
    Author
  3. jenkins-infra-bot commented on Oct 18, 2019

    @jenkins-infra-bot
    Author
    jglick:
    • Original comment link
    • Raw content of original comment:

      From the discussion of JCasC I am guessing this is being interpreted in the context of global settings. There is a somewhat analogous RFE for project settings: JENKINS-50173.

    From the discussion of JCasC I am guessing this is being interpreted in the context of global settings. There is a somewhat analogous RFE for project settings: JENKINS-50173.

  4. jenkins-infra-bot commented on Jan 23, 2020

    @jenkins-infra-bot
    Author
    oleg_nenashev:
    • Original comment link
    • Raw content of original comment:

      Should it be an EPIC now?

    Should it be an EPIC now?

  5. jenkins-infra-bot commented on Feb 24, 2020

    @jenkins-infra-bot
    Author
    oleg_nenashev:

    Foundation bits were landed in https://jenkins.io/changelog/#v2.222 . Now we definitely need an EPIC timja

  6. jenkins-infra-bot commented on Feb 26, 2020

    @jenkins-infra-bot
    Author
    danielbeck:
    • Original comment link
    • Raw content of original comment:

      Someone reported this issue in the changelog feedback, but it's unclear what's wrong.

    Someone reported this issue in the changelog feedback, but it's unclear what's wrong.

  7. jenkins-infra-bot commented on Feb 26, 2020

    @jenkins-infra-bot
    Author
    timja:
    • Original comment link
    • Raw content of original comment:

      yeah not useful at all

    yeah not useful at all

  8. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    Author

    [Original is_duplicated_by from Jira: JENKINS-32533]

  9. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    Author

    [Original is_duplicated_by from Jira: JENKINS-13434]

  10. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    Author

    [Original relates_to from Jira: JENKINS-66911]

  11. 6 remaining items

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