Aether Lemric
Coming soonTeam work management

From issue to resolution.

Aether Lemric will bring projects, issues and workflows into one system. We are building it for teams that need to know what needs doing, who owns each task and what is blocking the next step.

Explore the featuresSee the product concept

In development. Discover the planned features and product direction.

Aether Lemric / AET
Release preparation0.1
To do2
In progress1
Done1
AET-12Organise the release backlog
AET-14Define issue closure conditions
AET-08Prepare the team workflow
An interface concept with sample data. It illustrates the planned way of working, rather than a finished application.

Organised issues. Clear rules for your team.

01

Every issue has an owner.

Issues with priorities, assignees and a change history. Lists, backlogs and boards will help teams plan their work and track its progress.

List · Backlog · Board

02

A process defined by rules.

States, transitions and conditions tailored to each project. Teams will see what is needed to close an issue and why a transition is blocked.

States · Transitions · Conditions

03

Time linked to the work done.

Manual entries, a timer and period approvals. A correction history will preserve the context of time records and accountability for every change.

Time records · Approvals · History

Aether / AET

Explore your team's workspace.

An interface concept with sample data. It illustrates the planned way of working, rather than a finished application.

ARelease preparationAET

Agile and Kanban boards

A backlog, iteration planning and tasks moving across a board. Agile and Kanban views will support both sprints and continuous delivery of work.

To do2

  • AET-12
    Organise the release backlog
    To doAK
  • AET-14
    Define issue closure conditions
    To doJP

In progress1

  • AET-08
    Prepare the team workflow
    In progressMK

Done1

  • AET-05
    Define the project scope
    DoneAK

Project dashboard

Issue statuses, priorities and project progress in one view. A starting point for the team's daily review of its work.

To do2
In progress1
Done1
Project dashboard
IssueStatus
AET-12Organise the release backlogTo do
AET-14Define issue closure conditionsTo do
AET-08Prepare the team workflowIn progress
AET-05Define the project scopeDone

Project components

Divide a project into areas and assign issues to them. Components will help teams find work related to a specific part of the product.

Project componentsIssueAssignee
WorkflowAET-08Prepare the team workflowMK
BoardAET-12Organise the release backlogAK
Time trackingAET-14Define issue closure conditionsJP

Releases and versions

Issues linked to planned releases. A version overview will show which tasks are ready and which still need work.

0.1Release preparation
Releases and versions
IssueStatus
AET-12Organise the release backlogTo do
AET-14Define issue closure conditionsTo do
AET-08Prepare the team workflowIn progress
AET-05Define the project scopeDone

Development

Branches, commits and code reviews in the context of an issue. The planned view will connect each task with the code changes that address it.

Branchfeature/aet-08-workflow
Commit7c81e2a · AET-08
Code reviewAET-08 · #24

Gantt planning

Tasks on a timeline, dates and dependencies between work items. The Gantt view will help teams build a schedule and see the order of delivery.

Gantt planning
IssueWeek 1Week 2Week 3Week 4
AET-12Organise the release backlogAET-12
AET-14Define issue closure conditionsAET-14
AET-08Prepare the team workflowAET-08
AET-05Define the project scopeAET-05

Workflow

A transition changes an issue's state. Conditions determine when that transition can take place.

  1. 1To do
  2. 2In progress
  3. 3Done
Example closure condition

Closing the issue requires approval. Without it, the issue remains in progress.

Time tracking

Manual entries, a timer and period approvals. A correction history will preserve the context of time records and accountability for every change.

Sample time entries
IssueTime
AET-08Prepare the team workflow1.5 hr
AET-05Define the project scope0.75 hr
AET-12Organise the release backlog1 hr
Total3.25 hr

The same product. Two deployment models.

We are planning Aether as a self-hosted installation and as a service. Your team will choose where it runs.

On your infrastructure

A self-hosted installation for organisations that want to manage their own system and data. Also designed to work without a connection to the vendor's service.

In the Lemric cloud

A SaaS edition for teams that want to use Aether without maintaining their own server. Lemric will manage the infrastructure.

Coming soon

Aether Lemric is in development.

We are starting with the foundations: issue tracking, the workflow engine and time records. The first release is planned for self-hosted installation and as a SaaS service.

We will announce the launch date when work on the first release is complete.

Explore Lemric projects