Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODKBEKBJ-674

...

I suggest to remove providers, packages, titles, resources tables. Because we already have record_id and record_type columns in tags table.
One addition is to include credentials_id column to tags


Code Refactoring:

We use a lot of joins to retrieve records by tags. But now we can retrieve records from one table.

...

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMSEARCH-429

We use a lot of joins to retrieve records by tags. But now we can retrieve records from one table.

  • Write databaseChangeLog script to edit database structure
  • Delete repositories related removed tables PackageRepository, ResourceRepository, TitleRepository, ProviderRepository
  • Implement logic in TagsRepository to retrieve records from tags table by TagFilter
  • Unit tests refactoring¬†

Changes advantages:

  • Remove unused data, simplify database structure
  • Get rid of code duplications, so searching by tag logic will be in the one class. Instead of 4 same classes
  • Will stop using SQL Joiners to improve module response time when searching by tags.

...