OpenFn / OpenFn/lightning

Consider Re-ordering the activity history page when a work order is re-run

Open
#1,360 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs detail ux/ui improvement
Dominant language
Elixir
Stars
296
Forks
86
Avg merge
1d 13h
Merged PRs (30d)
50

Description

Right now we don't. And that might be OK. But we also might want it jumping up to the top? Smoothly? Lol. @NickOpenFn , what should we do here?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the activity history page and the work-order re-run flow described in the issue. Before changing anything, confirm with the maintainer whether re-run activity should move to the top and whether that movement should be smooth; done requires an agreed ordering and interaction behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
elixir
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.