Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-3922

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

XMLWordPrintable

    • 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

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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. screenshot-1.jpg
          screenshot-1.jpg
          53 kB
        2. Advanced-cards.jpg
          Advanced-cards.jpg
          13 kB
        3. RapidIssueEntry.class
          2 kB
        4. RapidIssueEntryFactory.class
          6 kB
        5. Capture.PNG
          Capture.PNG
          49 kB
        6. rapid board suggestion.png
          rapid board suggestion.png
          98 kB
        7. RapidPlanningBoard.png
          RapidPlanningBoard.png
          133 kB
        8. download.png
          download.png
          175 kB
        9. Epics.png
          Epics.png
          513 kB
        10. No_time.png
          No_time.png
          42 kB
        11. showing_time.png
          showing_time.png
          7 kB
        12. screenshot-2.jpg
          screenshot-2.jpg
          16 kB
        13. card-layout-config.png
          card-layout-config.png
          47 kB
        14. plan-narrow.png
          plan-narrow.png
          28 kB
        15. plan-normal.png
          plan-normal.png
          29 kB
        16. work-narrow.png
          work-narrow.png
          17 kB
        17. work-normal.png
          work-normal.png
          36 kB
        18. sample.jpg
          sample.jpg
          18 kB

              mjopson Martin (Inactive)
              94298a523126 David Fischer
              Votes:
              824 Vote for this issue
              Watchers:
              544 Start watching this issue

                Created:
                Updated:
                Resolved: