• Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-6603Term Spec maintenance doc add context
      KULRICE-11819Term Specification maintenance doc not loading related contexts
      KULRICE-5419add description to Context, Term, Term Spec, and KRMS Attribute Definition at DB, BO, model object, builder, and interface layers
      KULRICE-11449in TermSpecification maintenance doc, items added to the Context collection should not be editable
      KULRICE-13956Term Specification maintenance screen "add Contexts" and "add Categories" action lines are non fuctional.
      KULRICE-6971When copying a Term Specification, categories are not copied and you get a validation error when trying to submit on Context
      KULRICE-6364javascript error on adding a line to a collection on a Term Specification
      KULRICE-6652Lock down (add auth check) to Context, Term Specification, and Term maintenance docs
      KULRICE-242Add "context" support to KSB for retrieving services in different environments/locations
      KULRICE-6013SQLException when editing rule if there are no valid terms on a context
    • Rice Module:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      Context maintenance only includes the most basic fields on a Context. Much configuration needs to be done via sql. Minimally, it would be helpful to support managing the terms within a context.


        There are no comments yet on this issue.


          • Assignee:
            Peter Giles (Inactive)
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created:

              Structure Helper Panel