> I'd like a really easy way to see all of the tickets I've ever completed.
Can be solved by creating a custom person field called “Developer”. Then you can customize the Status transition for your In Progress status to automatically set that field to the current user or maybe the issue assignee.
For better or worse, Jira is quite powerful and flexible. But it’s not always simple to setup.
We do it the other way (and I’ve always seen it done this way): database change is compatible with current code and new code. So deploy the database change, then deploy the code change. It usually allows you to rollback code changes.
It's incredibly useful for household budgeting purposes. Knowing that, at most, I can expect to pay $xxx per month for a service makes estimating expenses easier.
The service apparently alerts you when you get close the "limit". Which means that if you're disciplined you can cut yourself off or just realize that you need to increase your monthly budget.