Aluleth Boards Pro – Kanban, Gantt Timeline, Time Tracking and Client Portal for WordPress

Changelog:

= 0.3.9 =
* Timeline, moving the cards that wait for a moved card: each card's new dates are written by one conditional database update, which applies only while the card still has the dates read for the move (and the due-done and reminder settings that change with them) and is still open on the board. A card someone edits while the move runs keeps that edit and is reported as changed, also during a retry round; a card done, archived or moved to another board meanwhile is reported as no longer moved. A moved card still gets the activity line, the reminder change and the automations, webhooks and calendar sync of a date change.
* Timeline: the critical path follows the links until the path ends, however many cards it has (it stopped after 100 before); a loop of links ends the path.

Aluleth Boards Pro 0.3.8
= 0.3.8 =
* Complete plugin: Aluleth Boards 0.7.2 is included (unchanged), nothing else to install.
* Timeline, moving the cards that wait for a moved card: a card counts as moved only when the database, read again after the change, holds its new dates. A card the database did not change is no longer counted as moved: it is kept in the move's list of failed cards, saved with the move, and tried again a little later (after 10 seconds, 1 minute and 5 minutes), also after a stop and when the 5-minute task finishes the move. A card already at its new dates is never moved twice.
* The report at the end tells the cards moved apart from the cards that could not be moved (with their titles), and is shown as a warning when a card was left. While a move waits to try again, the Timeline says so.
* A failed read of the links between cards, or of the cards to move, is no longer taken for "no more cards": the step is tried again a little later, and the move is never reported done with a part of the cards only. After several failed reads in a row the move stops, and the report says what was not done (when the links could not be read, no card is changed).
* The question before a move says "more than" when the cards that wait could not all be read.

Aluleth Boards Pro 0.3.7
= 0.3.7 =
* Complete plugin: Aluleth Boards 0.7.2 is included (unchanged), nothing else to install.
* Timeline: when a card is dragged and the cards that wait for it are moved too, every one of them is moved, however many there are (the earlier limit of about 500 is gone). The move runs a few seconds at a time and is saved after each step: the page shows where it is ("Moving the cards that wait for …: 600 of 1,203 done") and reports it done only once every card that waits has been looked at. If the page is closed, the move goes on with the 5-minute task, and the page shows it when it is opened again.
* The cards that wait are followed through every link, each card once: links that loop back end the walk instead of moving a card twice. A card in the chain without a date is passed through, and the cards after it move. A card whose dates someone else changed during the move is left as it is, and the report says how many. A move stopped halfway goes on where it stopped, without moving any card twice. One move per board at a time.
* The question before the move counts all the cards that wait (or says "more than" for very long chains).

Aluleth Boards Pro 0.3.6
= 0.3.6 =
* Complete plugin: Aluleth Boards 0.7.2 is included (unchanged), nothing else to install.
* "Add a card" in board buttons and scheduled commands: the card is written with the reference of the run and action in the same insert, also when it is made from a card template (whose labels, checklists and fields are then copied step by step, each step noted before it runs). After a stop, the card is looked for by that reference only: no other card of the stage is ever taken for it or renamed. A card made from a template finishes the steps that had not run; a step it can not be sure of (checklists stopped halfway, automations for new cards already starting) is not done twice and is named in the history. A run stopped by an earlier version while it was adding a card from a template is reported in the history (check the stage) without adding the card again or changing any other card.
* "Email each person their cards": each person's open cards are read for that board only, so cards on other boards never take their place, in both ways the command runs. The email lists the first 50 cards (soonest due first), says how many more there are, and links to all of the person's cards on the board.

Aluleth Boards Pro 0.3.5
= 0.3.5 =
* Complete plugin: Aluleth Boards 0.7.2 is included (unchanged), nothing else to install.
* Board buttons and scheduled commands that go through the cards keep their own copy of the automation (actions, their settings and order, conditions) from the moment they start, and use it until they finish, also for the history. Changes saved meanwhile apply from the next run, and the save message says so. A run started by an earlier version goes on only when its automation was not changed since it started; otherwise it stops with a clear line in the history.
* Board actions in those runs are marked before they run: a card added by "Add a card" is found and not added again after a stop, and "Email each person their cards" notes each person before and after their email, so nobody is emailed twice; a person whose email was being sent when the work stopped is named in the history instead of being emailed again.

Aluleth Boards Pro 0.3.4
= 0.3.4 =
* Board buttons and scheduled commands: a card whose action fails (for example an email to the client that can not be sent) is now listed in the history with the card, the action and the reason, and counted apart from the cards that changed. A run where every action failed is "Failed", a run with changes and failures is "Done with errors" (not "Done"). The progress line shows the failures so far.
* A card's action is marked as started before it runs, so if the work stops on that card, the action is not run again on the next try (it is reported on that card instead). Cards already changed are never changed twice.
* Card buttons, tests and rules name the action that failed in the history.

= 0.3.3 =
* The listing description states the included Aluleth Boards version (0.7.2), the minimum version of a separate Aluleth Boards plugin (0.7.2) and the note about updating it before deleting it, as in the readme; it is in English only, with a short Live demo paragraph. No other change.

= 0.3.2 =
* Complete plugin: Aluleth Boards 0.7.2 is included, nothing else to install. If the free Aluleth Boards plugin is already on the site, it is used as before and its boards stay.
* Board-level commands (board buttons and scheduled commands) go through every card of the board: 100 cards at a time, with the progress saved after each card changed, from the last card done. Before, only the first 300 cards were looked at. A command that needs more time goes on in the background (also after a request that stopped, within about 3 minutes) and the history shows it as "Working" until every card was looked at; only then is it "Done", with the number of cards changed and looked at. A second start while a run is still working does nothing. "Archive cards done long ago" and "Move cards due soon" also go through every card.
* Test an automation on any card: by its number, besides the list of the first 200 cards.
* Privacy: erasing a person anonymizes every card made from their emails, 200 cards per step of the WordPress erase tool: the "Sent by email by Name (address)" line becomes "Sent by email (address removed)", so the name goes too. The tool is told "done" only when no such card is left, and a card that could not be saved is reported (run the erasure again) instead of being counted as erased.
* Dashboard: every total, chart and count is worked out in the database over all the cards of the board, whatever is shown. Charts grouped by person, label or field draw their 12 biggest groups and say how many more there are; the table under the chart lists them all.
* Public link of a stage: 200 cards per page with previous and next links (the link's token is kept); counts and the "client cards only" setting are applied in the database.
* Table view: 200 rows per page, group counts and sums over every card. Timeline: every dated card (the critical path uses them all), rows 300 per page, the real number of cards without dates. Map, AI duplicate check and roadmap read every card in batches; roadmap columns get "Show more ideas". Client portal: the work list is paged and the file and date lists say how many more there are. Cross-board reports no longer stop at 5,000 or 20,000 cards.
* When the separate Aluleth Boards plugin is used, it must be 0.7.2 or newer.

Aluleth Boards 0.7.2 (included)
* Big boards: no card is left out of any view any more. The board shows the first 100 cards of each stage with a "Show 100 more (X left)" link (it also works without JavaScript); stage counts come from the database. A card dropped below the last card shown in a stage that is not fully loaded goes right after that card, and the cards not loaded keep their order.
* List view and archived cards are paged (page links, counts of every card). The REST API and the abilities take a page parameter and give the totals (X-WP-Total and X-WP-TotalPages headers).
* Calendar ("No date yet") and board report: the real number of cards, with a link to the full list where a list is cut. The calendar no longer stops at 1,500 cards.