Recurring expenses should generate expense content so they can be used the same way.
Smart Date has a way to edit instances, but I don't think it's enough if the expense amount varies (like an electric bill).
Recurring expenses should generate expense content so they can be used the same way.
Smart Date has a way to edit instances, but I don't think it's enough if the expense amount varies (like an electric bill).
Receipts need to be filed in order to deduct an expense.
A document with record of payment needs to be stored securely and retrieved easily.
Some expenses are recurring, like a monthly internet bill.
Smart Date provides a recurring date field, with instances that can be used in Views.
I added an Issue module field to issues and need to move the previous Modules field data into it.
I added the related modules field to Issue and manually cleaned up issues with multiple values.
Bookmark is a multivalue field, but should be called Bookmarks according to the naming convention.
An account may need to share data with multiple users.
If content is in a group, it can be hidden to outside users.
Freelancers or teams can a group with optional subgroups.
Each client can have a group to see their invoices.
Goals and objectives have periods in which we try to meet the target.
At the end of the period, we should reflect on our progress, evaluate how we did, and decide what to do next.
The deadline field was created with date and time, so the form shows the time field.
This isn't needed, so replace the field with a regular date and fix the values.
This may require a data migration.
A module tag might make more sense than a boolean field, since it's similar to extension/utility...
Stability might make more sense, as core is one level above secure.