Uploaded image for project: 'JIRA Agile'
  1. JIRA Agile
  2. GHS-3922

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

    Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

    • Current Status:
      Hide
      Atlassian Status as at Sept 8th 2014

      Thank you for following this issue.
      We will first address requests which require additional fields to be shown on the cards. I'll outline the solution with some examples of the designs.

      Configuration
      Card Layout will allow the configuration per board of up to 3 additional fields (custom and/or system) to be added to the cards in each mode (plan and work). Independent selections for plan mode and work mode will allow for better customisation and needs due to the different contexts required in each mode.

      Plan mode
      Additional fields will appear on the card below the normal fields. There are no labels for the fields, hovering over the value will show the label/key and its full value, helpful in case of truncation with long values or when displayed in narrow spaces.

      As today, when a combination of narrow viewport width or having multiple panels open (detail view, epic panel, versions panel) the cards are responsive and change to a different layout. Here we see the avatar, estimate statistic and any epic or version lozenge move to a second line. This allows more of the summary to be read. The additional fields move to a third line.

      Note this only happens for narrow widths and is designed to best display the fields on the cards. Closing additional panels or widening the viewport would see the card move to the wider design which uses 2 lines.

      Work mode
      Additional fields will appear on the card below the normal fields.
      Hovering over the value will show the label/key and its full value, helpful in case of truncation with long values or when displayed in narrow spaces.

      As today, when a combination of narrow viewport width or multiple columns or the detail view being open, the cards are responsive and change to a different layout. Here we see the avatar and font reduce in size. This allows more of the summary to be read.

      Note this only happens for narrow widths and is designed to best display the fields on the cards. Closing the detail view or widening the viewport would see the card move to the wider design.

      We are prioritising getting the additional fields onto the cards in a uniform design as shown above. As can be seen in the designs above the additional fields will be rendered as text fields. We will then track any requests and feedback for fields to be displayed in a different format separately i.e. showing a label in a label ‘capsule’.

      We expect that this will fulfil the majority of requests on this issue. This work is now done and so this issue has been resolved.

      Requests that are not fulfilled by this solution will be tracked elsewhere in separate issues so we can understand better the use-cases and needs for each of them.
      Related issues include:

      There are no plans to make the fields on the cards editable inline, the detail view (panel on the right which opens with more fields and can be configured) will be improved to serve this purpose better. Currently, only some of the fields are editable and the intention is to make all valid editable fields in the detail view editable by those with the correct permissions. Please follow this issue for progress: https://jira.atlassian.com/browse/GHS-7893

      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 Sept 8th 2014 Thank you for following this issue. We will first address requests which require additional fields to be shown on the cards. I'll outline the solution with some examples of the designs. Configuration Card Layout will allow the configuration per board of up to 3 additional fields (custom and/or system) to be added to the cards in each mode (plan and work). Independent selections for plan mode and work mode will allow for better customisation and needs due to the different contexts required in each mode. Plan mode Additional fields will appear on the card below the normal fields. There are no labels for the fields, hovering over the value will show the label/key and its full value, helpful in case of truncation with long values or when displayed in narrow spaces. As today, when a combination of narrow viewport width or having multiple panels open (detail view, epic panel, versions panel) the cards are responsive and change to a different layout. Here we see the avatar, estimate statistic and any epic or version lozenge move to a second line. This allows more of the summary to be read. The additional fields move to a third line. Note this only happens for narrow widths and is designed to best display the fields on the cards. Closing additional panels or widening the viewport would see the card move to the wider design which uses 2 lines. Work mode Additional fields will appear on the card below the normal fields. Hovering over the value will show the label/key and its full value, helpful in case of truncation with long values or when displayed in narrow spaces. As today, when a combination of narrow viewport width or multiple columns or the detail view being open, the cards are responsive and change to a different layout. Here we see the avatar and font reduce in size. This allows more of the summary to be read. Note this only happens for narrow widths and is designed to best display the fields on the cards. Closing the detail view or widening the viewport would see the card move to the wider design. We are prioritising getting the additional fields onto the cards in a uniform design as shown above. As can be seen in the designs above the additional fields will be rendered as text fields. We will then track any requests and feedback for fields to be displayed in a different format separately i.e. showing a label in a label ‘capsule’. We expect that this will fulfil the majority of requests on this issue. This work is now done and so this issue has been resolved. Requests that are not fulfilled by this solution will be tracked elsewhere in separate issues so we can understand better the use-cases and needs for each of them. Related issues include: A way to show if an issue is assigned in plan mode. https://jira.atlassian.com/browse/GHS-10604 This will be addressed shortly, the design can be seen in the examples above. An option to show the assignee name instead of the avatar. https://jira.atlassian.com/browse/GHS-7879 Until this is addressed a workaround will be to add the assignee name as one of the custom fields to the card as described above. 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 There are no plans to make the fields on the cards editable inline, the detail view (panel on the right which opens with more fields and can be configured) will be improved to serve this purpose better. Currently, only some of the fields are editable and the intention is to make all valid editable fields in the detail view editable by those with the correct permissions. Please follow this issue for progress: https://jira.atlassian.com/browse/GHS-7893 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

      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. plan-narrow.png
        28 kB
      8. plan-normal.png
        29 kB
      9. rapid board suggestion.png
        98 kB
      10. RapidPlanningBoard.png
        133 kB
      11. sample.jpg
        18 kB
      12. screenshot-1.jpg
        53 kB
      13. screenshot-2.jpg
        16 kB
      14. showing_time.png
        7 kB
      15. work-narrow.png
        17 kB
      16. work-normal.png
        36 kB

        Issue Links

          Activity

          Hide
          mjopson Martin Jopson [Atlassian] added a comment -

          Shiyuan Lin, JIRA Agile 6.6 is already released, please see:
          https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.6+Release+Notes
          http://blogs.atlassian.com/2014/09/jira-agile-6-6-now-available/

          Antony Galdi, Could you please create a support ticket at https://support.atlassian.com
          That way we can provide you with support specific to your circumstances and with higher security.

          Regards,
          Martin
          JIRA Agile

          Show
          mjopson Martin Jopson [Atlassian] added a comment - Shiyuan Lin , JIRA Agile 6.6 is already released, please see: https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.6+Release+Notes http://blogs.atlassian.com/2014/09/jira-agile-6-6-now-available/ Antony Galdi , Could you please create a support ticket at https://support.atlassian.com That way we can provide you with support specific to your circumstances and with higher security. Regards, Martin JIRA Agile
          Hide
          gulhaq Gulfam Amin ul Haq added a comment -

          When the fields are blank the text 'none' is shown which is more distracting. is there a way to have it as blank or would that be a FR

          Show
          gulhaq Gulfam Amin ul Haq added a comment - When the fields are blank the text 'none' is shown which is more distracting. is there a way to have it as blank or would that be a FR
          Hide
          robertbergs Robert Bergs added a comment -

          As a workaround, blank fields have an extra CSS class (ghx-fa), so you can hide them with some custom CSS:

          .ghx-issue .ghx-extra-fields .ghx-fa {
              display: none;
          }
          

          It is hacky, but you can inject this CSS into the banner.

          Show
          robertbergs Robert Bergs added a comment - As a workaround, blank fields have an extra CSS class (ghx-fa), so you can hide them with some custom CSS: .ghx-issue .ghx-extra-fields .ghx-fa { display: none; } It is hacky, but you can inject this CSS into the banner.
          Hide
          asgeir Ásgeir Halldórsson added a comment -

          Where do you add that css hack?

          Show
          asgeir Ásgeir Halldórsson added a comment - Where do you add that css hack?
          Show
          robertbergs Robert Bergs added a comment - See: https://answers.atlassian.com/questions/54624/customize-jira-with-my-own-css

            People

            • Assignee:
              mjopson Martin Jopson [Atlassian]
              Reporter:
              dfischer David [Innovalog]
            • Votes:
              824 Vote for this issue
              Watchers:
              562 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: