• 7
    • 16
    • Hide
      Atlassian Update – 3 September 2018

      Hi everyone,

      Thanks for your interest in this issue. As jschumacher mentioned in his comment, the Jira Cloud team is working on this suggestion, for Jira Cloud please comment and vote on JSWCLOUD-6656.

      As for Jira Server it is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions:

      In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including:

      • Filters and dashboards collaborative editing
      • Selectable delimiters in CSV export 
      • Microsoft SQL Server 2016 support 
      • iPv6 support
      • Faster Kanban boards
      • Refreshed projects and custom fields management pages in the admin's section 

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 3 September 2018 Hi everyone, Thanks for your interest in this issue. As jschumacher mentioned in his comment, the Jira Cloud team is working on this suggestion, for Jira Cloud please comment and vote on  JSWCLOUD-6656 . As for Jira Server it is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions: Further performance and stability improvements Email notifications template editor available from the UI  JRASERVER-7266 Jira email notifications batching  JRASERVER-1369 Mobile app for Jira Server  JRASERVER-46149 Improved filter and dashboard management by Jira administrators  JRASERVER-15900  and  JRASERVER-41269   Adding the "updated-by" JQL search query  JRASERVER-1973 Support for 4 byte characters in MySQL connection  JRASERVER-36135 In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including: Filters and dashboards collaborative editing Selectable delimiters in CSV export  Microsoft SQL Server 2016 support  iPv6 support Faster Kanban boards Refreshed projects and custom fields management pages in the admin's section  We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more on how you suggestions are reviewed, see our  updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

       

      The ability to convert Rapid Agile boards between Scrum and Kanban types.

            [JSWSERVER-6656] Ability to convert Agile boards between Scrum and Kanban types

            Any update?
            since its two years from that last update, this could be considered 'long term' 

            John Matheson added a comment - Any update? since its two years from that last update, this could be considered 'long term' 

            +1

            Kersi Asare added a comment - +1

            +1

            James Hanley added a comment - +1

            Atlassian Update – 3 September 2018

            Hi everyone,

            Thanks for your interest in this issue. As jschumacher mentioned in his comment, the Jira Cloud team is working on this suggestion, for Jira Cloud please comment and vote on JSWCLOUD-6656.

            As for Jira Server it is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions:

            In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including:

            • Filters and dashboards collaborative editing
            • Selectable delimiters in CSV export 
            • Microsoft SQL Server 2016 support 
            • iPv6 support
            • Faster Kanban boards
            • Refreshed projects and custom fields management pages in the admin's section 

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Jira Server Product Management

            Kasia Derenda added a comment - Atlassian Update – 3 September 2018 Hi everyone, Thanks for your interest in this issue. As jschumacher mentioned in his comment, the Jira Cloud team is working on this suggestion, for Jira Cloud please comment and vote on  JSWCLOUD-6656 . As for Jira Server it is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including the top-voted suggestions: Further performance and stability improvements Email notifications template editor available from the UI  JRASERVER-7266 Jira email notifications batching  JRASERVER-1369 Mobile app for Jira Server  JRASERVER-46149 Improved filter and dashboard management by Jira administrators  JRASERVER-15900  and  JRASERVER-41269   Adding the "updated-by" JQL search query  JRASERVER-1973 Support for 4 byte characters in MySQL connection  JRASERVER-36135 In the recent Jira Server releases we have also shipped some highly-voted features and improvements, including: Filters and dashboards collaborative editing Selectable delimiters in CSV export  Microsoft SQL Server 2016 support  iPv6 support Faster Kanban boards Refreshed projects and custom fields management pages in the admin's section  We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more on how you suggestions are reviewed, see our  updated workflow for server feature suggestions . Kind regards, Jira Server Product Management

            +1

            Hi I ma interesting to find the methodologie to change my kanban board to an agile board. 

            Unfortunately, the two links below are error pages. Could you explain how to do it ?

            Sonia PASCAL added a comment - Hi I ma interesting to find the methodologie to change my kanban board to an agile board.  Unfortunately, the two links below are error pages. Could you explain how to do it ?

            +1

            +1

            Denis Kozlov added a comment - +1

            It’s actually super easy to create a scrum board for the existing Kanban project then u have both boards. Just use the same filter from the project. Hope this helps. Now all my projects are both Kanban and scrum board enabled.

            George Adams IV added a comment - It’s actually super easy to create a scrum board for the existing Kanban project then u have both boards. Just use the same filter from the project. Hope this helps. Now all my projects are both Kanban and scrum board enabled.

            Nits G added a comment -

            please also allow to convert Agility board to Scrum

            +1

            Nits G added a comment - please also allow to convert Agility board to Scrum +1

            +1

            Daniel Obst added a comment - +1

            +1

            Jorge Vargas added a comment - +1

            +1

            Reuel Reis added a comment -

            +1

            Reuel Reis added a comment - +1

            +1

            That would be a very helpful feature.

            Thomas Rumeau added a comment - That would be a very helpful feature.

            This would be a very helpful feature to have.

            Mike Flores added a comment - This would be a very helpful feature to have.

            @Joshua Balsillie thanks, I must have missed that comment from Jens, I thought the last Atlassian response appeared to be some time ago.

            Adam Robertson added a comment - @Joshua Balsillie thanks, I must have missed that comment from Jens, I thought the last Atlassian response appeared to be some time ago.

            @Adam Robertson, Andrew Mills and Munjal,

            There has been communication from Atlassian, and progress is being made, however it is not reflected in this issue. The Atlassian team may have another open issue that encompasses this issue, but it sounds as if progress is being made. Shouldn't have to "communicate with them directly" as they've seen this issue and stated they've started working on it.

            Atlassian Responses in this Issue

            https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=694560&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-694560

            https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=729834&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-729834

            https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=1067547&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1067547

            https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=1721609&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1721609

            • jens@atlassian.com: "Thanks everyone for their input. We are actively working on making the transition between Scrum and Kanban seamless."

             

            Joshua Balsillie added a comment - @Adam Robertson, Andrew Mills and Munjal, There has been communication from Atlassian, and progress is being made, however it is not reflected in this issue. The Atlassian team may have another open issue that encompasses this issue, but it sounds as if progress is being made. Shouldn't have to "communicate with them directly" as they've seen this issue and stated they've started working on it. Atlassian Responses in this Issue https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=694560&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-694560 https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=729834&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-729834 https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=1067547&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1067547 https://jira.atlassian.com/browse/JSWSERVER-6656?focusedCommentId=1721609&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1721609 jens@atlassian.com : "Thanks everyone for their input. We are actively working on making the transition between Scrum and Kanban seamless."  

            I think there's a good chance we all have development backgrounds.  It shouldn't be about ROI, it should be about customer satisfaction.  Also, if the answer is no, they should at least tell people why instead of leaving everyone here hanging forever. 

            Adam Robertson added a comment - I think there's a good chance we all have development backgrounds.  It shouldn't be about ROI, it should be about customer satisfaction.  Also, if the answer is no, they should at least tell people why instead of leaving everyone here hanging forever. 

            Coming from a Development background, what we are asking could be very difficult to accomplish, maybe the ROI just isn't there. Perhaps that is why no one has answered this thread. Has anyone tried communicating with them directly?

            Andrew Mills added a comment - Coming from a Development background, what we are asking could be very difficult to accomplish, maybe the ROI just isn't there. Perhaps that is why no one has answered this thread. Has anyone tried communicating with them directly?

            Adam Robertson added a comment - - edited

            Not sure what happened with my last comment–but:

            @Andrew while I agree with you on tone, it's absolutely infuriating to be essentially ignored on such a reasonable and oft-requested feature.  There currently doesn't appear to be a solution to the issue without spending days of work and losing all history in the process–if there is I think a lot of people here are missing it.  Perhaps SOME communication from the development or product teams would be helpful since this issue has been open for over half a decade?

            Adam Robertson added a comment - - edited Not sure what happened with my last comment–but: @Andrew while I agree with you on tone, it's absolutely infuriating to be essentially ignored on such a reasonable and oft-requested feature.  There currently doesn't appear to be a solution to the issue without spending days of work and losing all history in the process–if there is I think a lot of people here are missing it.  Perhaps SOME communication from the development or product teams would be helpful since this issue has been open for over half a decade?

            Munjal, all I am saying is complaining about it isn't the way to go. I'd appreciate it if you could keep that kind of commenting off this thread

            Andrew Mills added a comment - Munjal, all I am saying is complaining about it isn't the way to go. I'd appreciate it if you could keep that kind of commenting off this thread

            Munjal added a comment -

            Andrew - for the past 4 years??

            I don't believe that it's the devs issue - it's the program manager / product owner issue.

            Munjal added a comment - Andrew - for the past 4 years?? I don't believe that it's the devs issue - it's the program manager / product owner issue.

            @Munjal

            That is a very unfair and unprofessional response. I am certain the developers care for their users and are working their hardest.

            Andrew Mills added a comment - @Munjal That is a very unfair and unprofessional response. I am certain the developers care for their users and are working their hardest.

            Munjal added a comment -

            Hey guys! What's wrong with y'all?

            It's been more than 4 years that this feature has been asked and y'all not taking a serious look at this?!!

             

            Or is that you don't give a shit about y'all users?

             

            Munjal added a comment - Hey guys! What's wrong with y'all? It's been more than 4 years that this feature has been asked and y'all not taking a serious look at this?!!   Or is that you don't give a shit about y'all users?  

            +1 I will also like to see this feature added. Project teams can change approach and adapt midway.

             

            charanjeet singh added a comment - +1 I will also like to see this feature added. Project teams can change approach and adapt midway.  

            jens added a comment -

            Thanks everyone for their input. We are actively working on making the transition between Scrum and Kanban seamless.

            jens added a comment - Thanks everyone for their input. We are actively working on making the transition between Scrum and Kanban seamless.

            +1 please add this... My client has a kanban project/board and is moving towards needing more forward planning... thx, JP

            Jeff Pierce added a comment - +1 please add this... My client has a kanban project/board and is moving towards needing more forward planning... thx, JP

            +1, please add this missing functionality. Current method of replacing a Kanban board with a Scrum board of the same name via board deletion or vice versa is rather unintuitive.

            Jonathan Ang added a comment - +1, please add this missing functionality. Current method of replacing a Kanban board with a Scrum board of the same name via board deletion or vice versa is rather unintuitive.

            I get this question almost daily from the teams that use the Jira instance I am an admin for. It's very frustrating to not be able to do this and causes a large amount of extra work. I would love to see this feature added

            Deleted Account (Inactive) added a comment - I get this question almost daily from the teams that use the Jira instance I am an admin for. It's very frustrating to not be able to do this and causes a large amount of extra work. I would love to see this feature added

            Lots of people are looking for this feature according to the related article: https://community.atlassian.com/t5/Jira-questions/Change-Board-Type-from-KanBan-to-Scrum/qaq-p/82343

            I for one would also like to see this feature. As project structures and teams change and adapt so do the way things are done. Personally the division of Kaban and Scrum boards doesn't make sense to me. The categorization of these two types does, but dividing them into separate buckets entirely does not.

            Joshua Balsillie added a comment - Lots of people are looking for this feature according to the related article: https://community.atlassian.com/t5/Jira-questions/Change-Board-Type-from-KanBan-to-Scrum/qaq-p/82343 I for one would also like to see this feature. As project structures and teams change and adapt so do the way things are done. Personally the division of Kaban and Scrum boards doesn't make sense to me. The categorization of these two types does, but dividing them into separate buckets entirely does not.

            This feature would be helpful.

            I have many users who have created complicated quickfilters and swimlanes based on JQL and having an easy way for them to switch or "copy and change board type" would be most helpful.

             

            Rick Carini added a comment - This feature would be helpful. I have many users who have created complicated quickfilters and swimlanes based on JQL and having an easy way for them to switch or "copy and change board type" would be most helpful.  

            Adam Robertson added a comment - - edited

            I just clicked on my Kanban board, clicked the options (...) icon, clicked "Create board", and added a scrum board.  Everything not done appears in the backlog, which is exactly what I wanted.  So it looks like this might actually be solved? You have to make sure you're viewing the scrum board in the dropdown, but it looks like conversion works in this way?

            Adam Robertson added a comment - - edited I just clicked on my Kanban board, clicked the options (...) icon, clicked "Create board", and added a scrum board.  Everything not done appears in the backlog, which is exactly what I wanted.  So it looks like this might actually be solved? You have to make sure you're viewing the scrum board in the dropdown, but it looks like conversion works in this way?

            Ines Pons added a comment -

            The proposed solution of exporting/importing board settings would do the work for me as well

            Ines Pons added a comment - The proposed solution of exporting/importing board settings would do the work for me as well

            Hope this is helpfull, it was for me.

            In JIRA boards are simply views on projects. It is the projects that contain the stories, epics and other issue types.

            This means that you can create a new board that points at an existing project.

            Say for example your original Kanban board was called 'Team X'. When that was created it would have created a project called 'Team X' as well. The board would be a view on this project.

            You can now create a new board of type Scrum. Make sure that when you create it you chose the option 'Board from an existing project'. Then select the project that you were using previously (in my example it is the one called 'Team X').

            Now you have a Scrum board that shows all the issues that were on your Kanban board.

            You don't even need to get rid of the Kanban board. Both of them will still work.

            This is the Atlassian page that explains how to create a new board

             

            https://pm.stackexchange.com/questions/17809/how-do-i-convert-a-jira-kanban-board-to-a-scrum-board

             

            Zaid Baban added a comment - Hope this is helpfull, it was for me. In JIRA boards are simply views on projects. It is the projects that contain the stories, epics and other issue types. This means that you can create a new board that points at an existing project. Say for example your original Kanban board was called 'Team X'. When that was created it would have created a project called 'Team X' as well. The board would be a view on this project. You can now create a new board of type Scrum. Make sure that when you create it you chose the option 'Board from an existing project'. Then select the project that you were using previously (in my example it is the one called 'Team X'). Now you have a Scrum board that shows all the issues that were on your Kanban board. You don't even need to get rid of the Kanban board. Both of them will still work. This is the Atlassian page that explains how to create a new board   https://pm.stackexchange.com/questions/17809/how-do-i-convert-a-jira-kanban-board-to-a-scrum-board  

            Recently i've looked at the rapidview table and see a column SPRINTS_ENABLED:

            SELECT * FROM ao_60db71_rapidview;
            

            It seems that a simple change of the value to 0 (Kanban) or 1 (Scrum) change the board type..

            Tim Eddelbüttel added a comment - Recently i've looked at the rapidview table and see a column SPRINTS_ENABLED : SELECT * FROM ao_60db71_rapidview; It seems that a simple change of the value to 0 (Kanban) or 1 (Scrum) change the board type..

            As an add-on, it would be perfect if we were able to choose which settings to import. So, if we already have an existing board, but want to import for example only card colours from another (template) board, then we'd be able to do that without overwriting any of the other settings.

            Maximilian Hantsch added a comment - As an add-on, it would be perfect if we were able to choose which settings to import. So, if we already have an existing board, but want to import for example only card colours from another (template) board, then we'd be able to do that without overwriting any of the other settings.

            salem.korayem160032443, that would absolutely work for me. I think it's an excellent suggestion.

            Maximilian Hantsch added a comment - salem.korayem160032443 , that would absolutely work for me. I think it's an excellent suggestion.

            Maybe a better solution would be "export/import" `board settings` that typically covers the following:

            • quick filters
            • swimlanes
            • card layout
            • card colors
            • working days
            • issue detail view
            • estimation

            Salem Korayem added a comment - Maybe a better solution would be "export/import" `board settings` that typically covers the following: quick filters swimlanes card layout card colors working days issue detail view estimation

            mjopson yes, while you can create another board with the same filter, you will have to reconfigure all the board settings.

            We use a lot of JQL quick filters and custom card colour configurations, and it takes a lot of time to reconfigure all of these, just in order to change the board type!

            BR
            Max

            Maximilian Hantsch added a comment - mjopson yes, while you can create another board with the same filter, you will have to reconfigure all the board settings. We use a lot of JQL quick filters and custom card colour configurations, and it takes a lot of time to reconfigure all of these, just in order to change the board type! BR Max

            Thanks for watching and commenting on this Suggestion.

            Where possible please add use-cases for the conversion from Scrum to Kanban or vice-versa, this assists with our research and potential solutions.

            Please also note, as a workaround, it is fairly easy to create a new board which use the same filter, so a Kanban board can be created with the same content as a Scrum one.

            Kind regards,
            Martin
            JIRA Software

            Martin (Inactive) added a comment - Thanks for watching and commenting on this Suggestion. Where possible please add use-cases for the conversion from Scrum to Kanban or vice-versa, this assists with our research and potential solutions. Please also note, as a workaround, it is fairly easy to create a new board which use the same filter, so a Kanban board can be created with the same content as a Scrum one. Kind regards, Martin JIRA Software

            Max Nebl added a comment -

            +1 
            It's important for us too - we have a huge kanban board for customer projects and now we need to move to a scrum oriented process on this board. This means I need to create a new board plus hundreds of tickets that need to be bulk edited.... 

            Max Nebl added a comment - +1  It's important for us too - we have a huge kanban board for customer projects and now we need to move to a scrum oriented process on this board. This means I need to create a new board plus hundreds of tickets that need to be bulk edited.... 

            1+. We could use that, too

            Andreas Hoppe added a comment - 1+. We could use that, too

            Zaid Baban added a comment -

            Got the same concern, is there anyway we can switch from Kanban to Scrum view?

            Zaid Baban added a comment - Got the same concern, is there anyway we can switch from Kanban to Scrum view?

            +1

            Our project started with kanban, but now we want to switch to scrum with existing hundred tickets there so that we can have sprint.

            Xiaojing Si added a comment - +1 Our project started with kanban, but now we want to switch to scrum with existing hundred tickets there so that we can have sprint.

            Andrew Mills added a comment - - edited

            Yes I would love this aswell. Please!

            In my case, I do not wish to create a new board and have to update all my external links.

            Andrew Mills added a comment - - edited Yes I would love this aswell. Please! In my case, I do not wish to create a new board and have to update all my external links.

            josue.tello412303070 added a comment -

            +2

            josue.tello412303070 added a comment - +2

            ++1

            Victor Pedroso added a comment - ++1

            +1

            Joe Cross added a comment -

            Another big reason for a convert vs. "create new and replace" is to retain the URL of the original board.  Otherwise, you have to update Confluence links and make sure everyone stops using the old board and starts using the new board.  By converting the board and retaining the URL, these issues go away.

            Joe Cross added a comment - Another big reason for a convert vs. "create new and replace" is to retain the URL of the original board.  Otherwise, you have to update Confluence links and make sure everyone stops using the old board and starts using the new board.  By converting the board and retaining the URL, these issues go away.

            The original feature request description says: "The ability to convert Agile boards between Scrum and Kanban types."

            Charle's suggestion is: "Create new Scrum board using same filter as an existing Kanban board".

            Note that the difference is that the feature request is to be able to convert an existing Kanban board to a Scrum board, whereas Charle's suggestion is to create a new board not convert an existing board. The value of being able to convert is described in some of the above comments, such as the one from Tim Harris.

            +1 for this!

            Curtis Simonson added a comment - The original feature request description says: "The ability to convert Agile boards between Scrum and Kanban types." Charle's suggestion is: "Create new Scrum board using same filter as an existing Kanban board". Note that the difference is that the feature request is to be able to convert an existing Kanban board to a Scrum board, whereas Charle's suggestion is to create a new board not convert an existing board. The value of being able to convert is described in some of the above comments, such as the one from Tim Harris. +1 for this!

            Greg Smart added a comment -

            +1 for Charles, just did this! Perfect.

            Greg Smart added a comment - +1 for Charles, just did this! Perfect.

            I agree Charles: you can create a new board as Scrum with option from existing project. Then, wizard will ask for name and feeder project and you will get sprints management at all. Then you can tune up more board's properties: columns, filters, colors...

            Francisco Retuerta added a comment - I agree Charles: you can create a new board as Scrum with option from existing project. Then, wizard will ask for name and feeder project and you will get sprints management at all. Then you can tune up more board's properties: columns, filters, colors...

            +1 this would be great for us. I'm sure others have experienced the need to migrate to other agile methodologies as they mature or as project teams are split to do R&D / enhancements vs maintenance etc.

            Deleted Account (Inactive) added a comment - +1 this would be great for us. I'm sure others have experienced the need to migrate to other agile methodologies as they mature or as project teams are split to do R&D / enhancements vs maintenance etc.

            Hi Charles - how did you get the backlog to exist for both? Would love to do that for my project. Thanks.

            Shari McGuire added a comment - Hi Charles - how did you get the backlog to exist for both? Would love to do that for my project. Thanks.

            I'm a bit confused by this request. I had a project with a Kanban board, and when we changed to Agile I created a Scrum board for the project. The same backlog exists in both, so now I can switch between them at the click of a mouse. What am I missing?

            charles_gnshealthcare added a comment - I'm a bit confused by this request. I had a project with a Kanban board, and when we changed to Agile I created a Scrum board for the project. The same backlog exists in both, so now I can switch between them at the click of a mouse. What am I missing?

            I agree with the others - really need the ability to switch from a Scrum Board to a Kanban board and vice versa. Thanks.

            Shari McGuire added a comment - I agree with the others - really need the ability to switch from a Scrum Board to a Kanban board and vice versa. Thanks.

            Daniel Felten added a comment - - edited

            +1 This would be a great feature. In the moment I've got a Scrum project and would like to use it now as a Kanban board, but it's not possible and I don't know what to do now.

            Daniel Felten added a comment - - edited +1 This would be a great feature. In the moment I've got a Scrum project and would like to use it now as a Kanban board, but it's not possible and I don't know what to do now.

              Unassigned Unassigned
              itse Ivan Tse
              Votes:
              402 Vote for this issue
              Watchers:
              135 Start watching this issue

                Created:
                Updated: