Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.5
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-10111Document ViewTheme and theme builder
      KULRICE-14232Regression KewToRulesEngineIntegrationTest.testSimpleKrmsPeopleFlowRules fails
      KULRICE-9905Document theme builder and updates to view theme
      KULRICE-8626Document theme images
      KULRICE-8879Themeing Support
      KULRICE-7273Regression Test issues found testing for 2.2 m1
      KULRICE-13097CI AFT Regression Rerun
      KULRICE-12567Setup 2.5 CI Jobs
      KULRICE-10426Theme builder requires copy to temp directory
      KULRICE-14074Manually merge Rice 2.5 to trunk
    • Epic Link:
    • Rice Module:
      KRAD
    • Application Requirement:
      KC
    • Sprint:
      2.5.0-m3 Sprint 2, 2.5.0-m4 Sprint 1, UXI 2.5.0-m4 Sprint 2, UXI 2.5.0-m6 Sprint 1, UXI 2.5.0-m6 Sprint 2
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes
    • Story Points:
      0

      Description

      Attempting to upgrade to Rice 2.5 and there have been regressions to the theme. See attachment for details.

        Issue Links

          Activity

          Hide
          Tom Clark added a comment -

          Regarding the 'styling issues' screenshot, KRAD is rendering some extra style classes that are interfering with the design. Specifically:

          • The <label> tag inside of the right content area is rendering a 'clearfix' class. This needs to be removed.
          • The 'more info' dropdown table has a class of 'uif-table-fixed'. This needs to be removed.
          • The application build info shown in the screenshot should be rendered in a new component that we've designed for this. See KULRICE-13038

          In general, the doc header should be rebuilt to utilize bootstrap responsive classes/layouts, etc. The current uif classes aren't responsive.

          Show
          Tom Clark added a comment - Regarding the 'styling issues' screenshot, KRAD is rendering some extra style classes that are interfering with the design. Specifically: The <label> tag inside of the right content area is rendering a 'clearfix' class. This needs to be removed. The 'more info' dropdown table has a class of 'uif-table-fixed'. This needs to be removed. The application build info shown in the screenshot should be rendered in a new component that we've designed for this. See KULRICE-13038 In general, the doc header should be rebuilt to utilize bootstrap responsive classes/layouts, etc. The current uif classes aren't responsive.
          Hide
          Tom Clark added a comment - - edited

          Regarding the 'cramped modal' screen capture, the KRAD sample app library renders completely different (and corrrect) styling:

          http://env14.rice.kuali.org/kr-krad/dialog?viewId=Demo-DialogGroupView

          I'm not sure why this styling isn't being used in the KC implementation.

          Show
          Tom Clark added a comment - - edited Regarding the 'cramped modal' screen capture, the KRAD sample app library renders completely different (and corrrect) styling: http://env14.rice.kuali.org/kr-krad/dialog?viewId=Demo-DialogGroupView I'm not sure why this styling isn't being used in the KC implementation.
          Hide
          Tom Clark added a comment -

          Resolving this one for now, since the actionable items are outside of UXI. Please reopen if there's additional help that UXI can provide on this one.

          Show
          Tom Clark added a comment - Resolving this one for now, since the actionable items are outside of UXI. Please reopen if there's additional help that UXI can provide on this one.
          Hide
          Jerry Neal (Inactive) added a comment -

          Hi Tom,

          I was talking with Christie and my understand was subtasks would be created in the UXI project. Then you would close the subtask, and then we would resolve the kulrice task. So if there are additional things we need to do in Rice we can account for those after the UXI work has been done.

          Does that work for you? Since you have done the UXI part on this one, we can just reopen and assign to a developer.

          Jerry

          Show
          Jerry Neal (Inactive) added a comment - Hi Tom, I was talking with Christie and my understand was subtasks would be created in the UXI project. Then you would close the subtask, and then we would resolve the kulrice task. So if there are additional things we need to do in Rice we can account for those after the UXI work has been done. Does that work for you? Since you have done the UXI part on this one, we can just reopen and assign to a developer. Jerry
          Hide
          Tom Clark added a comment -

          Sounds good - I'll reopen and mark it as unassigned.

          Show
          Tom Clark added a comment - Sounds good - I'll reopen and mark it as unassigned.

            People

            • Assignee:
              Tadas Paegle (Inactive)
              Reporter:
              Douglas Pace
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile

                  Structure Helper Panel