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

Ability to map custom field to columns on the board

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • Board configuration
    • None
    • 1
    • 1
    • 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.

      As a JIRA Admin, I want to be able to use some custom status field as a base for columns separation. The system status field is used for all development tickets (Open, In Progress, In QA, Complete, etc).

      Meanwhile, Epics have an additional set of statuses as they represent a Release (Piepelined, Approved, In Ideation, In Execution, Under Review, Closed). So I would like to be able to create a Release Board with columns based on those custom statuses.

            [JSWSERVER-6838] Ability to map custom field to columns on the board

            Andy Ukasick added a comment -

            There appears to be a purchasable option at least:  https://marketplace.atlassian.com/apps/1211683/comala-canvas-for-jira  

            What this issue requests would be tremendously useful.

            Andy Ukasick added a comment - There appears to be a purchasable option at least:   https://marketplace.atlassian.com/apps/1211683/comala-canvas-for-jira   What this issue requests would be tremendously useful.

            mmunst added a comment -

            We want this too, but for Cloud.  Is there a similar request for Cloud?  This would solve so many problems we have with board configuration.  The way it is now, we end up adding a zillion statuses just so we can make the board columns work for us.  Having the ability to configure the columns based on a filter would eliminate the need for us to create so many statuses, which makes our workflows more complex and harder to maintain.

            mmunst added a comment - We want this too, but for Cloud.  Is there a similar request for Cloud?  This would solve so many problems we have with board configuration.  The way it is now, we end up adding a zillion statuses just so we can make the board columns work for us.  Having the ability to configure the columns based on a filter would eliminate the need for us to create so many statuses, which makes our workflows more complex and harder to maintain.

            christophe demez added a comment -

            We also need this, please reopen the ticket or provides us a reason for not reopening please.
            The goal is to provide a view based on other aspect than the status. By example, we have added a custom field "Business Value" with values "XL/M/L/S" and we wish a board to manage them. So, having a visual board and the ability to move from one colum to another with the team will be very helpful. Thanks

            christophe demez added a comment - We also need this, please reopen the ticket or provides us a reason for not reopening please. The goal is to provide a view based on other aspect than the status. By example, we have added a custom field "Business Value" with values "XL/M/L/S" and we wish a board to manage them. So, having a visual board and the ability to move from one colum to another with the team will be very helpful. Thanks

            Michael Holmes added a comment -

            The very inelegant work around has been to create additional swimlanes but that blows the board out badly. We've got products that need to be tested in multiple environments and don't want to have to create 4 different 'In QA' statuses so we have an 'environment tested in' field which could be used if columns could be done on queries like swimlanes can be.

             

            Michael Holmes added a comment - The very inelegant work around has been to create additional swimlanes but that blows the board out badly. We've got products that need to be tested in multiple environments and don't want to have to create 4 different 'In QA' statuses so we have an 'environment tested in' field which could be used if columns could be done on queries like swimlanes can be.  

            Matthew Redway added a comment - - edited

            We need this too. Did anybody get anywhere with this?

            Matthew Redway added a comment - - edited We need this too. Did anybody get anywhere with this?

            Gonzalo Martinez added a comment -

            I need it too for backlog health

            Gonzalo Martinez added a comment - I need it too for backlog health

            Wu Hao added a comment -

            I am still looking for workarounds, could anybody help me?

            Wu Hao added a comment - I am still looking for workarounds, could anybody help me?

            sinan.ucak added a comment -

            I need this too ! I want to create a board where I can map horizontally by Sprint (kind of like a timeline). Any workarounds for this one ?

            sinan.ucak added a comment - I need this too ! I want to create a board where I can map horizontally by Sprint (kind of like a timeline). Any workarounds for this one ?

            Tarang Zilpe added a comment -

            This is indeed needed everywhere. I had worked in 2 organisation and it is indeed needed.

            Workflow has statuses.. however we have defined a customer field for substatus. But cannot map it now.

            Tarang Zilpe added a comment - This is indeed needed everywhere. I had worked in 2 organisation and it is indeed needed. Workflow has statuses.. however we have defined a customer field for substatus. But cannot map it now.

            Gosia Kowalska added a comment -
            Atlassian Update – 14 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 14 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              08971236d00f Elena Chinenkova
              Votes:
              4 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: