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

Better view to track an orgs progress #183

Open
pkoenig10 opened this issue Apr 13, 2016 · 3 comments
Open

Better view to track an orgs progress #183

pkoenig10 opened this issue Apr 13, 2016 · 3 comments

Comments

@pkoenig10
Copy link
Member

Something like a chart for each org. Unfortunately as Binder is now, this would require some hardcoding to the organization_status_entries. We will need to come up with a more creative solution. Maybe have a field in each organization_status_entry_type to indicate which step it is in the review process.

@purelogiq
Copy link
Member

From meeting

For each org status type, add type and a order number.
If an org status type has an order number, it is part of a process that has order
(e.g. first floor, first floor walls)
Any that has an order, show in order on a chart.

@ChaseBro
Copy link
Member

There was some work done for statuses to show on the Org index page, not
sure what happened to it, but there was supposed to be a boolean for each
status type that said whether or not to have it display on the index, then
you can set it to true for stuff like inspections and false for random
things and the Org Index page would just show the latest status for each
org. A chart is much nicer, but I wouldn't put in explicit orders, I would
just assume that there are multiple classes of statuses and some of them
should show on such a chart in chronological order or whatever.

The possible exception would be if you want to have a fixed output to see
stats such as "what percentage of booths have 1st floor leveling approved"
in which case having an order for those items would be nice, although even
there you could just say order them by completion percentages or something
similar. Just also make sure that it's ok if an org does things out of
order, even if there's a warning message or something.

On Mon, Apr 18, 2016 at 4:01 PM Israel Madueme [email protected]
wrote:

From meeting

For each org status type, add type and a order number.
If an org status type has an order number, it is part of a process that
has order
(e.g. first floor, first floor walls)
Any that has an order, show in order on a chart.


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#183 (comment)

@pkoenig10
Copy link
Member Author

The ordering isn't really to enforce a process for building, it more for organizing the view for booth committee who will be looking at it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants