Kanban
Kanban is reserved for the Business tier. It sorts an application's requests into columns, like a board of cards: your team's columns to note and sort ideas, the assistant's to follow each request until it is live. It opens with the “Kanban” button, the first of the application's line on the Applications page, left of “Edit”, or with the “Kanban” tab of its pages.
On a computer screen, the menu folds on arrival on the Kanban (≡ opens it for the visit), and when columns overflow to the right, a shadow on the row’s edge says so.
On this page
Reserved for the Business tier
That button only shows on the application's row for an organisation on the Business tier. On the other tiers, a test version works the same way, shared conversation included, without a board to sort it: you find it on the Applications page. If your organisation leaves that tier while it still has waiting cards, the board stays readable and says so: “Kanban is for the Business tier only. You can still open your cards, abandon them or take them out of the queue.” No card can be added any more, nor can a card be queued to run its plan, and those cards wait for the organisation to return to the Business tier, which is taken on quote (see Subscription). An adjustment requested in the conversation still goes ahead, on every tier.
Two kinds of columns
The dashed columns are your team's: you name them, place them and fill them with cards. The tinted columns, marked with a robot and a padlock, are the assistant's: they cannot be renamed, moved or deleted. Beside each one's name, a badge says whose turn it is (“Your turn” or “The assistant's turn”); under the name, a line says what to do.
The assistant's columns
- In discussion: “clarify the request with the assistant, then approve its plan”. A card the assistant has already answered carries, right of its title, an icon of two bubbles: “Talked with the assistant” on hover.
- Queued: “it takes it as soon as it is free”.
- Being built: “it applies the plan and checks it”.
- To approve: “try the test version, then publish or ask for a change”.
- Live: “Published: tests then going live, about 4 min”.
The number beside the name counts the column's cards.
Waiting cards
A waiting card is an idea noted in a few words, without starting anything. Click “Add a card” at the top of one of your team's columns, then type its title. Enter adds it and keeps the field open for the next one; Shift+Enter adds it and opens it straight away; Escape or the cross close the field. A new card lands at the top of its column.
A click on the card opens its window: its title, and its description, “What to change, and why (optional)”, up to 100,000 characters. The paperclip, “Attach files”, joins images, PDFs, spreadsheets, documents or ZIP archives to it, as to a message: you can also drop them on the description, or paste a screenshot into it, and a pasted text of 4,000 characters or more becomes “pasted-1.txt”. The “Rename” pencil, on hover next to its bin and always on a phone, opens the same window to change its title. The “Rename” pencil, on hover next to its bin and always on a phone, opens the same window to change its title. “Save” keeps your edits, “Delete” removes the card after a confirmation. A card with a description or attached files shows a small icon. To change the order, drag a card to the place you want, in its column or in another of your team's.
Once started, the card sends its files to the assistant with its words, in the first message of its conversation. They stay under the card's description, at the top of its conversation, where each one downloads. The pencil, “Edit the description”, adds or removes some, and the assistant reads the new list with your next message or your next plan request.
Your team's columns
The first one is called “Backlog”. “Add a column”, at the end of the board, creates another. Click a column's name to change it, and drag the column by its header to place it wherever you like, even between two of the assistant's columns. Its bin deletes it: its waiting cards go back to “Backlog”, its started cards to their assistant column. “Backlog” cannot be deleted.
A started card can also be kept in one of your team's columns, to set it aside for instance. It takes a place among the waiting cards there: drag it above or below one of them, and a waiting card passes it the same way. It keeps its buttons there and recalls, under its title, the assistant column it stands in. It leaves when you drag it back to that column, or when the assistant gets back to work on it. A card that is queued or being built cannot be set aside.
Set aside, its test version is paused: it stops and no longer counts in your tier, which frees a place for another one. Its test data is kept, and so is its conversation. The card shows “Paused” under its title; while it stays there, its conversation can be read but takes no message, its preview still opens, and “Publish” is still possible. Kedalia refuses to set it aside while the assistant works on it or while its test version is being prepared or put online: “The assistant is working on this card or its test version is being prepared: put it away once that is over.” “Relaunch”, on the card or in its conversation, puts it back online without changing its column; dragging it back to an assistant column, or queueing it, relaunches it too. Allow a few minutes. If your tier is full, the relaunch is refused and the card stays paused. Relaunched but left in its column, it pauses again after 12 hours with no activity: no message, no preview opened, no sign-in to the test version.
Starting a card
A started card is a request in progress. It has its own test version, with its address and its test data (see Test versions), and its conversation with the assistant, shared by the whole team. A started card is born in four ways:
- “Discuss with the assistant”, in a waiting card's window;
- a waiting card dragged into “In discussion”;
- “Add a card”, at the top of “In discussion”: a title, “What should change?”;
- “Create a test version”, on the Applications page: every test version is a card of the board.
A change made straight in the live application's conversation has no card: to follow it here, go through a test version.
The card arrives at the top of “In discussion” and first says “Preparing” while its test version is prepared. One that was waiting quotes its text and adds: “The assistant will read this card as soon as the test version is ready.” A click on the card opens its conversation; the “Kanban” tab returns to the board.
A card changes column from the Kanban: with its buttons, or by dragging it. When the top bar has room for it, the “Kanban column” list, at the top of its conversation beside “Publish”, also tells where the card stands and moves it: to “Queued” once its plan is read, from the queue back to its previous column, or to a column of your team. If your organisation leaves the Business tier while a card waits in the queue, the “Take out of the queue” button, at the top of its conversation beside “Publish”, takes it out of the queue.
Clarify, then approve the plan
In the card's conversation, answer the assistant's questions, then click “Request the plan” (see Asking well). Meanwhile the card says “Writing the plan”, then “Plan ready”. As long as there is no plan, the card stays in “In discussion” and says so: “Ask for the plan in its conversation first.” A person always reads the plan before the assistant applies it.
The queue
Once the plan is read, click “Add to the queue” or drag the card into “Queued”. The assistant takes the cards in order, as soon as it is free. Each card shows its place, for instance “No. 2 in the queue”, counted among all your organisation's queued cards, every application included. Then “Starts in a moment”, or “Waiting:” followed by the reason, when the assistant's usage is used up for a while.
“Take out of the queue” brings it back to the column it came from. An interrupted build sends the card back to “In discussion” with “Interrupted”: “Continue” puts it back in the queue.
Being built, then to approve
While building, the assistant applies the plan, checks it and updates the test version by itself. The card says “Updating” while the test version updates, then moves to “To approve”. If the tests are still running, it says “Tests running” there, and “Publish” offers to publish now or after the tests. There it offers “Open the test version”; you get in with your Kedalia account, or with the “Sign-in details” button at the top of its conversation.
Try it. If something is wrong, click “Ask for a change” on the card, or drag it into “Queued”: the “What should change?” window opens. Describe the change, then “Add to the queue”. The card goes back to “Queued” with “Change requested”, and the assistant applies your words to what was just done. If the tests failed, the card says “Tests failed” and does not offer to publish: ask for a change.
For a change worth talking over first, drag the card into “In discussion”: its conversation opens. A question does not move the card; “Request the plan” brings it back to “In discussion” with “Plan ready”, and you put it back in the queue once you have read the new plan.
Publish
When the test version suits you, click “Publish”. The “Publish this card?” window recalls that the changes join the live app, then that the test version is removed; it closes at once, and a message says “Publishing started: tests, then going live, about 4 min.”. The card carries a line that follows its publication: “Publishing · combining with” the app, “Publishing · Tests”, “Publishing · Start-up”, then “Live since” followed by the time (and the day, if not today), or “Tests failed · nothing changed”. It moves to “Live” once combining is done. In “Live”, a card's border says where its publication stands, and a legend under the column recalls it: “Amber dashes: publishing”, “Green: live”, “Red: failed, nothing changed”. Under a failed card, “See the error” (the tests) or “See why” (the start-up) opens its conversation, which explains what happened. A live card stays so, even if the app stops later, until another change is published to the app: it then gets the ordinary border back and says “Published”. A published card moved to one of your team's columns keeps its border. When “Publish” is greyed out or missing on a card, the reason is written on it: the tests of the test version failed, the assistant is working, or the live app is being updated. The card's conversation can still be read, but takes no more messages. The “Remove” bin takes it off the board. For what happens when going live, see Going live.
For an app whose code stays on GitHub, the card's change request opens on GitHub as soon as the assistant sends its first change, and its tests run there at each new send. “Publish” waits until they have all passed. If a test fails, the assistant says which one and why, then proposes to fix either the test or the app, depending on what changed: nothing is changed without your agreement. If the same tests still fail at the next change, the conversation says so without analysing again. “Analyse” disappears once the failure is analysed and comes back when a new change fails; for another analysis, ask for it in the conversation. If the card conflicts with the live app, GitHub does not run its tests: the conversation says so. If “Publish” must first catch up with the live app, the tests run again on the new version, and the publication goes out by itself as soon as they have passed.
For an app whose code stays on GitHub, the change request “Publish” opened can also be accepted directly on GitHub. Kedalia notices within five minutes and moves the card to “Live”, as if it had published it, unless it still has changes to send: “Publish” sends them. Kedalia merges the way the repository accepts, trying in turn the three ways GitHub offers; when it must, it first gathers the card into a single change, with the same content. If the repository refuses them all, for example because it requires a review, the change request stays open on GitHub: once the review is accepted and its tests have passed, Kedalia merges it on its own within the next few minutes, and the card moves to “Live”. A change request closed on GitHub without being merged stops the publication.
To take a published card up again, click “Reopen”, or drag it into “In discussion”. Its test version is recreated from the app as the “Preview” shows it, and its conversation carries on, with the assistant, once the card is ready. It is back in “In discussion”: what it had published is already live. Either way, Kedalia first asks “Reopen “…”?”, with the card's title. A reopened card in which nothing has been done since can go back to “Live” without publishing anything: click “Close again”, or drag it to “Live”. Kedalia first asks “Close “…” again?”. If the live app changed the same files meanwhile, the assistant first combines the two versions: see Test versions.
Renaming a card
A card's “Rename” pencil, which shows on hover next to its bin and always on a phone, opens the “Rename the test version” window, the same as in “Applications” (see Test versions). A ready card also changes address: it goes back to “In discussion”, “Preparing”, while it installs itself again. While the assistant works on a ready card, the pencil is greyed. A published card is renamed too: only its title changes, the one it takes back if you reopen it.
Abandoning a card
A card's bin, which shows on hover, abandons it. The “Remove this card?” window warns that the test version, its data and its conversation are deleted for good. As long as the assistant has built nothing on the card, and its test version has not failed, “Remove” is enough; once it has built something, the window also asks you to type its title. A card being built or being prepared cannot be abandoned. The bin only shows for the person who created the card and for the organisation's administrators.
Undoing a start
A card in “In discussion” started by mistake becomes a waiting card again: its back arrow, which shows on hover, opens the “Undo the start?” window. Its test version and its conversation are deleted, and the card goes back to the top of “Backlog” with the card's title, description and attached files. “Discuss with the assistant” will open a new conversation. The arrow shows once the test version is ready, not while the card says “Preparing”, and, like the bin, only for the person who created the card and for the administrators.
On a phone
A finger does not drag the cards: the cards' buttons do the work (“Add to the queue”, “Ask for a change”, “Publish”…). You can also write the change in the card's conversation, then click “Adjust directly”. A “Move to…” list puts a waiting card in another of your team's columns, moves it up or down (“Move up”, “Move down”), and puts a started card in one of your team's columns, where it moves up and down the same way. What it puts in a column lands at the bottom of it. The line under the board's title then speaks of “Add to the queue”, not of dragging. The bins stay visible.