JIRA Agile (formerly GreenHopper)
  1. JIRA Agile (formerly GreenHopper)
  2. GHS-3922

As a user, I would like to configure the cards displayed in the rapid board

    Details

    • Current Status:
      Hide
      Atlassian Status as at April 15th 2014

      The requests on this issue have been analysed and we will begin to tackle them in a number of increments.

      "First initial” avatars, shipped in version 6.3.11, delivered improved work mode cards helping with the identification of assignees in work mode. https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.11+Release+Notes

      The remaining requests on this issue fall into two broad categories.

      1. The first of these we’ll deliver as "Custom Card Layout”. This will allow the configuration per board of a number of custom fields to be added to the cards.
      Independent selections for plan mode and work mode will allow for better customisation and needs due to the different contexts required in each mode.

      A mockup of how this configuration may appear:

      The final designs for the cards are still in progress, in work mode the additional fields are likely to be added as key/value pairs below the current contents of the card.
      Your feedback on this feature is welcome, please add a comment if this will satisfy your requirements. We expect that this will fulfil the majority of requests on this issue. When this work is done this issue will be resolved.

      This issue is next on the roadmap and the JIRA Agile team will begin implementation once current commitments are completed. A further update will be given as work begins.

      2. The remainder of the requests will be tracked in individual issues based on their use-cases. These are listed below and further additions will be added as linked issues.

      A number of configuration options will be made available to address popular requests, these are still being analysed and design’s explored but are likely to include:

      Please follow these individual issues for further updates.

      If you do not see your requirements listed in one of the stories above, or in an existing story in this project, please add a comment below. Your feedback on these issues is welcomed.

      Kind regards,
      Martin Jopson
      JIRA Agile team

      Show
      Atlassian Status as at April 15th 2014 The requests on this issue have been analysed and we will begin to tackle them in a number of increments. "First initial” avatars, shipped in version 6.3.11, delivered improved work mode cards helping with the identification of assignees in work mode. https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.11+Release+Notes The remaining requests on this issue fall into two broad categories. 1. The first of these we’ll deliver as "Custom Card Layout”. This will allow the configuration per board of a number of custom fields to be added to the cards. Independent selections for plan mode and work mode will allow for better customisation and needs due to the different contexts required in each mode. A mockup of how this configuration may appear: The final designs for the cards are still in progress, in work mode the additional fields are likely to be added as key/value pairs below the current contents of the card. Your feedback on this feature is welcome, please add a comment if this will satisfy your requirements. We expect that this will fulfil the majority of requests on this issue. When this work is done this issue will be resolved. This issue is next on the roadmap and the JIRA Agile team will begin implementation once current commitments are completed. A further update will be given as work begins. 2. The remainder of the requests will be tracked in individual issues based on their use-cases. These are listed below and further additions will be added as linked issues. A number of configuration options will be made available to address popular requests, these are still being analysed and design’s explored but are likely to include: An option to show the assignee name instead of the avatar. https://jira.atlassian.com/browse/GHS-7879 A way to show if an issue is assigned in plan mode. https://jira.atlassian.com/browse/GHS-10604 Options to hide the version and epic labels in plan mode. https://jira.atlassian.com/browse/GHS-8444 An option to show an additional statistic on the card in plan mode. https://jira.atlassian.com/browse/GHS-10605 An option to show both the original and remaining estimate on the card in work mode when using time-tracking https://jira.atlassian.com/browse/GHS-10606 Please follow these individual issues for further updates. If you do not see your requirements listed in one of the stories above, or in an existing story in this project, please add a comment below. Your feedback on these issues is welcomed. Kind regards, Martin Jopson JIRA Agile team
    • Last commented by user?:
      true

      Description

      It would be nice to be able to modify the fields that are displayed in the cards on the RapidBoard, just like you can for the Planing and Task boards.
      In particular, it would be nice to be able to show the name of the assignee in addition of their avatar

      Please Note

      This issue relates to configuring the layout of the card on the Rapid Board. If you are instead interested in configuring the fields shown in the detail view that pops up when you click on an issue in the Rapid Board, please see GHS-3474 - As a Rapid Board user I would like to configure the detail view for an issue


      Latest update by Tom can be found at here

      1. RapidIssueEntry.class
        2 kB
        Holger Schimanski
      2. RapidIssueEntryFactory.class
        6 kB
        Holger Schimanski
      1. Advanced-cards.jpg
        13 kB
      2. Capture.PNG
        49 kB
      3. card-layout-config.png
        47 kB
      4. download.png
        175 kB
      5. Epics.png
        513 kB
      6. No_time.png
        42 kB
      7. rapid board suggestion.png
        98 kB
      8. RapidPlanningBoard.png
        133 kB
      9. screenshot-1.jpg
        53 kB
      10. screenshot-2.jpg
        16 kB
      11. showing_time.png
        7 kB

        Issue Links

          Activity

          Hide
          Peter Adolphs added a comment -

          Good to hear that there is progress on this issue!

          You write:

          The final designs for the cards are still in progress, in work mode the additional fields are likely to be added as key/value pairs below the current contents of the card.

          It would be great if the values are not just displayed as plain text but if they would be links where appropriate. For instance, I would like to visualize labels and components on the cards. They should be clickable so that I get to all the issues with that label/component with one click.

          It would also be great if the values would be displayed with a color where appropriate. I would like to add Epic links to the cards in my Kanban boards. Epics are so far only fully supported in Scrum boards. There, they are clickable and are displayed with a specific color, so it's easier to visually scan which issues belong together. I think the coloring of values would be a handy feature for all values with a limited set of possible values, such as Epics, components or labels.

          Show
          Peter Adolphs added a comment - Good to hear that there is progress on this issue! You write: The final designs for the cards are still in progress, in work mode the additional fields are likely to be added as key/value pairs below the current contents of the card. It would be great if the values are not just displayed as plain text but if they would be links where appropriate. For instance, I would like to visualize labels and components on the cards. They should be clickable so that I get to all the issues with that label/component with one click. It would also be great if the values would be displayed with a color where appropriate. I would like to add Epic links to the cards in my Kanban boards. Epics are so far only fully supported in Scrum boards. There, they are clickable and are displayed with a specific color, so it's easier to visually scan which issues belong together. I think the coloring of values would be a handy feature for all values with a limited set of possible values, such as Epics, components or labels.
          Hide
          Rainer Mueck added a comment -

          You wrote: "The final designs for the cards are still in progress, in work mode the additional fields are likely to be added as key/value pairs below the current contents of the card."

          Could you please add a mockup for this as well? I'm a bit concerned, that a repeated display of the field names per card could take too much of the screen space - resulting in less total number of cards.

          Many thanks in advance.

          Show
          Rainer Mueck added a comment - You wrote: "The final designs for the cards are still in progress, in work mode the additional fields are likely to be added as key/value pairs below the current contents of the card." Could you please add a mockup for this as well? I'm a bit concerned, that a repeated display of the field names per card could take too much of the screen space - resulting in less total number of cards. Many thanks in advance.
          Hide
          Hans-Jürgen Tappe added a comment - - edited

          I believe that a key/value pair is not what we as customers expect. My team expects exactly the same highly usable layout as in the classic boards, namely:

          • Only the values are displayed
          • The tooltip explains what is behind
          • a double-click allows inline editing

          Nothing more than what we had before the rapid boards...

          I am not in the position to question your internal design but from my SW engineering understanding, it should be feasible to use the same widgets for the inline editable fields at multiple places, depending on the field type. I cannot see a blocking point to make things worse (i.e. add yet another field and then wait for us users to complain that it should be inline editable as we were used to).

          Show
          Hans-Jürgen Tappe added a comment - - edited I believe that a key/value pair is not what we as customers expect. My team expects exactly the same highly usable layout as in the classic boards, namely: Only the values are displayed The tooltip explains what is behind a double-click allows inline editing Nothing more than what we had before the rapid boards... I am not in the position to question your internal design but from my SW engineering understanding, it should be feasible to use the same widgets for the inline editable fields at multiple places, depending on the field type. I cannot see a blocking point to make things worse (i.e. add yet another field and then wait for us users to complain that it should be inline editable as we were used to).
          Hide
          Rainer Mueck added a comment -

          100% support from my side for this statement.

          Show
          Rainer Mueck added a comment - 100% support from my side for this statement.
          Hide
          Moriah Chandler added a comment -

          Yes, we want what we had before the rapid boards. The rapid boards have caused so many headaches for everyone, and have put JIRA administrators in the unenviable position of explaining to our users why Atlassian chose to remove functionality that everyone used (and loved.) This goes against one of your basic tenets (Don't $^%& the customer!) and has been the bane of my existence since I championed your products and switched everyone in our company over to them.

          Show
          Moriah Chandler added a comment - Yes, we want what we had before the rapid boards. The rapid boards have caused so many headaches for everyone, and have put JIRA administrators in the unenviable position of explaining to our users why Atlassian chose to remove functionality that everyone used (and loved.) This goes against one of your basic tenets (Don't $^%& the customer!) and has been the bane of my existence since I championed your products and switched everyone in our company over to them.

            People

            • Votes:
              630 Vote for this issue
              Watchers:
              420 Start watching this issue

              Dates

              • Created:
                Updated:
                Last commented:
                1 day ago