Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Promote status to stage #634

Open
ari opened this issue Jul 4, 2016 · 2 comments
Open

Promote status to stage #634

ari opened this issue Jul 4, 2016 · 2 comments
Assignees
Labels
Milestone

Comments

@ari
Copy link
Owner

ari commented Jul 4, 2016

https://github.com/ari/jobsworth/wiki/Stage

Make the following new schema...

[ 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.

@ari ari added the feature label Jul 4, 2016
@ari ari added this to the 5.0 milestone Jul 4, 2016
@ari ari assigned k41n Jul 4, 2016
@ari
Copy link
Owner Author

ari commented Jul 4, 2016

The above is just stage one: to migrate the existing field and pave the way for future new work.

@ari
Copy link
Owner Author

ari commented Jul 4, 2016

Oh, and I'm aware that at the end of this task we will no longer have a UI to edit the stages.

@ari ari modified the milestones: 5.0, 5.1 Jul 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants