...

Specialty Groups whilst still present in the TIS application as of 20 Jun 2018 are scheduled to be retired -

Categorising with Specialties

...

• Curricula can have a single Specialty
• Curricula Specialty dropdown contents limited to Specialties with SpecialtyType of Curricula and status 'Current' <not implemented by TIS currently> currently> 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TISDEV-5007

Posts

TIS allows a Post to be categorised with a Specialty in 3 ways as can be seen on the Posts UI below, these are defined as Primary Specialty, Other Specialty and Sub-Specialty. 

• Posts can only have a single Primary Speciality
• Primary Specialty dropdown contents limited to Specialties with SpecialtyType of Post and status 'Current' <'Current' is implemented in TIS but SpecialtyType of Post isn't at present> present> 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TISDEV-5008

• Posts can have multiple Other Specialties (chosen from Specialties with SpecialtyType of Post)
• Other Specialties dropdown contents limited to Specialties with SpecialtyType of Posts and status 'Current' <'Current' is implemented in TIS but SpecialtyType of Post isn't at present> present> 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TISDEV-5008

• Posts can have multiple Sub-Specialties (chosen from Specialties with SpecialtyType of Sub-Specialty) <'Current' is implemented in TIS but SpecialtyType of Sub-Specialty isn't at present> present> 

  Jira Legacy
  server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status serverId 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 key TISDEV-5008

These relationships are all stored in a TCS table called PostSpecialty as seen below using a PostSpecialtyType:

...