Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-17392 Team-managed software projects
  3. JSWCLOUD-17331

Add "Board settings" to next-gen projects

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Duplicate
    • None
    • None
    • next-gen
    • None

      Atlassian status as of October 2020

      Hello all,

      Thank you very much for voting, watching, and/or commenting on this ticket. We appreciate the huge amount of feedback, not just from customers who came directly to this ticket themselves, but also from customers who reached out to our support teams with questions or problems and were then directed to this ticket.

      “Board settings” is a very broad problem to solve because, by itself, it doesn’t tell us what exactly customers are trying to configure. Hence, we have read through all the comments here and from tickets raised through our support team. We’ve found that there are several different, specific settings that customers would like to configure, but they have been all broadly amalgamated into the term “board settings”. The settings that have been specifically requested from the comments are:

      • the ability to define working days in a project: JSWCLOUD-17773
      • the ability to find out how many days a card has been in a column: JSWCLOUD-20809
      • the ability to use colours to quickly identify cards: JSWCLOUD-17277
      • the ability to choose which labels appear on cards in the board/backlog: JSWCLOUD-17450
      • the ability to choose which fields appear on cards in the board/backlog: JSWCLOUD-17336
      • the ability to create Components in next-gen projects: JSWCLOUD-17601
      • the ability to have multiple boards in a next-gen project: JSWCLOUD-17371
      • the ability to have a board with issues from multiple projects (including issues from next-gen projects): JSWCLOUD-17444
      • the ability to create templates to be used when creating next-gen projects: JSWCLOUD-17982
      • the ability to create a new status without creating a column (coming really soon!): JSWCLOUD-17434
      • the ability to set limits on the number of issues in a column (you can do this now)

      Each of these settings, except the last one, have an existing ticket associated with it. Kindly vote/watch/comment the specific settings that are relevant to you. If you feel the settings you are looking for aren’t listed above, kindly tell us about it. Meanwhile, we will close this ticket.

      Again, thank you for your feedback and patience.

      Cheers,
      Emily Chan
      Atlassian.

      Currently, due to the restrictions next-gen projects has, we can't change Working days, card colors, layout, columns issue limits, for example.
      It would be good if we could have the option to change these simple settings on next-gen projects.

            [JSWCLOUD-17331] Add "Board settings" to next-gen projects

            andycaseASA added a comment -

            I'll join the queue who want this

            andycaseASA added a comment - I'll join the queue who want this

            Arthur Konrath added a comment - - edited

            Why is it called next-gen project if there is less features???

            Working days setting is essential to get burn up and down charts working properly.

            I am pretty disappointed now that I discovered its not implemented and being requested for more than 4 years.

            (when next-gen projects actually should have born with that).

            This is my first next-gen project and I think I will have to create and setup everything from 0 to get things working thew way I need.

            I am really thinking on migrating to another service.

            Arthur Konrath added a comment - - edited Why is it called next-gen project if there is less features??? Working days setting is essential to get burn up and down charts working properly. I am pretty disappointed now that I discovered its not implemented and being requested for more than 4 years. (when next-gen projects actually should have born with that). This is my first next-gen project and I think I will have to create and setup everything from 0 to get things working thew way I need. I am really thinking on migrating to another service.

            Isaac picado added a comment -

            I need to be able to customize the fields that are visible from the backlog list, I have created a custom field that shows the urgency on the bug to be resolved different than priority and I need to see this from a single glance.

            Isaac picado added a comment - I need to be able to customize the fields that are visible from the backlog list, I have created a custom field that shows the urgency on the bug to be resolved different than priority and I need to see this from a single glance.

            Deleted Account (Inactive) added a comment - - edited

            This is a crucial feature because it directly effects the proper visualization of Burn-down and Burn-up graphics. Currently it estimated the ideal burn-up or burn-down trend by ignoring the day is a working day or not. Hence it misleads the reader if the sprint is going OK or not? I believe this is one of the core functions of such a tool!

            It is quite discouraging to see no action on this important deficiency on Jira Next Gen. 

            Deleted Account (Inactive) added a comment - - edited This is a crucial feature because it directly effects the proper visualization of Burn-down and Burn-up graphics. Currently it estimated the ideal burn-up or burn-down trend by ignoring the day is a working day or not. Hence it misleads the reader if the sprint is going OK or not? I believe this is one of the core functions of such a tool! It is quite discouraging to see no action on this important deficiency on Jira Next Gen. 

            Infrastructure Solutions added a comment -

            It's because they don't care!  People started using Jira because it sucked less then other tools on the market at the time, and now they're banking on the fact that people won't invest the time to move to a new platform and retrain their users.

            Next-gen boards are incorrectly advertised as a stepping stone forwards, when it's a long slide down a rocky hill backwards in terms of functionality.  They took something that was good enough, the Classic Boards, and made an incomplete and functional destroyed monster, which is in late stage Alpha / early Beta at best.  They want to close / break up this ticket because it's clear how bad the steps have been and it's now easy to find this ticket from search engines, which hurt the migration.

            If they had any back bone or integrity they'd own up to this disgraceful and embarrassing mess.  A single developer could have resolved the issue by now, which means either they're no supporting it, or I don't know what else to think.

            Infrastructure Solutions added a comment - It's because they don't care!  People started using Jira because it sucked less then other tools on the market at the time, and now they're banking on the fact that people won't invest the time to move to a new platform and retrain their users. Next-gen boards are incorrectly advertised as a stepping stone forwards, when it's a long slide down a rocky hill backwards in terms of functionality.  They took something that was good enough, the Classic Boards, and made an incomplete and functional destroyed monster, which is in late stage Alpha / early Beta at best.  They want to close / break up this ticket because it's clear how bad the steps have been and it's now easy to find this ticket from search engines, which hurt the migration. If they had any back bone or integrity they'd own up to this disgraceful and embarrassing mess.  A single developer could have resolved the issue by now, which means either they're no supporting it, or I don't know what else to think.

            John Worrall added a comment -

            This is very frustrating.  This ticket was opened two years ago, and last month you guys decided it needed to be broken down into smaller pieces?

            Some of this stuff is really fundamental, must-have functionality.  You need to be able to see if a card has been stagnant without opening it up and looking through history.  You need to be able to decide what fields you want to see on the board and in the backlog, so that you don't have to spend all your time opening up every single ticket to find out important information.

            How has next-gen been available for such a long time, yet still lacks this super-basic stuff?

            John Worrall added a comment - This is very frustrating.  This ticket was opened two years ago, and last month you guys decided it needed to be broken down into smaller pieces? Some of this stuff is really fundamental, must-have functionality.  You need to be able to see if a card has been stagnant without opening it up and looking through history.  You need to be able to decide what fields you want to see on the board and in the backlog, so that you don't have to spend all your time opening up every single ticket to find out important information. How has next-gen been available for such a long time, yet still lacks this super-basic stuff?

            Anand Kumar Tripathi added a comment -

            I cannot see Board settings on my next gen board. Please help

            Anand Kumar Tripathi added a comment - I cannot see Board settings on my next gen board. Please help

            Jeff Hudson added a comment -

            Thanks so much for your thorough investigation of the comments Emily! We appreciate Atlassian getting the next-gen feature out so quickly initially, and understand that it meant that some features like the ones you listed couldn't be included. That said, I'm really looking forward to some of them being implemented! Especially JSWCLOUD-17336, JSWCLOUD-17277, and JSWCLOUD-17773 for my team personally.

            Jeff Hudson added a comment - Thanks so much for your thorough investigation of the comments Emily! We appreciate Atlassian getting the next-gen feature out so quickly initially, and understand that it meant that some features like the ones you listed couldn't be included. That said, I'm really looking forward to some of them being implemented! Especially  JSWCLOUD-17336 ,  JSWCLOUD-17277 , and  JSWCLOUD-17773  for my team personally.

            Infrastructure Solutions added a comment -

            Don't close this ticket, it's a summary ticket.  When will the changes be done?  Frankly the fact this wasn't part of Next-Gen from the very start is a serious issue.

            Infrastructure Solutions added a comment - Don't close this ticket, it's a summary ticket.  When will the changes be done?  Frankly the fact this wasn't part of Next-Gen from the very start is a serious issue.

            Emily Chan (Inactive) added a comment - - edited
            Atlassian status as of October 2020

            Hello all,

            Thank you very much for voting, watching, and/or commenting on this ticket. We appreciate the huge amount of feedback, not just from customers who came directly to this ticket themselves, but also from customers who reached out to our support teams with questions or problems and were then directed to this ticket.

            “Board settings” is a very broad problem to solve because, by itself, it doesn’t tell us what exactly customers are trying to configure. Hence, we have read through all the comments here and from tickets raised through our support team. We’ve found that there are several different, specific settings that customers would like to configure, but they have been all broadly amalgamated into the term “board settings”. The settings that have been specifically requested from the comments are:

            • the ability to define working days in a project: JSWCLOUD-17773
            • the ability to find out how many days a card has been in a column: JSWCLOUD-20809
            • the ability to use colours to quickly identify cards: JSWCLOUD-17277
            • the ability to choose which labels appear on cards in the board/backlog: JSWCLOUD-17450
            • the ability to choose which fields appear on cards in the board/backlog: JSWCLOUD-17336
            • the ability to create Components in next-gen projects: JSWCLOUD-17601
            • the ability to have multiple boards in a next-gen project: JSWCLOUD-17371
            • the ability to have a board with issues from multiple projects (including issues from next-gen projects): JSWCLOUD-17444
            • the ability to create templates to be used when creating next-gen projects: JSWCLOUD-17982
            • the ability to create a new status without creating a column (coming really soon!): JSWCLOUD-17434
            • the ability to set limits on the number of issues in a column (you can do this now)

            Each of these settings, except the last one, have an existing ticket associated with it. Kindly vote/watch/comment the specific settings that are relevant to you. If you feel the settings you are looking for aren’t listed above, kindly tell us about it. Meanwhile, we will close this ticket.

            Again, thank you for your feedback and patience.

            Cheers,
            Emily Chan
            Atlassian.

            Emily Chan (Inactive) added a comment - - edited Atlassian status as of October 2020 Hello all, Thank you very much for voting, watching, and/or commenting on this ticket. We appreciate the huge amount of feedback, not just from customers who came directly to this ticket themselves, but also from customers who reached out to our support teams with questions or problems and were then directed to this ticket. “Board settings” is a very broad problem to solve because, by itself, it doesn’t tell us what exactly customers are trying to configure. Hence, we have read through all the comments here and from tickets raised through our support team. We’ve found that there are several different, specific settings that customers would like to configure, but they have been all broadly amalgamated into the term “board settings”. The settings that have been specifically requested from the comments are: the ability to define working days in a project: JSWCLOUD-17773 the ability to find out how many days a card has been in a column: JSWCLOUD-20809 the ability to use colours to quickly identify cards: JSWCLOUD-17277 the ability to choose which labels appear on cards in the board/backlog: JSWCLOUD-17450 the ability to choose which fields appear on cards in the board/backlog: JSWCLOUD-17336 the ability to create Components in next-gen projects: JSWCLOUD-17601 the ability to have multiple boards in a next-gen project: JSWCLOUD-17371 the ability to have a board with issues from multiple projects (including issues from next-gen projects): JSWCLOUD-17444 the ability to create templates to be used when creating next-gen projects: JSWCLOUD-17982 the ability to create a new status without creating a column (coming really soon!):  JSWCLOUD-17434 the ability to set limits on the number of issues in a column (you can do this now) Each of these settings, except the last one, have an existing ticket associated with it. Kindly vote/watch/comment the specific settings that are relevant to you. If you feel the settings you are looking for aren’t listed above, kindly tell us about it. Meanwhile, we will close this ticket. Again, thank you for your feedback and patience. Cheers, Emily Chan Atlassian.

              Unassigned Unassigned
              adaluz Angélica Luz
              Votes:
              656 Vote for this issue
              Watchers:
              283 Start watching this issue

                Created:
                Updated:
                Resolved: