Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-3691

Enterprise Contract security tab feedback & UI suggestions

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Developer
    • None
    • False
    • False
    • None

      It's great to be able to play around with the first iteration of the enterprise contract result page! 

      After viewing it in a couple situations, here are some thoughts on possible improvements in the next iteration:

      1. focusing on the rule name, without showing the failure message makes any rule that flags multiple tasks or components hard to tell apart, you just see multiple failures on the same rule name and have to click in to see the task difference (affecting a different component would be obvious since that has a column)
        • Should we consider better aggregation of failures? or is it better to keep them separate, and maybe consider including the task name or failure message so that it is always visible and wouldn't require a user to click in
        • moved to HAC-3842
      2. I'm not sure what the default sort is, none of the columns show a selected sort when the page loads (covered in HAC-3760)
      3. I can only expand a row by clicking on the arrow, it would be nice if the click target was larger. perhaps clicking the rule name could also expand its row? (covered in HAC-3760)
      4. xrefs are displayed in the log output and carried up into this tab, I assume those are embedded links that are coming through from the documentation layout? is there something we could do to make those more useful in this context? 
        • this is on the contract team to consider (fixed in HACBS-2102)
      5. summarizing how many pass/fails/warnings could be beneficial for at a glance digestibility as this scales across rules and multiple components (covered in HAC-3760)
      6. mentioning the policy validated against would be helpful (split to HAC-3842)
      7. there's a typo in the description text - "rego policy langauage"  (created bug HAC-3696)
      8. effective on isn't that useful right now. will it be more helpful in a production setting, or should we look at removing it from the column here, and making room for other information (like the failure message)? (covered in HAC-3760)
      9. the search field should say filter (created bug HAC-3696)
        • maybe this should be similar to the commit list filter field which says "Filter by name..."?

              sbudhwar-1 Sahil Budhwar
              mreid1@redhat.com Matt Reid
              Archiver:
              rhn-support-sthamilt Stacey Hamilton

                Created:
                Updated:
                Resolved:
                Archived: