Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-87234

Provide the possibility to add "Target end", "Target start" and "Start date" field in the List View.

XMLWordPrintable

    • 0
    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When in a list view inside a project both fields "Target end", "Target start" and "Start date" are not possible to be selected to be displayed on the grid. Both fields are possibly to be selected in the issue lists and the documentation says that both should be selectable since they are date pickers.

      Please feel free to reach me to gather more details if needed.

            [JRACLOUD-87234] Provide the possibility to add "Target end", "Target start" and "Start date" field in the List View.

            Aaron Lieb added a comment -

            Please see more details about the request:

            Supported, “locked” fields in the Jira List feature:

            • Target start & Target end (locked fields used in Jira Portfolio/Advanced Roadmaps)
            • Team (locked field, Team[team], used by Atlassian Teams)

            We have been moving toward adopting Jira features such as Advanced Roadmaps and the Atlassian Team field. We have switched over from using regular custom fields to the required locked ones in order to get the most out of these two sets of features. With “List” also being an Atlassian Feature, it would help our team members if they could use all three Feature sets; List, Advanced Roadmaps, Atlassian Team, cohesively by supporting the same required locked fields.

            Workaround: None (Without introducing field syncing/copying values to regular, supported custom fields. However, we would see this as going backwards to introduce for the added administrative overhead, and we have spent quite a bit of effort migrating OFF of using custom fields instead of the “Atlassian feature introduced, locked fields”

            Please see https://support.atlassian.com/requests/PCS-343004/ for more details about this request.

            Aaron Lieb added a comment - Please see more details about the request: Supported, “locked” fields in the Jira List feature: Target start & Target end (locked fields used in Jira Portfolio/Advanced Roadmaps) Team (locked field, Team [team] , used by Atlassian Teams) We have been moving toward adopting Jira features such as Advanced Roadmaps and the Atlassian Team field. We have switched over from using regular custom fields to the required locked ones in order to get the most out of these two sets of features. With “List” also being an Atlassian Feature, it would help our team members if they could use all three Feature sets; List, Advanced Roadmaps, Atlassian Team, cohesively by supporting the same required locked fields. Workaround: None (Without introducing field syncing/copying values to regular, supported custom fields. However, we would see this as going backwards to introduce for the added administrative overhead, and we have spent quite a bit of effort migrating OFF of using custom fields instead of the “Atlassian feature introduced, locked fields” Please see https://support.atlassian.com/requests/PCS-343004/ for more details about this request.

              Unassigned Unassigned
              c79e6a70f93d Ivan Jose (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: