To resolve before first release

[fosterlynn]

Before releasing the alpha to a few key users, here are some minor things I think we need to fix. I'll start with some name display items. Note there are methods that exist in the models that are not exposed on the UI. We could expose them on the UI, or the UI can build its own.

Plan text and Commitment text need to be built if there is not a name or description entered in the data. The first screen is an example of missing plan names.

The next screen is an example of missing commitment descriptions.

The next screen is an example of good names/descriptions because they were entered into the base data. This one is good because it was created from a recipe. If they don't look like this, I think we need to create something ourselves.

The next screen is an example of created commitment names. It would be good to have this info plus the description.

The next screen is an example of created plan names. It is not so good, but at least better than just the id. (The work app in OCP doesn't really give a way to create a plan name in the planning without recipe function. So it isn't helping. In this case, we could take the process name and put it into the plan.)

[bhaugen]

The 4th screenshot (CE Area Facilitation) shows some awkward computed names (duplicated due dates). We can do better. Same for the plans.

[fosterlynn]

The 4th screenshot (CE Area Facilitation) shows some awkward computed names (duplicated due dates). We can do better. Same for the plans.

Ha it certainly does. That's probably in the UI, not the model method though.

I'll create some displayText properties for Plan and Commitment for the UI.