Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-5834

As a user, I would like to configure label, select, check, radio and version fields to be shown on the detail view

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.1.2
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      COS:

      • Label custom fields
      • Select & Multi select custom fields - Check & multi check - Radio
      • Version custom field

      Testing Notes

      Q: How many of these fields can you add?
      A: As many as you like

      Q: Will these be selectable in the detail view? Or only the current state of the field?
      A: Read-only

      Q: How will we display a field with multiple selections?
      A: Comma-separated

      Q: Will there be any problem adding fields that have duplicate names?
      A: No, field configuration is stored by id. It would be hard to know which one is which though

            [JSWSERVER-5834] As a user, I would like to configure label, select, check, radio and version fields to be shown on the detail view

            Merged into default

            Nikolay Petrov (Inactive) added a comment - Merged into default

            Added also cascading select type

            Nikolay Petrov (Inactive) added a comment - Added also cascading select type

            We need to implement a cascade select field.

            Nikolay Petrov (Inactive) added a comment - We need to implement a cascade select field.

            branch GHS-5834-more-detailview-fields

            Nikolay Petrov (Inactive) added a comment - branch GHS-5834 -more-detailview-fields

            +1 single select lists

            (we use it to define sprint teams)

            Fabian Meier added a comment - +1 single select lists (we use it to define sprint teams)

            dtollefson: Yes, should be 6.0.6

            Shaun Clowes (Inactive) added a comment - dtollefson : Yes, should be 6.0.6

            Cool. That's the best solution. Is "next release" 6.0.6? or a more major one?

            Dave Tollefson added a comment - Cool. That's the best solution. Is "next release" 6.0.6? or a more major one?

            Hi dtollefson,

            We will be releasing the first cut of revamped Epic support in the next version of GreenHopper, we won't be adopting the label approach used in the old GreenHopper.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi dtollefson , We will be releasing the first cut of revamped Epic support in the next version of GreenHopper, we won't be adopting the label approach used in the old GreenHopper. Thanks, Shaun

            re: Labels. We're running GH 6.0.5 and the detail has the "Labels" field shown by default, which is a label field. But the Objective/Epic/Theme field is not available to display. Whassup with that? Why one and not all?

            I would add that for us, not being able to see the Objective/Epic/Theme field on the "new" board is another big reason we'll stick with the Classic until the "new" are usable. I understand a new method of handling Obj/Epic/Themes is in the works, but until then we should have the existing functionality available - as in having that field visible and clickable (to get the popup window and/or the Issue Navigator view of the hierarchy).

            Dave Tollefson added a comment - re: Labels. We're running GH 6.0.5 and the detail has the "Labels" field shown by default, which is a label field. But the Objective/Epic/Theme field is not available to display. Whassup with that? Why one and not all? I would add that for us, not being able to see the Objective/Epic/Theme field on the "new" board is another big reason we'll stick with the Classic until the "new" are usable. I understand a new method of handling Obj/Epic/Themes is in the works, but until then we should have the existing functionality available - as in having that field visible and clickable (to get the popup window and/or the Issue Navigator view of the hierarchy).

              Unassigned Unassigned
              sclowes Shaun Clowes (Inactive)
              Votes:
              21 Vote for this issue
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: