v0.4.0
What's new
Status timeline on every issue
A Stats section above the activity log shows how the issue moved through the
statuses.
- The compact bar gives one share per status, plus lead time and cycle time once
the issue is done. - The timeline gives a lane per status on one time axis. A status visited twice
shows as two bars in the same lane. - Click a share or a bar to read what was written while the issue sat there.
- Account → Preferences sets how the section opens: expanded or collapsed, compact
or timeline.
Code blocks, a slash menu, and images you already have
- Type "/" with nothing selected to insert a block from a list.
- Code blocks are syntax highlighted, in light and dark theme.
- Pick an image the issue already has attached and drop it at the cursor. No second
upload. - Drag the corner of an image to resize it. The width survives a reload.
Your version, and the next one
The sidebar footer shows the version this instance runs. Owners click it to read the
release notes and to check whether a newer release is out. The check runs once every
six hours no matter how many tabs are open, and a failed check keeps the last answer.
Agent chats have an owner
- Two agents on the same issue no longer share one conversation. A repeat mention or
a retry picks the thread back up instead of starting over. - The runs of one schedule build on each other, cron or manual.
- A chat thread belongs to the person who opened it. Nobody else can continue it.
- Delete a thread from either thread list. Delete the open one and the chat starts
fresh. - Delete an agent, a project or a schedule, or archive an issue, and its
conversations go with it. - An agent's temperature setting now reaches the model.
One anonymous snapshot a day
The instance reports once a day: version, runtime, rounded counts, which features and
integrations are on, how often webhooks and agent runs fail. No names, no content, no
exact numbers. TELEMETRY.md lists all of it. Turn it off with TELEMETRY_DISABLED
or DO_NOT_TRACK.
Fixes
- An issue can no longer be given another project's column, type, label or custom
field. It used to accept them, which parked issues on boards their project does not
own and gave away the names of other projects' labels and fields. - A custom field rejects an option that belongs to a different field, and leaves the
current selection alone. - Opening an issue from the board is faster: fewer requests, and they no longer wait
in line.
Changelog
Full diff: v0.3.0...v0.4.0
Features
- scope agent memory threads and delete them with their owner (#42) (2857970)
- send an anonymous daily instance snapshot (#35) (be68f4a)
- show an issue status timeline above the activity log (#34) (a4b6bd9)
- show the running version and available updates in the sidebar (#31) (74885d3)
- web: add code blocks, a slash menu and image picking to the issue editor (#40) (db52b5e)
Bug Fixes
- api: scope issue column and type to the issue's project (#39) (84b82e5)
- api: scope issue custom fields to the issue's project (#36) (51fe6d3)
- api: scope issue labels to the issue's project (#38) (9ba0fe8)
- web: correct the layout and figures of the issue stats (#41) (0a03c84)
Performance
CI