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

Advanced Roadmaps - Add support for more custom fields to the plan view

    • 176
    • 32
    • 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.

      Summary

      Currently, Advanced Roadmaps plans only support a limited number of field types. As explained in Configure custom fields in Advanced Roadmaps, the following field types are supported:

      • checkbox
      • date picker
      • user picker (single user)
      • number
      • radio button
      • label
      • single-choice select
      • multiple-choice select
      • single-line text
      • URL (read-only)

      When trying to add more Custom Fields to a plan via the menu âš™ > Configure > Configure fields, the fields that are not supported will be greyed out with the label "UNSUPPORTED", as shown in the screenshot below:

      Suggestion

      Add support for:

      • Other Jira Native field types such as:
        • Date Time Picker
        • Select List (Cascading)
        • Text (Multi line)
      • custom fields coming from 3rd party add-ons such as:

          Form Name

            [JSWSERVER-25122] Advanced Roadmaps - Add support for more custom fields to the plan view

            Another +1 for Date Time field support.

            I cannot fathom why Date Time fields would not be supported in any Planning functionality from the start. As a Software Engineer I cannot believe that adding Date Time support wouldn't be a straightforward change/addition. However, as a Jira Administrator, flipping all projects from the instance-wide Date/Time fields to Date fields is not an easy option. We would have to:

            • Add new Date fields to replace the existing Date/Time ones.
            • Update all existing field and screen configs to remove the existing Date/Time fields and add the new Date equivalents.
            • Update any affected Workflow logic.
            • Script a copy of the existing Date/Time field values to the new equivalent Date fields.
            • Either get every user to check/change all existing filters to remove the old Date/Time fields and replace with the new Date fields, or as per the Teams field debacle, hack the database behind the scenes to search and replace all references to the old Date/Time fields and replace with the new Date fields.

            Given the history of this Suggestion and the fact that there has been little input from Atlassian, I guess that this is another issue that is going to have it's own birthdays.

            Barry Millar added a comment - Another +1 for Date Time field support. I cannot fathom why Date Time fields would not be supported in any Planning functionality from the start. As a Software Engineer I cannot believe that adding Date Time support wouldn't be a straightforward change/addition. However, as a Jira Administrator, flipping all projects from the instance-wide Date/Time fields to Date fields is not an easy option. We would have to: Add new Date fields to replace the existing Date/Time ones. Update all existing field and screen configs to remove the existing Date/Time fields and add the new Date equivalents. Update any affected Workflow logic. Script a copy of the existing Date/Time field values to the new equivalent Date fields. Either get every user to check/change all existing filters to remove the old Date/Time fields and replace with the new Date fields, or as per the Teams field debacle, hack the database behind the scenes to search and replace all references to the old Date/Time fields and replace with the new Date fields. Given the history of this Suggestion and the fact that there has been little input from Atlassian, I guess that this is another issue that is going to have it's own birthdays.

            +1 for Date Time Picker support - lack of support for this basic type greatly reduces the usefulness of Plans to our organization.

            Robin Powell added a comment - +1 for Date Time Picker support - lack of support for this basic type greatly reduces the usefulness of Plans to our organization.

            Not having custom fields of type Date Time picker creates constrains when managing issues that need to be executed sequentially in very precise time frames, a more waterfall approach to the usage but that still is needed for some teams.

            Sérgio Nogueira added a comment - Not having custom fields of type Date Time picker creates constrains when managing issues that need to be executed sequentially in very precise time frames, a more waterfall approach to the usage but that still is needed for some teams.

            Please add support for Asset field types.

            Robert Davenport added a comment - Please add support for Asset field types.

            +1 to add ad Date Time picker as a supported field. This is basic component of plans/schedules.

            Anto Abraham added a comment - +1 to add ad Date Time picker as a supported field. This is basic component of plans/schedules.

            Dara Try added a comment -

            +1 we'd like more supported fields

            Dara Try added a comment - +1 we'd like more supported fields

            Would it ever be in scope to implement Version picker (multiple versions)?

            Neta Rothman added a comment - Would it ever be in scope to implement Version picker (multiple versions)?

            At Magenta Austria, we have tightly synchronised processes whose planning involves dates and times. We therefore urgently need the Date Time Picker datatype. It is actually incomprehensible why this is missing.

            Helmut Schreiber added a comment - At Magenta Austria, we have tightly synchronised processes whose planning involves dates and times. We therefore urgently need the Date Time Picker datatype. It is actually incomprehensible why this is missing.

            Dennis S. added a comment -

            +1

            Dennis S. added a comment - +1

            I've noticed that the votes from the previous similar tickets aren't carried over to this one which puts in back in the queue.  Can we get an update pls?  This is REALLY preventing this from being a more useful tool.

            Williams, Kris added a comment - I've noticed that the votes from the previous similar tickets aren't carried over to this one which puts in back in the queue.  Can we get an update pls?  This is REALLY preventing this from being a more useful tool.

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              107 Vote for this issue
              Watchers:
              89 Start watching this issue

                Created:
                Updated: