• 11
    • 15
    • Hide
      Atlassian Update – 20 March 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. 

      We 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 – 20 March 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.  We 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.

      As PjM, I'd like to customise panels in plan mode so that I can add and display necessary links/tags easily during meetings.

      Currently, there are only Versions and Epics on the panel. It would be nice if I could customise them by adding any fields I need.

      In my team, we want to quickly add and display Epics and Components during meetings. Referring the links/tag on the plan mode, it helps to skim all stories in the backlog without opening details views or use "Search issues" feature, and quickly identify a story we are looking for.

            [JSWSERVER-9554] Customisable panels in Agile Backlog

            +1

            +1 need components

            Sergey Andreev added a comment - +1 need components

            +1 need components and labels here at Trimble.  Jira missing a  concept between story/issue and epic that can be actioned via drag-drop.

            tom_kluyskens added a comment - +1 need components and labels here at Trimble.  Jira missing a  concept between story/issue and epic that can be actioned via drag-drop.

            would have been great to use this feature, please make this happen

            Rishabh Talim added a comment - would have been great to use this feature, please make this happen

            avrahamr added a comment -

            This would be great that we can use any field to add panels to the dashboard, and also in some project we would like to remove the versions panel, since it only slows us down.

            avrahamr added a comment - This would be great that we can use any field to add panels to the dashboard, and also in some project we would like to remove the versions panel, since it only slows us down.

            Jacob Ma added a comment -

            +1

            Jacob Ma added a comment - +1

            +1

            +1 Please make this happen for components. It's far more useful than epics considering you can assign multiple values.

            ahmed.elmorsy added a comment - +1 Please make this happen for components. It's far more useful than epics considering you can assign multiple values.

            Tom Pitts added a comment - - edited

            +1 for components or an easier way of grouping the backlog by component

            Tom Pitts added a comment - - edited +1 for components or an easier way of grouping the backlog by component

            I would like to see a list of things that were added since 2018. When I google for some very basic UI related topics, I discover often, that tickets are very old (2014 ... 16... 18) and things are NOT SOLVED. Which are mandatory. Or at least (if Atlassian see this different) shall be customizable easily. Like in this case to see the components. Fully don't understand, what Atlassian is doing there ...

            Alexander Karch added a comment - I would like to see a list of things that were added since 2018. When I google for some very basic UI related topics, I discover often, that tickets are very old (2014 ... 16... 18) and things are NOT SOLVED. Which are mandatory. Or at least (if Atlassian see this different) shall be customizable easily. Like in this case to see the components. Fully don't understand, what Atlassian is doing there ...

              Unassigned Unassigned
              5790d2363eb5 Miki Yuzawa
              Votes:
              629 Vote for this issue
              Watchers:
              278 Start watching this issue

                Created:
                Updated: