Skip to content

Radd 0.48.0

Choose a tag to compare

@github-actions github-actions released this 24 Sep 10:25
· 160 commits to main since this release

v0.48.0

23 changes · 4 Bugfixes, 14 New Features, 5 Chores · 82 points.

Bugfix

  • RADD-1303 A project's Manager can manage its SLA policies (sla. become project-scoped)*
    A project's Manager can create and edit that project's SLA policies; it no longer takes an instance administrator.
    access slas · 2 pts · 62e0ce0d
  • RADD-1294 Directory page stops rendering 4,439 checkboxes, the palette opens on what you need, the inbox groups repeats
    Settings → Directory is split into Connection / User sync / Groups tabs with the groups paged, the command palette opens on recent issues and the current project instead of 123 "New issue in X" rows, and repeated inbox notifications collapse into one row.
    performance ux · 5 pts · b71c7ff3
  • RADD-1293 Counts say what they count: request badges, "loaded" totals, duplicate roadmap counts, "0 shown"
    Counts say what they count: "My requests" shows the real total beside what needs your reply, the board header reads "N issues", the roadmap shows one count, and My Work never says "0 shown".
    ux · 2 pts · 3c11ce6e
  • RADD-1292 The create form follows Screens, the issue view stops 404ing on CSAT, list columns say what they show
    The new-issue form follows the type's Screen (hidden fields stay off it, secondary ones sit under "More fields"), issue views stop logging a failed CSAT request, and list columns show the type's name and the priority's word.
    items ux · 3 pts · b1868fb4

New Feature

  • RADD-1302 One role ladder: Viewer ⊂ Member ⊂ Manager, meaningful on projects and spaces alike
    "Admin" is now "Manager", and Viewer ⊂ Member ⊂ Manager is a real ladder that works on projects and on wiki spaces alike. Members no longer manage intake forms: grant Manager to anyone who edits them.
    access auth · 5 pts · 709a9a1b
  • RADD-1304 One "own ticket" set for Baseline, Requester and Contributor, and sharing becomes a grant (participant.manage@own)
    A ticket's reporter can attach to it and share it with others, and the same own-ticket rights now apply to staff, emailed-in requesters and public contributors alike.
    access auth participants · 3 pts · c944490a
  • RADD-1300 SLA policies can be edited, not only created
    SLA policies can be edited in place from the project's SLA settings, not only created and deleted.
    slas · 2 pts · 26c7b13a
  • RADD-1299 SLA targets say what "met" means: states entered or left, replies by chosen or assigned teams; policies can match on the reporter's team
    An SLA target can say what meets it: leaving or entering chosen states (e.g. "out of Triage"), or a reply from chosen teams or the issue's own team. A policy can also apply only to reporters in chosen teams.
    slas · 5 pts · 696838c2
  • RADD-1297 Link to one comment: permalinks on issues and pages, and notifications that land on the comment
    Every comment and reply has a Copy link that opens straight on it, even far back in a long thread; comment and mention notifications now open on the comment itself.
    comments notifications · 5 pts · 4b91f33e
  • RADD-1295 A person can have a real profile picture: upload, the IdP's picture, then the colour/emoji
    People can have a real profile picture: upload one, or get your Google/GitHub picture automatically.
    attachments auth · 3 pts · 9b486479
  • RADD-1282 Resolvable issue discussions with an all-threads-resolved workflow condition
    Resolvable threads. Start a thread instead of a plain comment when a discussion needs an answer: threads can be resolved and reopened (a reply can reopen one), "Unresolved threads" filters to what is still open, and a workflow rule can refuse a transition until every thread is resolved.
    triage · b6dfc2e2 · 6cd3ea68
  • RADD-1296 Checklists you can read and tick: legible checkboxes, strikethrough, toggle without editing
    Checklists are real checkboxes you can read at a glance, done items are struck through, and you can tick them without opening the editor.
    editor items pages · 3 pts · 356dbe5b
  • RADD-1279 An instance can require MFA: a policy switch, an enforcement seam, and admin visibility
    An administrator can require MFA: password sign-ins without TOTP are sent through enrolment first, the user list shows who is enrolled, and an admin can reset one person's enrolment. The switch refuses to turn on while the admin flipping it is not enrolled.
    auth · 5 pts · f221cf10
  • RADD-1291 Cycles have a home project: project managers create them, planning and reports show the project's cycles
    Cycles belong to a project: a project's manager can create and run its sprints without instance admin, and planning, reports and cycle pickers show that project's cycles (a cycle can still hold issues from other projects).
    cycles · 5 pts · 75a88cb6
  • RADD-1290 Releases and Reports are project pages, not settings or a buried menu; Milestones leaves the nav
    Releases and Reports are project pages every reader can open (each release lists the issues it shipped), and Milestones is off by default on a new instance. Issue-header actions are regrouped, with Delete behind ⋯ and a confirm.
    releases reporting ux · 5 pts · 6c824c10
  • RADD-1288 Settings autosave, working days are day toggles, durations take units, no native controls
    Settings save as you change them (no more one Save button per field), the working week is seven day toggles, SLA targets accept durations like "1h 30m" or "2d", and enable/disable rows are real switches.
    settings ux · 5 pts · 14ec94de
  • RADD-1285 Shipping is a workflow transition: "moves when a release is published" + "requires a release", and the four state-name settings go
    Shipping is set up in the workflow: a transition can "move when a release is published" and a state can require a release, replacing the two typed-in state-name settings. Existing pipelines are converted automatically.
    releases workflow · 8 pts · 75779bf4
  • RADD-1283 Threads on wiki pages, and who may resolve a thread is a per-project, per-issue-type policy
    Threads on wiki pages, and who may resolve them. Page discussions and inline comments get the same resolvable threads as issues, and each project decides who may resolve a thread (anyone, the thread's author, or chosen roles), with a different rule per issue type if needed.
    comments pages · 5 pts · 6cd3ea68

Chore

  • RADD-1305 Built-in roles cannot drift, Staff folds into Viewer, umbrellas imply what they administer
    Built-in roles keep themselves in step with each release (every correction is in the audit log); the Staff role is folded into the identical Viewer role.
    access auth · 3 pts · 7a42fd8e
  • RADD-1298 QR code at TOTP enrolment (GitHub #21)
    Reported by @remusavram in GitHub #21: "display a QR code (in addition to any manual entry code) so users can scan it with an authenticator app instead of typing the secret manually."
    auth · f221cf10
  • RADD-1289 Copy for people: no spec/ticket numbers, no stale claims, no banners that repeat the subtitle
    Settings, plugin and permission text is written for people: no spec or ticket numbers, no stale claims, and no banners repeating the page subtitle.
    docs ux · 2 pts · e3b51c24
  • RADD-1287 One vocabulary: "issue" in the UI, one name for the portal and the server page, "New …" for every create
    The interface says "issue" everywhere (the API still says item), the Portal and the Server status page each have one name, and every button that opens a form reads "New …".
    ux · 3 pts · aaa0e39f
  • RADD-1286 States are picked, never typed; workflow-wide settings say where they apply
    SLA pause states are picked from the project's states instead of typed, and workflow-wide settings say whether they are the instance default or this project's override.
    slas workflow · 3 pts · 0aa190e3

Changes from v0.47.0 to v0.48.0.