Yithro

TicketStructure
Add another field for scope (user or org)?

-name
-description
-structure (json)
  -fields available
    -field options available (based on conditions?)
  -conditional fields
  {
    TicketFields: [
      {
        ticketFieldId: 1111,
        name: envOS,
        validationRules: xxx,
        displayRules: yyy,
        phase: 1
      },
      {
        ticketFieldId: 1111,
        name: envOS,
        validationRules: xxx,
        displayRules: yyy,
        phase: 1
        options: [
          {
            optionId: 123,
            displayRules: zzz
          },
          {
            optionId: 456,
            displayRules: alwaysShow
          }
        ]
      }
    ]
  }
      



-Permissions
  -Liferay
    -Add Ticket
    -View
    -Add Comment
    -Delete
      -Yithro sub-permissions
        -3 tiers/visibilities
          -Customer
          -Worker
          -Admin
          -None
        -viewableBy
        -specific fields updatableBy


Ticket
-Friendly URLs (servlet that routes to a portlet?)
-Search
-Dashboard

Support
-Add SLAs
  -osgi extendable
-Routing (use Rules?)

Rules
-Business Rules
  -Triggers (object created/updated/deleted)
  -Conditions
  -Actions
  -Timed Events

Extensions
-Project based tickets (org connector)
-Offering based tickets (offering connector)  

Done
-Ticket View
  -Comments
  -Links
  -Attachments