• 7
    • 9
    • Hide
      Atlassian Update –

      23 February 2018
      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      I understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      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 your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 23 February 2018 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  I understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server 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 your 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.

      Leschev is the reporter - useful seeing the limits at the top of the columns and probably within the cell.

            [JSWSERVER-3681] Ability to have cell (column and swimlane) min/max constraints

            Ryan Shaw added a comment -

            +1

            Ryan Shaw added a comment - +1

            +1

            +1

            Jira Team,

            I'm echoing the above comments. As a Kanban team, it is crucial for us to have more granular control over WIP limits at the swimlane and person level at the least (though it would also be helpful to configure limits in regards to labels and components).

            Tayyaba Sharif added a comment - Jira Team, I'm echoing the above comments. As a Kanban team, it is crucial for us to have more granular control over WIP limits at the swimlane and person level at the least (though it would also be helpful to configure limits in regards to labels and components).

            Joe Amato added a comment -

            Another strong vote for this feature.  This request has been open and wanted by paying customers for (literally) over a decade and it's not complicated to implement.

            Multi-project tracking should be a key feature of Jira.

            Joe Amato added a comment - Another strong vote for this feature.  This request has been open and wanted by paying customers for (literally) over a decade and it's not complicated to implement. Multi-project tracking should be a key feature of Jira.

            Greg added a comment -

            A plugin or app that might address this issue: Advanced Agile & Kanban Boards by Release Management.

            Greg added a comment - A plugin or app that might address this issue: Advanced Agile & Kanban Boards by Release Management .

            I agree with Patrick and others.  Running a kanban team this is very important to us. So many workarounds when we can makes it so complex to manage. I hope Atlassian will revisit this sooner than in a year. Thank You, Jean 

            Jean Turnauckas added a comment - I agree with Patrick and others.  Running a kanban team this is very important to us. So many workarounds when we can makes it so complex to manage. I hope Atlassian will revisit this sooner than in a year. Thank You, Jean 

            Jira Team,

            I'm echoing the above comments. As a Kanban team, it is crucial for us to have more granular control over WIP limits at the swimlane and person level at the least (though it would also be helpful to configure limits in regards to labels and components).

            Patrick Lindsey added a comment - Jira Team, I'm echoing the above comments. As a Kanban team, it is crucial for us to have more granular control over WIP limits at the swimlane and person level at the least (though it would also be helpful to configure limits in regards to labels and components).

            Silvia Levai added a comment - - edited

            Hi Jira,

            we would also appreciate an addition of this feature.

            It is a very simple but effective way to increase productivity and overview within a Kanban-System.

            I also support the opinion that it should be a basic feature for any system providing Kanban.

             

            We would be very happy to see this feature implemented as soon as possible.

             

            Thank you

             

             

            Silvia Levai added a comment - - edited Hi Jira, we would also appreciate an addition of this feature. It is a very simple but effective way to increase productivity and overview within a Kanban-System. I also support the opinion that it should be a basic feature for any system providing Kanban.   We would be very happy to see this feature implemented as soon as possible.   Thank you    

            asaf2b added a comment - - edited

            Kanban support is weak in Jira.  An organization has a mix of Scrum and Kanban teams.  Please ramp up Kanban support.

            • Setting horizontal WIP limits (flexible to set by person, by level of service, or by some other grouping)
            • Setting a WIP limit on a group of columns or entire board
            • Column hierarchy. Ability to have under a given column, say "Development", sub-columns "In Progress" and "Done".  So you end up with "Development In Progress" and "Development Done".  Being able to do this for every column.  WIP limits applied at the "Development" level and not separate for "Development In Progress" and "Development Done".

            Refer to Kanban Practices - The six core Kanban practices - Aktiasolutions

            asaf2b added a comment - - edited Kanban support is weak in Jira.  An organization has a mix of Scrum and Kanban teams.  Please ramp up Kanban support. Setting horizontal WIP limits (flexible to set by person, by level of service, or by some other grouping) Setting a WIP limit on a group of columns or entire board Column hierarchy. Ability to have under a given column, say "Development", sub-columns "In Progress" and "Done".  So you end up with "Development In Progress" and "Development Done".  Being able to do this for every column.  WIP limits applied at the "Development" level and not separate for "Development In Progress" and "Development Done". Refer to  Kanban Practices - The six core Kanban practices - Aktiasolutions

              Unassigned Unassigned
              nmuldoon Nicholas Muldoon [Atlassian]
              Votes:
              623 Vote for this issue
              Watchers:
              249 Start watching this issue

                Created:
                Updated: