Uploaded image for project: 'Jira Work Management Cloud'
  1. Jira Work Management Cloud
  2. JWMCLOUD-38

Lists do not show certain custom field types in the Column selection

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

      Atlassian Update - 13th of September  2024

      Hi everyone,

      Thank you for taking the time to share your feature request with us. We've shipped a solution that deals with the ask in this issue. Please read more here: https://support.atlassian.com/jira-work-management/docs/customize-your-list-by-adding-or-removing-fields/
      Please feel free to reach out if you feel there are more use cases to deal with.

      Kind Regards,
      Joe Nguyen
      Product Manager - Jira Cloud

       

      Update - June 19th, 2024

      This also affects Jira Software projects' lists.

      Update March 8th, 2023


      Since the creation of this feature request there have been a few updates and more custom field types can be added to the list view. From our documentation page Customize your list by adding or removing fields:

      • Date picker
      • Date time picker
      • Number field
      • Select field (single select)
      • Select field (multiple select)
      • Text field (single line)
      • Text fields (multi-line)
      • URL field
      • User picker (single user)
      • Text field (Read Only)

      At the moment some other custom fields are not available in the list view, like the Sprint field.

      This is a limitation by design as mentioned in the documentation page View your work in a list:
      "You can currently only add single line text fields, URLs and user types. Learn more about setting up custom fields." and due to this this request was converted from Bug to Suggestion to gauge the interest in having all field types available here.

      Custom fields created by Advanced Roadmap such as Target start & Target end are not supported in List view too.

      Issue Summary

      Lists do not show certain custom field types in the Column selection

      Steps to Reproduce

      1. Go to Custom Fields
      2. Create several custom fields of different types (Text Single line, Text Multiline, Date, etc):
      3. Add the new fields to the screen of your project:
      4. Go to your project Lists, and try to add the new custom fields as new columns using the "+" icon:

      Expected Results

      All the new custom fields are shown and can be added as a column.

      Actual Results

      Only Single line text custom fields appear in the list:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

       

        1. image-2021-05-14-15-36-10-791.png
          image-2021-05-14-15-36-10-791.png
          101 kB
        2. image-2021-05-14-15-38-05-642.png
          image-2021-05-14-15-38-05-642.png
          54 kB
        3. image-2021-05-14-15-38-29-684.png
          image-2021-05-14-15-38-29-684.png
          149 kB
        4. image-2021-05-14-15-39-29-096.png
          image-2021-05-14-15-39-29-096.png
          154 kB
        5. image-2021-05-14-15-40-11-332.png
          image-2021-05-14-15-40-11-332.png
          174 kB
        6. screenshot-1.png
          screenshot-1.png
          113 kB

            [JWMCLOUD-38] Lists do not show certain custom field types in the Column selection

            Such an important custom fields why not allow to be added in Jira Software Project List View?

            It's been more than 3 years, why as of today still yet to take into consideration? 

            Yong Pei Sun added a comment - Such an important custom fields why not allow to be added in Jira Software Project List View? It's been more than 3 years, why as of today still yet to take into consideration? 

            How is this fixed when you cannot add a custom field asset picker

            Fanny Vachet added a comment - How is this fixed when you cannot add a custom field asset picker

            John Funk added a comment -

            Atlassian - why is this marked as Fixed with no Assignee and no comment on what was doing??

            John Funk added a comment - Atlassian - why is this marked as Fixed with no Assignee and no comment on what was doing??

            This was marked "fixed" but no fixVersion.  I don't see it fixed in Cloud on our instance.  

            Derek Rone added a comment - This was marked "fixed" but no fixVersion.  I don't see it fixed in Cloud on our instance.  

            When will this be worked on Atlassian team? Fields like "fix versions" and "parent" are so crucial for a proper user experience, and we can't add them. This is high impactful for my teams. Thanks!

            Aline Chapman added a comment - When will this be worked on Atlassian team? Fields like "fix versions" and "parent" are so crucial for a proper user experience, and we can't add them. This is high impactful for my teams. Thanks!

            Derek Rone added a comment -

            "Target Start" and "Target End" are literally from Advanced Roadmaps...we need them added to the list view please.  Thank you.

            Derek Rone added a comment - "Target Start" and "Target End" are literally from Advanced Roadmaps...we need them added to the list view please.  Thank you.

            When will it be released ??

            marco.krickl added a comment - When will it be released ??

            Derek Rone added a comment -

            The list is a valuable function that leadership uses, as of now there is no way for leaders to see any type of "Start" or "End" or "Due" date in this view.  Thank you.

            Derek Rone added a comment - The list is a valuable function that leadership uses, as of now there is no way for leaders to see any type of "Start" or "End" or "Due" date in this view.  Thank you.

            JWMCLOUD-97 was closed as a duplicate of this issue, but they are not the same. This issue is about custom fields whereas 97 was about adding a basic JWM field–Resolved Date. 

            DeGaust, Linda added a comment - JWMCLOUD-97 was closed as a duplicate of this issue, but they are not the same. This issue is about custom fields whereas 97 was about adding a basic JWM field–Resolved Date. 

            Issue JWMCLOUD-192 was closed as a duplicate of this issue, but they are not the same. 

            JWMCLOUD-192 is about custom fields being available in the Filter option in List View.

            JWMCLOUD-38 is about custom fields being available to add as Columns in the List view.

            Those are entirely different features.

            Additionally various custom fields ARE available in the Columns additions, while NO custom fields are available in the Filters option.

            Trudy Claspill added a comment - Issue JWMCLOUD-192 was closed as a duplicate of this issue, but they are not the same.  JWMCLOUD-192 is about custom fields being available in the Filter option in List View. JWMCLOUD-38 is about custom fields being available to add as Columns in the List view. Those are entirely different features. Additionally various custom fields ARE available in the Columns additions, while NO custom fields are available in the Filters option.

              c9015ffb80f2 Joe Nguyen
              rchiquete Rene C. [Atlassian Support]
              Votes:
              50 Vote for this issue
              Watchers:
              61 Start watching this issue

                Created:
                Updated:
                Resolved: