You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ stage_model ]
company_id
name
id
-> projects (one to many join)
On migration create one model per company with name "default".
[ stage ]
company_id
id
name
sort
-> stage_model (many to many join so they can be reused for several workflows)
On migration look for a task property called "status", "state" or "stage" (in that order). Then create new stage records for each property_value. Join this to stage stage_model 'default' created above. Remember this is one set of records per company (tenant).
If there is no task property to migrate, then make a new set like this:
Review
In progress
Testing
Documentation
This new default set should also be created whenever a user creates a new company (tenant) or initialises a whole new database.
Add a new relationship to task:
[ task ]
-> current_stage
And finish the migration by copying over the existing propery-task joins to this new entity.
Finally, migrate over all the existing UI to the new schema. This involves adding the new entry field to:
task list view (including the dropdown of configurable columns)
task edit view (under the attributes section)
billing page (as an option to group on for pivot reports)
task search UI
Then finally delete the old custom attrbute from the database once the migration is done and successful.
The text was updated successfully, but these errors were encountered:
https://github.com/ari/jobsworth/wiki/Stage
Make the following new schema...
On migration create one model per company with name "default".
On migration look for a task property called "status", "state" or "stage" (in that order). Then create new stage records for each property_value. Join this to stage stage_model 'default' created above. Remember this is one set of records per company (tenant).
If there is no task property to migrate, then make a new set like this:
This new default set should also be created whenever a user creates a new company (tenant) or initialises a whole new database.
Add a new relationship to task:
And finish the migration by copying over the existing propery-task joins to this new entity.
Finally, migrate over all the existing UI to the new schema. This involves adding the new entry field to:
Then finally delete the old custom attrbute from the database once the migration is done and successful.
The text was updated successfully, but these errors were encountered: